Curated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.
This repository also configures its own agents. See what agents tells them →
Skill Claude CodeCodex
Multi-perspective codebase survey that produces beads and mermaid diagrams from code structure. Each agent perspective (prod, staging, dev, feature, PM) examines the same codebase at a different zoom level, creating tagged beads and a disagreement matrix.
Skill Claude Code
Wire validation so local == CI by construction: every check is a Taskfile target; CI and hooks invoke it rather than reimplementing it. Use when adding a validation gate, when local/CI disagree, or when a hook duplicates a command.
Skill Claude Code
Hunt vacuous / low-fidelity tests — the ones that pass whether or not the code is wrong in the way they claim to catch. Probes four shapes: a double that dodges the real thing, an assertion too loose to constrain behavior, inputs that never reach the claim, and coverage that is claimed but not guaranteed. Uses…
Skill Claude Code
Decompose feature work into reviewable, shippable PR-sized units before coding starts. Use for a ticket, a feature description, or before a multi-file change. Feeds writing-plans — each unit becomes a plan.
Skill Claude Code
Mine the user's Claude Code chat corpus for self-optimization patterns — repeated corrections, tool thrash, dropped threads — into a ranked, PII-scrubbed report. Different from self-audit (PR code review). Dispatch as a sub-agent to keep context clean.
Skill Claude Code
Before opening a PR, enumerate every behavior it claims — stated, callers- unaffected, invariants-preserved — and tag each with the strongest evidence actually held: RAN, READ, or ASSUMED with a closed-set reason. Ship the ASSUMED residue in the PR description; log harness blockers durably. After review, reconcile…
Skill Claude CodeCodex
Use when asked whether a repo's architecture is still right — a counterfactual "how would this be designed today?" question, a suspicion of over/under-engineering or monolith-vs-split, recurring bug families that smell structural, or before committing to a major refactor. Read-only, evidence-first, multi-pass; "the…
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: