skills.rest
dmae97
dmae97COMMUNITY
Explore all skills by this author →
GitHub

deepseek-enable

Enables DeepSeek as a read-only worker pool for OMK coding workflows.

130|14|Updated Apr 30, 2026
Search Tags:#deepseek#read-only#provider#omk#worker pool#coding runtime#safety rules
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill deepseek-enable
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deepseek-enable
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/deepseek-enable
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill deepseek-enable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn on DeepSeek as an optional, low-risk read-only worker pool so OMK can opportunistically expand capability while keeping Kimi as the main orchestrator.

Core Features & Use Cases

  • Optional DeepSeek worker pool: Adds DeepSeek availability for read-only work without replacing Kimi’s core planning and coordination roles.
  • Safety-first rules: Prevents accidental key disclosure and encourages running provider diagnostics before relying on availability.
  • Use Case: When you want broader model coverage for coding workflows, you can enable DeepSeek workers while ensuring DeepSeek is only used after valid credentials and adequate balance are confirmed.

Quick Start

Run omk deepseek enable to activate the DeepSeek opportunistic read-only workers.

Frequently Asked Questions about deepseek-enable

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

FAQPage Schema
How do I enable DeepSeek as a read-only worker pool for OMK coding workflows?▼

To enable DeepSeek as a read-only worker pool for OMK coding workflows, simply run the `omk deepseek enable` command to activate opportunistic availability while Kimi maintains core orchestration and planning responsibilities.

What does a low-risk read-only worker pool do in OMK-based coding workflows?▼

A low-risk read-only worker pool in OMK-based coding workflows expands model coverage for coding tasks without taking over Kimi’s core planning, orchestration, merging, and fallback coordination roles, keeping the primary pipeline stable.

Do I need valid credentials and balance to use DeepSeek with OMK?▼

Yes, valid credentials and sufficient balance are required to use DeepSeek with OMK. Operational safety constraints mandate confirming adequate balance and preventing accidental API key disclosure before relying on DeepSeek availability.

How do I check DeepSeek availability before starting an OMK coding workflow?▼

To check DeepSeek availability before starting an OMK coding workflow, run the `omk provider doctor deepseek` command to validate provider status and ensure the opportunistic read-only workers are ready for use.

Why should I keep Kimi responsible for orchestration instead of replacing it with DeepSeek?▼

Keeping Kimi responsible for orchestration ensures low-risk expansion of model coverage. DeepSeek is added as a read-only worker pool to expand capability without disrupting Kimi’s planning, merging, and fallback coordination.

Related Skills

Explore More Software Engineering Skills→
aibtcdevaibtcdev
9

styx

Reserve pool liquidity, build and sign a PSBT, and broadcast BTC→sBTC deposits.

Official
Advanced
dmae97dmae97
130

deepseek-disable

Disable DeepSeek opportunistic workers to enforce Kimi-only execution.

Community
Basic
dmae97dmae97
130

deepseekset

Store a DeepSeek API key in the user-local OMK secret environment file.

Community
Basic
agmangasagmangas
1

local-delegation

Delegate bounded codebase tasks like grep searches and file reading to a local model.

Community
Advanced