ccs-delegation
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" pa
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 2859
- Лиценз
- MIT
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add kaitranntt/ccsСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
CCS Delegation
Delegate deterministic tasks to cost-optimized models via CCS CLI.
Core Concept
Execute tasks via alternative models using:
- Initial delegation:
ccs {profile} -p "task" - Session continuation:
ccs {profile}:continue -p "follow-up"
Profile Selection:
- Auto-select from
~/.ccs/config.jsonvia task analysis - Profiles: glm (cost-optimized), kimi (long-context/reasoning), custom profiles
- Override:
--{profile}flag forces specific profile
User Invocation Patterns
Users trigger delegation naturally:
- "use ccs [task]" - Auto-select best profile
- "use ccs --glm [task]" - Force GLM profile
- "use ccs --kimi [task]" - Force Kimi profile
- "use ccs:continue [task]" - Continue last session
Examples:
- "use ccs to fix typos in README.md"
- "use ccs to analyze the entire architecture"
- "use ccs --glm to add unit tests"
- "use ccs:continue to commit the changes"
Agent Response Protocol
For /ccs [task]:
-
Parse override flag
- Scan task for pattern:
--(\w+) - If match:
profile = match[1], remove flag from task, skip to step 5 - If no match: continue to step 2
- Scan task for pattern:
-
Discover profiles
- Read
~/.ccs/config.jsonusing Read tool - Extract
Object.keys(config.profiles)→availableProfiles[] - If file missing → Error: "CCS not configured. Run: ccs doctor"
- If empty → Error: "No profiles in config.json"
- Read
-
Analyze task requirements
- Scan task for keywords:
/(think|analyze|reason|debug|investigate|evaluate)/i→needsReasoning = true/(architecture|entire|all files|codebase|analyze all)/i→needsLongContext = true/(typo|test|refactor|update|fix)/i→preferCostOptimized = true
- Scan task for keywords:
-
Select profile
- For each profile in
availableProfiles: classify by name pattern (see Profile Characteristic Inference table) - If
needsReasoning: filter profiles wherereasoning=true→ prefer kimi - Else if
needsLongContext: filter profiles wherecontext=long→ prefer kimi - Else: filter profiles where
cost=low→ prefer glm selectedProfile = filteredProfiles[0]- If
filteredProfiles.length === 0: fallback toglmif exists, else first available - If no profiles: Error
- For each profile in
-
Enhance prompt
- If task mentions files: gather context using Read tool
- Add: file paths, current implementation, expected behavior, success criteria
- Preserve slash commands at task start (e.g.,
/cook,/commit)