Loading...
Loading...
Found 3,203 Skills
Create or edit Claude Code skills with expert guidance on structure and best practices
Orchestrate teams of parallel Claude Code sessions working on the same codebase. Handles task decomposition, agent coordination, context isolation, and merge strategies. Builds on worktree-manager for infrastructure.
Translate entire books (PDF/DOCX/EPUB) into any language using Claude Code parallel subagents with resumable chunked pipeline
Audit your Claude Code setup for prompt caching efficiency. Measures prefix size, hook patterns, rule duplication, dynamic injection sizes, and tool stability. Use when asked to 'check caching', 'optimize prompt cache', or 'audit setup efficiency'. Returns a scored report with fixes ranked by token savings.
Step-by-step cookbook for setting up cryptographically signed audit trails on Claude Code tool calls. Use when explaining, evaluating, or demonstrating the pattern before committing to the protect-mcp runtime hooks. Covers Cedar policy, Ed25519 receipts, offline verification, tamper detection, CI/CD integration, and SLSA composition.
Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2) graduating a pattern from notes to enforced rules, (3) turning a debugging solution into a skill, (4) checking memory health and capacity.
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).
AI-assisted TradingView chart analysis and automation via Chrome DevTools Protocol for Claude Code
Audit the Claude Code ecosystem — skill health and staleness, project activity pulse, CLAUDE.md instruction drift, Mac Mini service status. Use this skill whenever the user asks about ecosystem health, stale skills, abandoned projects, system status, infrastructure check, "what's broken", "what's stale", "how's my setup", or any request to review the state of their Claude Code environment. Also triggers on "/ecosystem", "audit my ecosystem", "ecosystem health", "ecosystem audit".
Configure HUD display options (layout, presets, display elements)
Friendly onboarding when users ask about capabilities
Transform conversations and ideas into structured technical specifications. Outputs: User stories, acceptance criteria, technical requirements, edge cases. Use when user wants to document requirements before coding. Triggers: write spec, create user stories, document requirements, /spec