Claude Code plugin marketplace - productivity and learning plugins
Skill Claude CodeCodex
Use when starting debugging, planning features, encountering errors, making design decisions, or working in unfamiliar code. Searches past solutions and engineering principles captured by compound-capture to surface institutional knowledge and prevent repeated mistakes. Trigger phrases include "have we seen this…
Skill Claude CodeCodex
Part of agent-skills
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a session ID, Claude Code session/transcript, PR, branch, log, or run summary.
Skill Claude CodeCodex
Part of agent-skills
Use always when operating as Claude Fable on codebase-heavy or token-heavy work: Fable orchestrates, architects, synthesizes, and judges while cheaper subagents do bounded research, coding, testing, and log reduction.
Skill Claude CodeCodex
Part of agent-skills
Use whenever running a high-cost frontier model on codebase-heavy or token-heavy work (apply automatically on such models): delegate research, coding, testing, and log reduction to cheaper subagents, reserving the expensive model for planning, tradeoffs, synthesis, and final review.
Skill Claude CodeCodex
Part of agent-skills
Save agent-skills workflow feedback proactively. MUST trigger when the user corrects how a visual plan/recap, recap status block, orchestration, autonomy, docs-first, or review skill behaves ("recaps are too long", "always web-search the docs first", "don't stop to ask", "plans should lead with the wireframe") or…
Skill Claude CodeCodex
Part of agent-skills
Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies.
Skill Claude CodeCodex
Part of agent-skills
Use when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done", "finish while I am away", "do not ask questions unless truly blocked", or similar. Convert ordinary ambiguity into stated assumptions, proceed…
Skill Claude CodeCodex
Part of agent-skills
Use when the user wants every response to end with a clear status signal — "give me a status line", "use the red/yellow/green convention", "end with a recap" — or when installing the managed AGENTS.md/CLAUDE.md status-block instruction.
Skill Claude CodeCodex
Part of agent-skills
Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift…
Skill Claude CodeCodex
Part of agent-skills
Use before substantial work and between parallel agent waves — especially overnight batch runs or multi-wave parallel subagents that might exhaust the 5-hour or weekly usage window — to check usage, pause near the cap, and resume only when the window is clear.
Skill Claude CodeCodex
Part of agent-skills
Use when turning a plan into a self-contained interactive HTML document (diagrams, file maps, annotated code, wireframes, open questions) saved locally and opened in the browser — no account or external service.
Skill Claude CodeCodex
Part of agent-skills
Use when turning a PR/branch/commit diff into a self-contained interactive HTML recap (annotated diffs, file maps, API/schema summaries, wireframes) saved locally and opened in the browser.
Skill Claude CodeCodex
Part of autoloop
MUST use when the user wants autonomous, iterative optimization — letting Claude run experiments unattended. Trigger: "autoloop", "autoresearch", "experiment loop", "hill-climbing", "optimize overnight", "karpathy loop", "let Claude optimize while I sleep", "automate trying different approaches", "set up a loop to…
Skill Claude CodeCodex
Part of autonomous-sdlc
Use AFTER bdd-spec has produced acceptance criteria, or when the user has existing Given/When/Then scenarios that need pytest-bdd scaffolding. MUST NOT run without existing acceptance criteria — invoke bdd-spec first if none exist. Trigger: "generate feature files", "scaffold BDD tests", "wire up pytest-bdd", "make…
Skill Claude CodeCodex
Part of autonomous-sdlc
Use INSTEAD OF superpowers:brainstorming when the user wants structured acceptance criteria in Given/When/Then format. This is the right choice when requirements need to be testable — not just designed. Trigger: "spec this out", "acceptance criteria", "BDD", "behavior driven", "what should happen when", "edge cases"…
Skill Claude CodeCodex
Part of autonomous-sdlc
MUST use when creating, updating, or closing Beads issues via bd commands. Use proactively when starting work (bd update --status=inprogress) and completing work (bd close). Trigger: any mention of "issue", "task tracking", "what should I work on", "bd create/ready/close", or when the session hook indicates beads is…
Skill Claude CodeCodex
Part of autonomous-sdlc
The autonomous-sdlc state machine. Loaded by every /sdlc loop iteration to decide what one unit of work the current state requires, how to verify it, and which transition to record. Trigger: an active .sdlc/state.json exists, or the /sdlc command invokes it. Not for ad-hoc use outside a loop.
Skill Claude CodeCodex
Part of autonomous-sdlc
Python-specific TDD wrapper. Use INSTEAD OF superpowers:test-driven-development when the project uses uv + pytest. Adds: feedback loading from autonomous-sdlc, uv run pytest commands, test directory organization (unit/integration/e2e). Delegates core TDD discipline to superpowers:test-driven-development. Trigger…
Skill Claude CodeCodex
Part of compound-knowledge
Capture this solution NOW — use immediately after solving non-trivial problems, completing debugging sessions, or when the user confirms something works ("that worked", "it's fixed", "finally"). Do NOT wait to be asked — if a debugging session just ended successfully, proactively invoke this. Also trigger on…
Skill Claude CodeCodex
Part of compound-knowledge
Promote accumulated knowledge into living context. Use when the user says "graduate knowledge", "promote lessons", "update CLAUDE.md from what we've learned", "what should be in my CLAUDE.md", "compound graduate", "improve the system from my notes", or after a run of captures when patterns recur. Scans the read corpus…
Skill Claude CodeCodex
Part of compound-knowledge
MUST check before starting any debugging session, investigating unfamiliar code, or planning a feature that might have been attempted before. Searches past solutions in knowledge/solutions/ to prevent repeated mistakes. Designed to be fast (<30s). Trigger proactively: before ANY bug investigation, before implementing…
Skill Claude CodeCodex
Part of hexagonal-agents
MUST use when building web apps where an AI agent generates HTML UI dynamically. Use INSTEAD OF superpowers:brainstorming or impeccable:frontend-design when the architecture is agent-driven (Claude Agent SDK + FastAPI + HTMX). Trigger: "build an agent app", "AI-driven web UI", "hexagonal architecture", "ports and…
Skill Claude CodeCodex
Part of mochi-creator
MUST use when the user mentions flashcards, Mochi, spaced repetition, memorization, studying, or wanting to remember something. Trigger proactively when the user says "I want to remember this", "make flashcards", "create Mochi cards", "help me study", "turn this into flashcards", "SRS", "Anki", or "I need to memorize…
Skill Claude CodeCodex
Part of observability-harness
Install a local, Docker-free OTLP observability stack (OpenTelemetry → Vector → JSONL files, optionally VictoriaLogs + VictoriaMetrics) into a project, and instrument the code to emit traces, metrics, and logs. Use this whenever the user wants observability, telemetry, tracing, metrics, or structured logging in a…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: