Loading...
Loading...
Found 2,149 Skills
Analyze CLAUDE.md files for token bloat and suggest optimizations
Build a persistent knowledge graph of your codebase so Claude reads only what matters — up to 49x fewer tokens on coding tasks.
A validation framework that ensures Claude's responses are current, accurate, complete, and clear. Use this skill whenever the user asks a factual or research question, requests analysis or recommendations (e.g., "What's the best framework for X?", "Compare options for Y"), or any prompt where recency and accuracy matter. Also trigger when the user explicitly asks for validated, verified, or fact-checked answers. This skill should activate broadly — if the answer depends on facts that could have changed in the last few months, use it. Even questions that seem straightforward ("Is X still the recommended approach?") benefit from this skill's validation pipeline. Do NOT trigger for purely creative writing, casual chat, or tasks that are entirely opinion-based with no factual claims.
Deploy and configure CC Gateway, a reverse proxy that normalizes Claude Code device fingerprints and telemetry for privacy-preserving API proxying
Use OpenAI Codex from inside Claude Code for code reviews and delegated background tasks.
Agent harness architecture — structure a project's agent context across layers for effective AI-assisted development. Covers CLAUDE.md, skills, design docs, hooks, and all artifacts that shape how an agent understands and operates in a codebase. Use when setting up or improving a project's agent configuration, when agent context feels bloated or disorganized, when onboarding a new project for AI-assisted development, or when the agent keeps losing architectural awareness mid-task. Trigger on phrases like "set up claude", "improve CLAUDE.md", "agent keeps forgetting", "context is too long", "harness setup", "organize agent context", "how should I structure my prompts". Supports arguments: `/harness audit` to evaluate an existing project's context architecture, `/harness init` to set up harness from scratch.
Use when acting as a project manager that delegates tasks to other Claude Code sessions - launch workers, assign them work, monitor progress, review their tool calls, and collect results
Promote entries from the current project's .claude/settings.local.json into the global ~/.claude/settings.json. Use when user says "promote settings", "upgrade settings", "sync settings to global", "move local settings to global", or wants to move project-local Claude Code settings to global scope.
Discover session files for a repo across Claude Code, Codex, and Cursor, and extract session metadata (timestamps, branch, cwd, size, platform). Invoked by session-research agents — not intended for direct user queries.
Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration
Run Ruflo background workers using Claude Code native /loop scheduling
[Hyper] Use when the user explicitly wants Anthropic Claude Code CLI (`claude`) for an isolated session, non-interactive (`-p`) run, session resume by ID or name, or a CI-friendly `--bare` invocation. Trigger phrases: "use claude code", "ask claude", "run claude", "continue the last claude session", "resume the auth-refactor claude session", or "use Anthropic's CLI to inspect or fix this repo".