Loading...
Loading...
Found 6,678 Skills
This skill should be used when the user wants to review code, audit a diff, get a second opinion on changes, or run an adversarial review of files in the current working tree. Common triggers include "review this code", "audit this diff", "find issues in", "second opinion on this", "harsh review of", "adversarial review", and "security review of". Picks one or more reviewer personas (adversarial, security, architecture, performance). Reviews local files, `git diff`, or `git diff --staged` only — does not fetch external content. Runs in one of four modes: single-agent (one persona in the current agent), cross-model handoff (independent second opinion via another local AI CLI, with secret-shield preflight + prompt-shield wrap), multi-bg-agent (one persona per parallel background subagent), or agent-team (Claude Code Teams or equivalent on supporting agents). Skip when the user wants formatting fixes (use a linter) or refactoring patterns (use ts-best-practices or ts-best-practices-functional).
Covers the full meeting lifecycle for engineering managers — produces guidance on whether to schedule a meeting, how to run it well, how to protect team focus time, how to kill recurring waste, and how to evaluate a past meeting from a transcript or description. Use when the user says "too many meetings," "meetings are a waste of time," "how do I run this meeting," "meeting agenda," "meeting culture," "nobody comes prepared," "meetings go nowhere," "how do I decline meetings," "distractions," "focus time," "engineers can't focus," "context switching," "protect engineering time," "review this meeting," or "transcript."
Curate, install, and manage Codex skills from the awesome-codex-skills collection for AI coding agents.
Disciplined spec-driven test-driven development workflow for building software with AI coding agents. Transforms ambiguous requests into verified implementations through structured specification, test derivation, and strict TDD. Handles greenfield projects, brownfield enhancements (with or without existing tests), refactors, and complex bug fixes with workflow-specific guidance for each. Use when the user requests a new feature, module, enhancement, refactor, API, data pipeline, CLI tool, or system with multiple requirements, edge cases, or unclear specifications. Also use for complex bug fixes requiring root cause analysis. Triggers on phrases like "add a feature", "implement", "build a new module", "build an API", "build a CLI", "build a data pipeline", "refactor", "fix this bug", "write tests for", "TDD", "test-first", "the requirements are unclear", "characterization tests", or "spec this out". Triggers when modifying code with adjacent test files (`tests/`, `*_test.py`, `*.test.ts`, `*.spec.ts`, `spec/`, `__tests__/`) or test framework config (pytest.ini, jest.config.*, go.mod with testing imports, Cargo.toml with [dev-dependencies], package.json with a test script). Triggers when the user mentions edge cases, invariants, acceptance criteria, EARS notation, or red-green-refactor. Do NOT use for simple one-line fixes, cosmetic changes, formatting, renames, dependency bumps, or tasks where requirements are already fully specified with tests provided.
Local-first AI coding agent powered by llama.cpp with zero tokens costs, Docker sandboxing, 20 built-in tools, LSP/Roslyn intelligence, and MCP integration
Context layer for AI data agents - query warehouses accurately with semantic layers, metrics, and wiki knowledge through MCP
Multi-AI Agent P2P Debate. Suitable for technical solution stress testing, multi-perspective collision, and design decision convergence. Use it when you want a solution to be challenged or to understand the pros and cons of different technical routes. Triggered when mentioning "debate", "agent discussion", "multi-angle analysis", or "start a team".
Translates an image (or a set of image references — screenshots, mockups, Figma URLs, live websites) into two mirrored design-system artifacts: `docs/design.md` (YAML tokens + prose, following Google's open [design.md](https://github.com/google-labs-code/design.md) format, for the coding agent) and `docs/design.html` (a self-contained, token-driven style guide rendering every token and component live, for the human to read). Reads the imagery, asks targeted clarifying questions, derives the design tokens (colors, typography, spacing, rounded, components), and writes both files. Fully standalone — requires no other document or skill. Use when the founder says "create a design system", "design from image", "translate image to design", "create design.md", "image to design system", "extract design tokens", or shares an image with no other clear intent.
EV Charging Domain (evcharge): Read-only access to charging station list/details, charging pile (including gun port) list, station operation data statistics, and charging order list/details. Use this when users need to query charging stations, charging piles, gun port status, charging orders, operator (agent) operation data/charging revenue/electricity fees, or charging assets by operator account, mobile number, or station code. Trigger words: charging station, charging pile, charging gun/gun port, charging order, operator account, agent, charging revenue, charging electricity, electricity fee/service fee, evcharge, plotCode, useraccount. Note: The charging module is an independent platform module that reuses the same signature authentication; the actual order status is dual-dimensional: chargeStatus (charging status) + orderState (order status), which is inconsistent with the orderStatus English enumeration in the docking document (follow the actual platform measurement). For parking (non-charging) fee inquiry/records/monthly tickets/coupons, please use other openydt domain skills.
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTED_SOURCES_ENVIRONMENT_MISMATCH appears; or when choosing between `vercel curl` and the `x-vercel-trusted-oidc-idp-token` header.
Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run. USE FOR: editing, adding, or reviewing any file under .github/workflows/, writing run-name/name/if/env/run values that contain ${{ }} expressions, diagnosing a run that fails with 'This run likely failed because of a workflow file issue' and no jobs starting, deciding when a workflow scalar must be quoted, validating workflows with actionlint. DO NOT USE FOR: authoring application YAML unrelated to GitHub Actions, Azure Pipelines, GitLab CI, or non-workflow YAML. SCOPE: this skill covers *syntactic/structural* correctness of workflow YAML (quoting, parsing, actionlint); for *semantic and functional* workflow design (what a workflow should do, agentic-workflow behavior), see .github/agents/agentic-workflows.agent.md — the two are complementary. INVOKES: actionlint (downloaded pinned binary) plus git/grep for inspection.
Follow the Specture System for spec-driven development. Use when creating, implementing, validating, or migrating specs and agent execution plans.