Loading...
Loading...
Found 1,682 Skills
Final retrospective and self-assessment for participants of Claude Code Lab. Runs four sequential interactive parts — progress audit, best prompt, monthly plan, and feedback — using AskUserQuestion. Triggers on "/lab-retro", "lab retrospective", "claude code lab final", or after completing the 6-week Claude Code Lab cohort.
Decide which CLI worker (Claude, OpenCode, or Gemini) should implement a given task. Routes by task type — large-context to Gemini, mechanical to OpenCode, judgment to Claude. Returns the chosen worker and a short rationale; the caller invokes the worker via scripts/invoke-worker.sh.
Find the ghost tokens. Audit Claude Code setup, see where 25-38% of your context goes, fix it. Use when context feels tight.
Context window coach. Proactive guidance for token-efficient Claude Code projects, multi-agent systems, and skill architecture.
Evaluates which SaaS tools can be replaced with AI agents. Takes a list of current SaaS subscriptions with costs, assesses replacement feasibility, estimates build vs buy economics, identifies Claude+MCP alternatives, and generates a comprehensive replacement plan with priority matrix, ROI analysis, implementation timeline, and risk assessment.
Execute Claude Code commands in the telegram_agent project directory. Use when the user wants to work on the telegram agent itself, fix bugs, add features, or modify the bot code. This is a COMMAND HANDLER, not a script executor.
Initialize, diagnose, or migrate a project into the LLM wiki pattern with AGENTS/CLAUDE instructions, QMD MCP wiring, Claude/Codex hooks, guardrails, and QMD doctor checks. Use when the user asks to set up wiki infrastructure, check if a project needs migration, install wiki hooks, or validate QMD.
Creates or audits a Claude Code hook. Use when user says 'add a hook', 'create a hook', 'review our hooks', 'audit hooks', 'wire up a format-on-save hook', 'block edits to secrets', or 'our hooks are broken'. Do NOT use for skills (use create-or-audit-skill), agents (use create-or-audit-agent), or settings (edit `settings.json` directly).
Creates or audits a Claude Code subagent file. Use when user says 'create an agent', 'build a subagent', 'review this agent', 'audit our agents', 'add a code-reviewer agent', or 'our agents are too broad'. Do NOT use for skills (use create-or-audit-skill), hooks (use create-or-audit-hook), or CLAUDE.md files (use create-or-audit-claude-md).
Run a session retrospective against the CLAUDE.md, skills, and hooks — identify guidance violations, stale rules, and gaps. Use when user says 'reflect on this session', 'what did we learn', 'post-mortem this work', 'what should we update in CLAUDE.md', or 'are our skills still right'. Do NOT use for code review (use /review-diff), PR prep (use /create-pr), or creating new skills from scratch (use /create-or-audit-skill).
Creates or audits a CLAUDE.md file — the ambient project-context document Claude Code loads at session start. Use when user says 'create a CLAUDE.md', 'audit our CLAUDE.md', 'is our CLAUDE.md any good', 'our CLAUDE.md is out of date', 'make CLAUDE.md load-bearing', or 'write scope-level CLAUDE.md'. Do NOT use for skills (use create-or-audit-skill), agents (use create-or-audit-agent), or user-facing documentation (use write-doc).
Auto-capture per-session token usage from the Claude Code session jsonl and persist to the cost-tracking namespace