Skip to content

t1k:help

FieldValue
Modulet1k-base
Version2.17.3
Effortlow
Tools

Keywords: agents, commands, guide, help, list, registry, usage

/t1k:help
(no arguments)

Lists all commands and dynamically shows registered agents from the routing registry.

Live Registry State (fetch on demand — DO NOT inline in body)

Section titled “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.

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.

CommandPurpose
/t1k:cookFeature implementation (registry-routed)
/t1k:planImplementation planning (t1k-planner agent)
/t1k:brainstormIdeation (t1k-brainstormer agent)
/t1k:testRun tests (registry-routed)
/t1k:fixFix bugs (registry-routed)
/t1k:debugDebug issues (registry-routed)
/t1k:reviewCode review (registry-routed)
CommandPurpose
/t1k:docsDocumentation management
/t1k:gitGit operations (cm/cp/pr/merge)
CommandPurpose
/t1k:triageTriage issues/PRs across all registered repos
/t1k:sync-backPush .claude/ changes to origin kit repos
/t1k:issueReport problems to correct kit repo
/t1k:doctorValidate registry integrity
/t1k:helpThis help guide

Module Management (when modular kits installed)

Section titled “Module Management (when modular kits installed)”
CommandPurpose
/t1k:modules add <names>Install modules + auto-resolve dependencies
/t1k:modules remove <names>Remove modules (refuses if dependents exist)
/t1k:modules listShow installed and available modules
/t1k:modules preset <name>Switch preset (additive; —replace for clean)

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.

CommandPurpose
/t1k:scoutCodebase exploration
/t1k:askTechnical Q&A
/t1k:watzupSession review
/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

After showing help for a specific command, append suggested next commands:

Command shownSuggested next
t1k:plant1k:cook
t1k:cookt1k:test, t1k:review
t1k:testt1k:review (pass) or t1k:fix (fail)
t1k:reviewt1k:git cm
t1k:fixt1k:test
t1k:debugt1k:fix
t1k:triaget1k:cook --auto --parallel

Format: **Next:** /t1k:{cmd1}, /t1k:{cmd2}