Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 33451–33480 of 35193 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| ship-levelcodezeroexe/levelsAudit how reliably a project gets from code to a running product against a 5-level release maturity scale (build, configuration, deploy, rollback, monitoring, backups), propose options, then split the chosen work into sub-plans delegated to Haiku or Sonnet while Opus plans and reviews. Use when the user runs /ship-level or asks to prepare, audit or harden a release or deployment. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| test-levelcodezeroexe/levelsAudit how well a project proves it works against a 5-level testing maturity scale, find untested critical paths and weak tests, propose options, then split the chosen work into sub-plans delegated to Haiku or Sonnet while Opus plans and reviews. Use when the user runs /test-level or asks to rate, audit or improve tests. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| ux-levelcodezeroexe/levelsAudit how easily real users complete their tasks against a 5-level usability scale, by walking each key task as a first-time user and checking flow, feedback, error recovery and wording, then propose options and split the chosen fixes into sub-plans delegated to Haiku or Sonnet while Opus plans and reviews. Covers behaviour and flow, not visual style. Use when the user runs /ux-level or asks to audit or improve usability, flows, onboarding or interface wording. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| <name>-levelcodezeroexe/levelsAudit <what part of a project> against a 5-level <what the scale measures> scale, propose options, then split the chosen work into sub-plans delegated to Haiku or Sonnet while Opus plans and reviews. Use when the user runs /<name>-level or asks to <the requests that should trigger it>. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| Git Commit Helpershyinlim/claude_setting_managerGenerate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| mcp-buildershyinlim/claude_setting_managerGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| brandvoicejaimeschwarz/brandvoiceBuild a living, governed brand voice through the Brand Therapy discipline — an eight-stage process that treats a brand as the relational space between a company and its consumer. Use this skill whenever the user wants to create a brand voice, define a brand identity, build a brand persona, establish brand governance, or articulate what their brand actually sounds like. Also trigger when users say "brand voice", "brand identity", "who is my brand", "brand persona", "brand guidelines", "brand therapy", or ask for help making their brand feel coherent, consistent, or governed. This skill goes far beyond typical brand voice exercises — it builds a governed voice that can hold itself together under pressure, across channels, over time, and then turns it on. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| cfqmCuppaTea1983/cfqmKeeps this project's CFQM.md true. CFQM.md is the session memory that the cfqm hooks print back into the session after every compaction, resume and clear. Use when a "[cfqm]" nudge appears, when the restore says NOW was not rewritten, at a milestone (something finished, a decision made, the plan changed), when the user says something about themselves or how to work that should outlast this session, before a long session ends, or when the user runs /cfqm. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| ai-native-developmentjacob-balslev/skillsUse when reasoning about agent autonomy levels, designing auto-improve loops, evaluating AI-generated code quality, or measuring agent productivity in an LLM-assisted codebase. Covers Karpathy's three eras of software (1.0 explicit / 2.0 learned / 3.0 natural-language), the vibe-coding-vs-agentic-engineering distinction, the 0–5 autonomy slider with task-type recommendations, the one-asset / one-metric / one-time-box AutoResearch loop, Software 3.0 productivity metrics, and the documented quality regressions of ungated AI-generated code (the 'vibe hangover'). Do NOT use for choosing a specific autonomy-loop topology (use `agent-engineering`), for the per-prompt authoring discipline (use `prompt-craft`), or for reviewing the AI-generated code that comes out of a Software 3.0 workflow (use `code-review`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| autonomous-loop-patternsjacob-balslev/skillsUse when designing, reviewing, or debugging an autonomous AI agent loop: repeated agent execution, completion signals, checkpoints, supervisor respawn, stall detection, safety caps, and human handoff rules. Covers the core loop patterns from simple bounded runs through sentinel-based continuation, checkpoint-resume, and external supervisor loops. Do NOT use for choosing a specific agent product command (use agent-engineering or the product's docs), writing ordinary task instructions (use prompt-craft), or optimizing individual tool calls (use tool-call-strategy). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| claude-codejacob-balslev/skillsUse when deciding whether to run a task in the Claude Code agent harness, when scoping work to its native capabilities (skills, hooks, subagents, MCP, plan mode, 1M-context Opus, background tasks, slash commands), or when choosing Claude Code versus a different harness (Codex, OpenCode, Copilot) for a given piece of work. Covers what the harness is good at, the extensibility stack and when each layer earns its keep, and the decision boundaries against rival harnesses. Do NOT use for writing Anthropic SDK / API code (use `claude-api`), for choosing which Claude MODEL to route a task to versus GPT (use `gpt-5-5`), or for designing a generic autonomous agent loop (use `autonomous-loop-patterns`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| claude-haikujacob-balslev/skillsUse when deciding whether to route a task to the fast/cheap tier (Claude Haiku) — transcription, polling, format conversion, structured-output slot-filling, small-diff review, high-volume low-latency work — and where the boundary is that should escalate to Sonnet/Opus. Covers the cost/latency floor, the 200K context ceiling (vs the upper tiers' 1M), the absence of the effort knob, the separate rate-limit pool, and when to drop below Haiku to a script. Do NOT use for ordinary multi-step feature work (use claude-sonnet), the hardest reasoning (use claude-opus), loop design (use autonomous-loop-patterns), or Claude API request syntax (read the claude-api reference). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| claude-opusjacob-balslev/skillsUse when deciding whether to route a task to Anthropic's frontier reasoning tier (Claude Opus) — architecture, multi-file synthesis, hard debugging, security reasoning, long-horizon agentic planning — and when NOT to (mechanical work belongs on a cheaper tier). Covers the Opus capability profile: 1M-token context, the cost/latency premium, adaptive thinking, the Opus-only effort ceiling (xhigh/max), task budgets, prompt-caching minimums, and high-resolution vision. Do NOT use for picking the balanced implementation tier (use claude-sonnet), the fast/cheap tier (use claude-haiku), designing the loop the model runs inside (use autonomous-loop-patterns), or for Claude API request syntax (read the claude-api reference). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| claude-sonnetjacob-balslev/skillsUse when deciding whether to route a task to the balanced implementation tier (Claude Sonnet) — feature work, bug fixes, test writing, multi-step code — as the default lane that is cheaper/faster than the frontier tier and more capable than the fast tier. Covers the cost/quality tradeoff vs Opus and Haiku, the shared 1M context window, effort behavior, and the 1M-context subscription billing caveat. Do NOT use for the hardest reasoning/architecture/security work (use claude-opus), high-volume mechanical or low-latency work (use claude-haiku), loop design (use autonomous-loop-patterns), or Claude API request syntax (read the claude-api reference). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| codexjacob-balslev/skillsUse when deciding whether to run a task in the Codex CLI agent harness (which drives a frontier GPT model), when scoping work to its native capabilities (resumable `codex exec resume` sessions, non-interactive `exec` stdout-piping, in-process dispatch, `/permissions` sandbox modes, MCP, on-demand subagents, the `/review` code-review agent), or when choosing Codex versus the Claude Code harness for a piece of work — and when avoiding its known failure modes (non-autonomous subagents, Full-Access network reach, cold-one-shot context loss). Do NOT use for routing a task to the GPT MODEL versus Claude (use `gpt-5-5`), for the Claude Code harness decision (use `claude-code`), or for designing a generic resumable agent loop (use `autonomous-loop-patterns`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| content-monitorjacob-balslev/skillsUse when building or operating multi-source intelligence pipelines across video, GitHub, Reddit, curated lists, search, and RSS feeds. Covers source adapters, discovery/transcription/summarization/evaluation phases, deduplication, schedules, model-stage choice, and actionable brief generation. Do NOT use for SEO keyword research (use `keywords`) or competitive product analysis (use `user-research`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| context-engineeringjacob-balslev/skillsUse when designing what information reaches an LLM agent before it reasons — system prompt, persistent memory, always-loaded rules, injected skills, and the user prompt — or when diagnosing why an agent produced a wrong answer despite a clear instruction. Covers the four context failure modes (missing, stale, wrong, overwhelming), the five-layer context stack, four context quality metrics (injection precision and recall, utilization, freshness), the Frequent Intentional Compaction (FIC) protocol, subagent delegation for context-heavy work, and the failure-mode decision tree. Do NOT use for prompt wording (use `prompt-craft`), authoring a new SKILL.md (use `skill-scaffold`), or deciding which skill the router activates for a given query (use `skill-router`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| context-graphjacob-balslev/skillsUse when designing or auditing the multi-graph context architecture of an AI-coding workspace: skill graph, document routing graph, memory index, script registry, and the cross-graph edges between them. Covers edge typing, orphan detection, connectivity health, deterministic graph synthesis signals, change-propagation checks, and drift or hub-and-spoke anti-patterns. Do NOT use for authoring one SKILL.md (use `skill-scaffold`), validating one skill (use `skill-infrastructure`), live routing decisions (use `skill-router`), context-window budgeting (use `context-window`), or session load/drop choices (use `context-management`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| context-managementjacob-balslev/skillsUse when deciding what to load into an active agent session, recovering from context drift, preparing compaction or restart, distilling raw inputs into a working summary, or writing a handoff another agent can resume quickly. Covers intake triage, the active-context contract, the six-step context-management loop, working-set shaping, evidence capsules and observation masking, just-in-time handle-before-payload loading, prompt-caching alignment, context-rot defenses, drift signals and reset, the runtime-primitives boundary, compaction-ready handoffs, and selective rebuild after context loss. Do NOT use for token math (use `context-window`), prompt wording (use `prompt-craft`), persistent memory curation, or multi-graph context architecture (use `context-graph`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| context-windowjacob-balslev/skillsUse when allocating context-window budget across system, skill-injection, working, and output zones; monitoring context health; deciding when to compact; preserving state before compaction; recovering after compaction; or choosing strategies for 1M, 200K, or 128K context windows. Covers zone budgets, practical model-budget tables, the 80% compaction rule, pre/post-compact protocols, persistence hierarchy, operation token costs, and token-reduction techniques. Do NOT use for deciding what information belongs in the working set (use `context-management`), prompt design (use `prompt-craft`), graph architecture (use `context-graph`), or memory curation. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| gemini-projacob-balslev/skillsUse when deciding whether to route a task to Google's Gemini Pro frontier model (current Gemini 3.1 Pro generation, moving to Gemini 3.5 Pro) instead of Claude Opus or GPT-5 — especially for very-large-context reasoning (1M-token input), whole-codebase or long-document analysis, native multimodal input (audio/video/PDF/image in one call), or capability-per-dollar at the frontier. Covers the context window, the 200K context-tier pricing cliff, multimodal support, and the per-lane comparison against Claude Opus / GPT-5. Do NOT use for choosing the cheap/fast tier (use `gemini-flash`), for general agent-system architecture (use `agent-engineering`), or for dispatching among local skills (use `skill-router`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| github-copilotjacob-balslev/skillsUse when deciding whether to spend GitHub Copilot's metered budget on a task (its premium-request / post-June-2026 AI-credit model, where 1 credit = $0.01 and cost = tokens × per-model rate), what Copilot is good at vs expensive at, which plan allowance (Pro 300 / Pro+ 1500, no rollover) applies, and when a cheaper or free lane should take the work instead. Covers the June 1 2026 shift from premium-request multipliers to usage-based token billing, the always-free completions/next-edit surface, and the IDE-native frontier-model lane. Do NOT use for choosing or operating the OpenCode runtime (use `opencode`), for picking a specific free model (use `opencode-free-models`), or for authoring an agent loop (use `autonomous-loop-patterns`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| gpt-5-5jacob-balslev/skillsUse when deciding whether to route a task to OpenAI's GPT-5.5 frontier model versus Claude Opus or Sonnet — picking the model lane for infrastructure scripts, CI pipelines, concrete implementation, analytical code review, security review, or CLI/terminal-heavy work, and weighing GPT-5.5's context window, pricing, and per-benchmark strengths against the Claude tiers for the same task. Covers the decision-useful capability and pricing facts, and the boundary against the Claude routing skills. Do NOT use for running the GPT model through a harness (use `codex`), for choosing among the Claude tiers themselves (use `claude-opus` / `claude-sonnet`), or for routing among local skills at request time (use `skill-router`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| opencodejacob-balslev/skillsUse when deciding whether to run a task on the OpenCode agent runtime (the open-source, provider-agnostic coding agent — usable as a terminal TUI, a non-interactive `opencode run` CLI, an IDE bridge via ACP, a desktop app (beta), a web UI, or a headless `opencode serve` server), how to invoke it non-interactively, how to pick a `provider/model` string, or how OpenCode differs from Claude Code and Codex. Covers its 75+-provider model routing, the OpenCode Zen curated/free model service and the separate OpenCode Go subscription lane, model-selection and config-source (8-layer) precedence, the `--format json` JSONL event stream, the full CLI command surface (serve/web/attach/acp/session/stats/export/import/github/pr/plugin/mcp/db/debug), built-in build/plan agents and LSP code intelligence, permissions vs provider policies, native Agent Skills / MCP / references / commands extension layers, local models, and scripting/automation. Do NOT use when choosing WHICH free model to route specific work to (use `opencode-free-models`), when the runtime is already chosen and you only need to write the agent loop (use `autonomous-loop-patterns`), or for GitHub Copilot's premium-request economics (use `github-copilot`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| opencode-free-modelsjacob-balslev/skillsUse when deciding WHICH free or cheap agent model to route a piece of work to (e.g. MiniMax M3 Free, NVIDIA Nemotron, GLM, GPT-5 Nano, or another OpenCode Zen free-tier model), what each is good at, where its quality ceiling sits, and when to escalate the same work to a frontier model instead. Covers cost-routing: matching deterministic/mechanical/high-volume work to the cheapest model that clears its bar, and the hard rule that quality-creating and quality-judging work never goes to a free/cheap model. Do NOT use for choosing or operating the OpenCode runtime itself (use `opencode`), for authoring the agent loop (use `autonomous-loop-patterns`), or for GitHub Copilot premium-request budgeting (use `github-copilot`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| skill-infrastructurejacob-balslev/skillsUse when designing or auditing deterministic health tooling for a skill library: schema/source validation, manifest/protocol parity, relation integrity, routing health, drift/export checks, supply-chain scanning, and eval-verdict evidence honesty. Covers checker ownership, the library-as-database model, release gates, and maintenance workflows after batch skill changes. Do NOT use for authoring one SKILL.md (use `skill-scaffold`), repo conformance audits (use `graph-audit`), generic lint rules (use `lint-overlay`), or reviewing checker code (use `code-review`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| skill-routerjacob-balslev/skillsUse when routing an agent request across multiple skills, building or auditing a routing table, detecting routing coverage gaps, or answering questions like 'which skill handles this?', 'who routes X?', or 'why did skill A activate instead of B?'. Covers trigger-label matching, file-path matching, keyword matching, description-based semantic matching, project-fit filtering, relation-aware co-loading and exclusion, eval/staleness annotations, and coverage-gap detection. Do NOT use when the target skill is already known (load it directly), when authoring a new skill (use `skill-scaffold` instead), or when evaluating a SINGLE skill's quality (use `graph-audit`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| skill-scaffoldjacob-balslev/skillsUse when creating a new SKILL.md from scratch, restructuring a draft before it becomes a stable skill, or teaching another author the canonical Skill Metadata Protocol frontmatter, body, and audit-state.json sidecar structure. Covers flat schema-conformant frontmatter, the sidecar split, v8 classification, body layout by skill intent, semantic-layer discipline (description vs activation vs Coverage), teaching-layer mechanics (TEMPLATE NOTE blockquotes), native skill-creator handoff, public/private safety, and routing-eval honesty. Do NOT use when modifying an already-written skill (edit it directly), writing general technical documentation, routing an existing request across skills, or fixing malformed library health at scale (use `skill-infrastructure`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| eval-driven-developmentjacob-balslev/skillsUse when reasoning about building language-model-integrated systems by writing evaluations before and alongside the system: the statistical (not binary) nature of LLM evals, the five primitives (dataset, evaluation function, aggregation, iteration loop, regression budget), the judgment-mechanism taxonomy (programmatic, model-graded, human-graded, preference comparison, trace/hybrid), the eval-surface stack (final response, trajectory/tool-use, retrieval/RAG, safety, side effects, cost/latency), continuous evals and model-upgrade gates, the statistical-significance discipline (paired tests, McNemar's test, bootstrap CI on the delta, minimum-detectable-effect, clustered standard errors), trajectory-vs-final-output evaluation for multi-step agents, judge calibration and bias, Goodhart's Law and suite saturation, benchmark contamination and eval-awareness, cost-aware regression budgets, the difference between system-specific evals and canonical benchmarks (MMLU, HumanEval, BIG-bench, GAIA), and the offline-eval-vs-production-telemetry distinction with its graded rollout spectrum. Do NOT use for deterministic unit testing (use testing-strategy), production monitoring (use evaluation or error-tracking), general-software TDD (use testing-strategy), or the construction of individual eval rubrics and task sets (outside this skill; construction belongs in task-specific eval artifacts, while this skill owns the iteration discipline). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| evaluationjacob-balslev/skillsUse when scoring a completed agent task, implementation, document, skill upgrade, or other deliverable against the original request, acceptance criteria, verification evidence, quality rubric, and residual risks before calling it done. Covers skeptical critic review, 1-5 scoring, score ceilings, evidence sufficiency, finding/action capture, and the evaluation-revision loop. Do NOT use for designing eval datasets or graders (use eval-driven-development), line-by-line diff review (use code-review), choosing test levels (use testing-strategy), or designing the overall process and gates before work starts (use methodology). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |