| name | t1k:help |
| description | Display TheOneKit usage guide with live registry state. Use for 'what commands exist', 'which agents are registered', 'how do I use TheOneKit'. |
| keywords | ["help","usage","guide","commands","agents","registry","list"] |
| effort | low |
| argument-hint | (no arguments) |
| version | 1.108.0 |
| origin | theonekit-core |
| repository | The1Studio/theonekit-core |
| module | t1k-base |
| protected | true |
TheOneKit Help
Lists all commands and dynamically shows registered agents from the routing registry.
Live Registry State (fetch on demand — DO NOT inline in body)
When the user asks for the help guide, fetch the live registry state via tool calls AFTER this skill body is loaded — do NOT embed inline shell-substitution tokens (the !-prefix-then-backtick syntax) in the body (cache-busts every fragment edit). Use:
Read .claude/metadata.json → installed kits + modules
Read .t1k-module-summary.txt → module summary (may not exist)
Read each .claude/t1k-routing-*.json matching glob → role→agent mapping (highest-priority wins per role)
Read each .claude/t1k-activation-*.json matching glob → keyword→skill activation
Read each .claude/t1k-config-*.json matching glob → extra commands registered by installed kits
If a file does not exist, treat as "no entries" and skip silently — do not echo error.
Dynamic Registry Listing
MANDATORY: After fetching above, generate the agents table from routing fragments. Show which role is mapped to which agent (highest-priority registry wins per role). List any extra commands from config fragments.
Commands (Core)
Implementation
| Command | Purpose |
|---|
/t1k:cook | Feature implementation (registry-routed) |
/t1k:plan | Implementation planning (t1k-planner agent) |
/t1k:brainstorm | Ideation (t1k-brainstormer agent) |
/t1k:test | Run tests (registry-routed) |
/t1k:fix | Fix bugs (registry-routed) |
/t1k:debug | Debug issues (registry-routed) |
/t1k:review | Code review (registry-routed) |
Documentation and Git
| Command | Purpose |
|---|
/t1k:docs | Documentation management |
/t1k:git | Git operations (cm/cp/pr/merge) |
Maintenance
| Command | Purpose |
|---|
/t1k:triage | Triage issues/PRs across all registered repos |
/t1k:sync-back | Push .claude/ changes to origin kit repos |
/t1k:issue | Report problems to correct kit repo |
/t1k:doctor | Validate registry integrity |
/t1k:help | This help guide |
Module Management (when modular kits installed)
| Command | Purpose |
|---|
/t1k:modules add <names> | Install modules + auto-resolve dependencies |
/t1k:modules remove <names> | Remove modules (refuses if dependents exist) |
/t1k:modules list | Show installed and available modules |
/t1k:modules preset <name> | Switch preset (additive; --replace for clean) |
Installed Modules (Dynamic)
Follow protocol: skills/t1k-modules/references/module-detection-protocol.md
If installedModules present in .claude/metadata.json, for each installed module:
- Module name, version (from
installedModules[name].version), kit, required/optional status
- Available-but-not-installed modules (from kit release info)
If no installedModules key or no metadata: skip this section silently.
Universal
| Command | Purpose |
|---|
/t1k:scout | Codebase exploration |
/t1k:ask | Technical Q&A |
/t1k:watzup | Session review |
Search and Filter
/t1k:help --search <query> # Filter commands matching keyword in name or description
/t1k:help --category <cat> # Filter by category: implementation, maintenance, modules, universal
Search behavior: case-insensitive match against command name + description. Show only matching rows.
Category values: implementation, docs-git, maintenance, modules, universal
Chaining Suggestions
After showing help for a specific command, append suggested next commands:
| Command shown | Suggested next |
|---|
t1k:plan | t1k:cook |
t1k:cook | t1k:test, t1k:review |
t1k:test | t1k:review (pass) or t1k:fix (fail) |
t1k:review | t1k:git cm |
t1k:fix | t1k:test |
t1k:debug | t1k:fix |
t1k:triage | t1k:cook --auto --parallel |
Format: **Next:** /t1k:{cmd1}, /t1k:{cmd2}