Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
refine-spec
Iteratively review and revise a specification document until no new findings survive evaluation. Runs /review-spec, /evaluate-findings, /apply-findings, then re-runs itself until stable. Use when the user asks to "refine the spec", "refine this spec", "iterate on the spec", "tighten the spec", or "improve the spec".
tobihagemann/turbo 261
-
apply-findings
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note skipped genuine improvements. Use when the user asks to "apply findings", "apply fixes", "apply suggestions", "apply accepted findings", "fix the findings", or "apply the review results".
tobihagemann/turbo 261
-
map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map the codebase", "map codebase", "architecture report", "codebase overview", "architecture overview", "what am I looking at", or "explain this codebase".
tobihagemann/turbo 261
-
codex-exec
Run autonomous task execution using the codex CLI. Use when the user asks to "codex exec", "run codex exec", "execute a task with codex", or "delegate to codex".
tobihagemann/turbo 261
-
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
tobihagemann/turbo 261
-
onboard
Developer onboarding guide that composes architecture mapping, tooling review, and agentic setup review with setup, troubleshooting, and next-steps agents to produce a comprehensive guide at .turbo/onboarding.md and .turbo/onboarding.html. Use when the user asks to "onboard me", "onboard to this project", "generate onboarding guide", "new developer guide", "how do I get started", or "help me ramp up".
tobihagemann/turbo 261
-
implement-improvements
Plan and implement improvements from the .turbo/improvements.md backlog after validating them against the current codebase. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement backlog", "tackle improvements", or "implement noted improvements".
tobihagemann/turbo 261
-
mobile-dev-server-sandbox
Connects Mux mobile (Expo web/native) to an isolated dev-server sandbox with deterministic port setup, backend pairing, and Chrome MCP interaction. Use when implementing or validating mobile features against a sandboxed Mux backend.
coder/mux 1,629
-
dev-desktop-sandbox
Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)
coder/mux 1,629
-
generate-readme-screenshots
Regenerate high-resolution README screenshots from Storybook stories. Use this skill when Chromatic detects visual diffs in any story under "Docs/README Screenshots", or when story data/layout changes require updated documentation assets. Triggers on: Chromatic visual regressions in readme screenshot stories, changes to App.readmeScreenshots.stories.tsx, changes to mockFactory.ts that affect screenshot stories, or explicit user request to update README images.
coder/mux 1,629
-
react-effects
Guidelines for when to use (and avoid) useEffect in React components
coder/mux 1,629
-
pull-requests
Guidelines for creating and managing Pull Requests in this repo
coder/mux 1,629
-
tbench
Terminal-Bench integration for Mux agent benchmarking and failure analysis
coder/mux 1,629
-
tests
Testing doctrine, commands, and test layout conventions
coder/mux 1,629
-
dev-server-sandbox
Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports)
coder/mux 1,629
-
deep-review
Sub-agent powered code reviews spanning correctness, tests, consistency, and fit
coder/mux 1,629
-
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
coder/mux 1,629
-
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
coder/mux 1,629
-
byethrow
Reference the byethrow documentation to understand and use the Result type library for error handling in JavaScript/TypeScript. Access detailed API references, practical usage examples, and best practice guides.
ryoppippi/ccusage 12,748
-
use-gunshi-cli
Use the Gunshi library to create command-line interfaces in JavaScript/TypeScript.
ryoppippi/ccusage 12,748
-
using-forgetful-memory
Guidance for using Forgetful semantic memory effectively. Applies Zettelkasten atomic memory principles. Use when deciding whether to query or create memories, structuring memory content, or understanding memory importance scoring.
ScottRBK/forgetful 249
-
curating-memories
Guidance for maintaining memory quality through curation. Covers updating outdated memories, marking obsolete content, and linking related knowledge. Use when memories need modification, when new information supersedes old, or when building knowledge graph connections.
ScottRBK/forgetful 249
-
exploring-knowledge-graph
Guidance for deep knowledge graph traversal across memories, entities, and relationships. Use when needing comprehensive context before planning, investigating connections between concepts, or answering "what do you know about X" questions.
ScottRBK/forgetful 249
-
using-forgetful-memory
Guidance for using Forgetful semantic memory effectively. Applies Zettelkasten atomic memory principles. Use when deciding whether to query or create memories, structuring memory content, or understanding memory importance scoring.
ScottRBK/forgetful 249