deepseek-disable

Name: deepseek-disable
Availability: InStock
Author: dmae97

Disable DeepSeek opportunistic workers to enforce Kimi-only execution.

130|14|Updated Apr 30, 2026

Search Tags:#slash command #deepseek #agent runtime #kimi #workflow reliability #provider fallback #configuration toggle

Ready to run

npx skills add https://github.com/dmae97/oh-my-kimi --skill deepseek-disable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deepseek-disable
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/deepseek-disable
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill deepseek-disable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents unreliable or uncertain DeepSeek worker routing by immediately disabling DeepSeek opportunistic workers and falling back to Kimi-only execution.

Core Features & Use Cases

DeepSeek worker disablement: Turns off DeepSeek opportunistic workers so your workflow continues without provider uncertainty.
Kimi-only fallback: Keeps OMK running using Kimi-only execution rather than attempting DeepSeek.
Operational safety controls: Avoids any handling or exposure of provider credentials while applying the disable decision.

Use case: When DeepSeek balance/auth/provider health is unclear during a coding session, disable DeepSeek to keep work moving with Kimi-only execution.

Quick Start

Run the deepseek-disable command to disable DeepSeek opportunistic workers and continue with Kimi-only execution.

Frequently Asked Questions about deepseek-disable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I switch to Kimi-only execution when DeepSeek provider routing is unreliable?▼

To switch to Kimi-only execution, you can disable DeepSeek opportunistic workers using a slash command. This stops unreliable provider routing during coding workflows without modifying API keys.

How do I disable DeepSeek workers without exposing my API keys?▼

You can disable DeepSeek workers without exposing API keys by applying an operational safety toggle. This command stops provider routing immediately without handling or modifying your provider credentials.

Can I re-enable DeepSeek routing after falling back to Kimi-only execution?▼

Yes, you can re-enable DeepSeek routing later using the corresponding enable command. This restores opportunistic worker availability once provider health, balance, or authentication issues are resolved.

When should I use a provider fallback to stop DeepSeek routing in my coding workflow?▼

You should use a provider fallback to stop DeepSeek routing when balance, authentication, or provider health is uncertain. This ensures workflow reliability by keeping your coding session running with Kimi-only execution.

Does disabling DeepSeek opportunistic workers affect my current agent runtime configuration?▼

Disabling DeepSeek opportunistic workers applies a configuration toggle to your agent runtime. It forces Kimi-only execution to maintain workflow reliability without permanently altering your underlying API key setup.