ctk
CTK: team progress, 5h/weekly usage, worker cap and settings, profile sync across machines.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- ctk
- description
- CTK: team progress, 5h/weekly usage, worker cap and settings, profile sync across machines.
- argument-hint
- [status | config | sync | what you want]
03 SKILL.md 正文
Request: $ARGUMENTS (if empty, use the user's last message). Pick ONE section. Answer in the user's language.
Status, progress, usage
The CTK tools are deferred: if mcp__ctk__ctk_team_status (or mcp__ctk__ctk_config) has no schema loaded, load it
first with ToolSearch (select:mcp__ctk__ctk_team_status). Then call it and answer from its JSON only. Fields:
live, max, workers, rejected, accepted, cap, teamsEnabled, taskTools, guard, running, idle, cleanupCandidates,
completed, failed, teamElapsedMs, subagents, explain, tasks. usage (contextPct, fiveHour, sevenDay, cost,
toolCalls, model) appears only when called with includeUsage: true.
cleanupCandidatescarriesagentId,teammateId, andnamefor idle teammates after observed task completion; it is advisory, not proof review passed or permission to shut them down.- A field that is missing, null or "unavailable": say "unavailable". Never estimate or guess a number.
- No workers or tasks: say
explain.workers/explain.tasksin your own words. Agents counted insubagentsare ordinary subagents, not teammates; never call them workers. - Usage questions (5h limit, weekly limit, cost): call with
includeUsage: trueand report only whatusagecontains. Never fetch it for plain progress questions or to pace the team. - Mention once that the clickable CTK band is the live view and
/ctk-missionopens Mission Control. - Tool not registered: the CTK mod is not active here. Say so; do not invent values.
Is CTK working
Tell the user to run /ctk-doctor, or call mcp__ctk__ctk_team_status and report what it returns.
Never state a result you did not see.
Change a setting
Load the tool with ToolSearch (select:mcp__ctk__ctk_config) if its schema is not loaded.
Option names: maxWorkers, explorerModel, implementerModel, reviewerModel, highRiskModel, designerModel, hudBand,
hudIdle (what the band shows before a team starts: full, minimal or hidden), recordStats, teamHint, bashFilter, stopAtFiveHourPct (1-100, 0 off), stopAtCostUsd (dollars, 0 off). Never guess another name; if the request maps to none, say so and list these.
- List current values:
mcp__ctk__ctk_configwith{"action":"show"}. - Change:
{"action":"propose","option":"maxWorkers","value":2}(value is a number, boolean or model name). - The tool applies NOTHING. It opens a confirmation in the Mission Control pane and the user confirms there.
Say that plainly, in the user's language: "I opened CTK Mission Control; press Confirm there to apply it (or Cancel).
Nothing changes until you do." The band shows "Confirm setting" until it is answered.
Never claim the change happened. Never edit
settings.json. - Tool not registered: say so and point to
/plugin configure ctk@ctk-kit.
Sync a profile between computers
This needs the optional ctk CLI (git-based; 3-way merge, secrets scan, conflict detection). It syncs the CTK
profile only, never credentials, env, hooks or permissions. Never touch settings.json or ~/.claude yourself.
ctk --versionwith Bash. If missing: say sync needs the CLI, linkdocs/INSTALLATION.md#the-optional-ctk-cli(in the CTK repository), and stop.ctk sync status. If it says sync is not set up, ask the user for the profile git remote (URL or path), thenctk sync init --remote <remote>only after they give it.- Preview first and show the output:
ctk sync pull --dry-run(get the other computer's settings) orctk sync publish --dry-run(send this computer's,-m "<message>"is optional). - Ask in plain words: "This will <pull/publish> as shown. Go ahead?" Run the same command without
--dry-runonly after an explicit yes. - Exit code 2 means conflicts: stop, show them, let the user choose
ctk sync resolve <pointer> ours|theirsper conflict. Exit 1 with a secrets finding means refused: show it and stop. Never bypass the scan, never force.
04 同仓库更多 Skills
team
Invoke before spawning several agents, or when asked to use CTK, a team or parallel work (多個 Agent, 平行, ctk 流程). Keeps the worker cap.
review
CTK risk-based review of current changes: picks reviewer depth by diff risk. For 'review my changes'.
debug
CTK debug for failing tests or behavior: reproduce, diagnose, fix, regression. Use when CTK debugging is requested, or when no standalone debugging skill is installed.
graders
暂无简介
graders
暂无简介
graders
暂无简介