Calibrate the Claude Code statusline against the real /usage numbers. Use when the user shares a screenshot of the in-app `/usage` panel (or the claude.ai Settings → Usage page) and wants the statusline's "time left", session %, and weekly % to match what Claude actually reports. Fixes ccusage block-drift, where the local 5-hour clock starts from the first transcript message instead of the real server-side reset.
Dispatch a review task to Gemini CLI (large-context review — plans, docs, large file corpora) or Codex CLI (code review — diffs, PRs, implementation quality). Routes based on the nature of the artifact being reviewed. Use from achieve-goal, literature-survey skills, or any skill that needs a CLI-based review gate. This is a headless CLI review gate over a concrete artifact (code, diff, or doc corpus); for an interactive second opinion or a side-by-side model comparison via MCP chat, use consult-llm instead.
Use when the user wants a second opinion from Gemini or OpenAI/ChatGPT, asks to "consult" another model, or wants to compare responses across models. This is the interactive MCP chat path for a second opinion or model comparison; to run a structured review gate over code, diffs, plans, or large doc corpora through a headless CLI, use cli-review instead.
Use this skill when deciding whether and how to update the knowledge base at /path/to/works/for/you/knowledge_base/ after completing a task. This is the post-task "does this work belong in the KB, and where" decision path; to turn a pasted LLM conversation transcript into a KB note use kb-from-conversation instead.
Periodic review of the memory system at ~/.claude/memory/ for duplicates, redundancies, conflicts, and stale entries. Use when the user asks to audit, clean up, or review memory. Presents findings with enforcement trade-off context — never retires anything without user confirmation. Scoped to the agent memory files under ~/.claude/memory/; for the same kind of duplicate/stale/conflict audit over the knowledge base at /path/to/works/for/you/knowledge_base/ use kb-sweep instead.
Use this skill when the user wants to "promote", "move", "upgrade", or "migrate" a project-level skill, agent, or rule (e.g. a Cursor rule, a project-local AI rule, or any .md skill/agent file) into a global Claude scope. By default always promotes to global (~/.claude/skills/, ~/.claude/agents/, ~/.claude/CLAUDE.md) unless the user explicitly says "project-level". Moves the file so it is shared across all projects and symlinks it back so the original project is not broken. This keeps the skill private to your global ~/.claude scope; to publish skills to the public agent_skills GitHub repo, use publish-skills instead.
Security-reviewed git commit for the ~/.claude backup repo — scans staged changes for secrets before committing. Use when committing only the ~/.claude config repo on its own; for the multi-repo "save state" checkpoint that scans and commits the knowledge base, paper-reading, agent_skills, and ~/.claude repos together, use save-to-github instead.
Surveys informal and industry sources for a given topic — covering Hacker News, engineering blogs, ProductHunt, Medium, Substack, X (indirect), and Quora. Complements literature-survey (which targets academic papers) with community signal, practitioner discourse, and tooling trends. Use when the user wants a community survey, practitioner signal, tooling trends, or runs /community-survey <topic>. This is the one-shot variant; to track a topic's community signal over time (trajectory queries — what shifted, went quiet, or is new across runs) use community-survey-nlm instead.