skills

In the author's own words, from each skill's SKILL.md.

• eval-skills

  Eval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each example input, grade the artifact against the expected outcome, and let the gaps drive the edits. Use when the user wants to test/eval/improve/harden a skill, says "this skill keeps producing X / keeps missing Y", or hands a skill plus example input→expected-output pairs. Pairs wit…

  skills/authoring/eval-skills/SKILL.md on GitHub (opens in a new tab)

• write-skills

  Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.

  skills/authoring/write-skills/SKILL.md on GitHub (opens in a new tab)

• audit-choices

  Audit the choices an implementing agent made, not its diff — a pure decision audit that traces the session's history into a choices ledger, changes no code, and never blocks an unsupervised run. Working code still embeds architecture the user never chose; surface it because future work inherits it. Use when the user wants to review the decisions the AI made on their behalf, before merging or comm…

  skills/engineering/audit-choices/SKILL.md on GitHub (opens in a new tab)

• audit-performance

  Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find performance issues, investigate freezes/500s/OOMs, review retries or polling for no-progress loops, rank a performance backlog, or implement the next simple performance fixes.

  skills/engineering/audit-performance/SKILL.md on GitHub (opens in a new tab)

• auto-research

  Run fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts, configurations, or other artifacts against a goal or benchmark, or when a long research run needs a planned hypothesis queue, focused trials, and durable findings.

  skills/engineering/auto-research/SKILL.md on GitHub (opens in a new tab)

• claude

  Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent opinion from Claude, or asks to delegate a well-scoped task to Claude. Supports selecting `--model` and thinking/effort level with defaults of `opus` and `high`.

  skills/engineering/claude/SKILL.md on GitHub (opens in a new tab)

• close-spec

  When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec…

  skills/engineering/close-spec/SKILL.md on GitHub (opens in a new tab)

• code-review

  Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.

  skills/engineering/code-review/SKILL.md on GitHub (opens in a new tab)

• codex

  Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user explicitly asks for Codex to do it. Also covers how to prompt Codex.

  skills/engineering/codex/SKILL.md on GitHub (opens in a new tab)

• eli5

  Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works, and every schema change.

  skills/engineering/eli5/SKILL.md on GitHub (opens in a new tab)

• explore-unknowns

  Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a refe…

  skills/engineering/explore-unknowns/SKILL.md on GitHub (opens in a new tab)

• implement-spec-with-codex

  Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.

  skills/engineering/implement-spec-with-codex/SKILL.md on GitHub (opens in a new tab)

• implement-spec

  Implement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints to periodically clean code, handoffs, priorities, and plan bloat before drift accumulates.

  skills/engineering/implement-spec/SKILL.md on GitHub (opens in a new tab)

• marketing-pages

  Best-practice rulebook for a marketing site's pages, organized by page class — campaign landers, product pages, programmatic SEO trees, editorial. Use when writing or updating a landing/marketing page, wiring a campaign lander to an attribution identifier, changing site-wide nav/footer links, touching sitemap/robots/agent-readable surfaces, or auditing a public site's indexing, reachability, and…

  skills/engineering/marketing-pages/SKILL.md on GitHub (opens in a new tab)

• refactor-clean

  Refactor cleanly instead of layering sediment. Use when a change reveals duplicated concepts, local adapters, obsolete owners, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.

  skills/engineering/refactor-clean/SKILL.md on GitHub (opens in a new tab)

• review

  Closeout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-revi…

  skills/engineering/review/SKILL.md on GitHub (opens in a new tab)

• write-docs

  Write and edit project docs (README/markdown) as a glossary of principles, not a mirror of the code. Use when creating or revising a README; when a doc enumerates exact scenes, scenarios, helpers, class ids, file lists, or command/flag matrices the code already holds; when trimming narrative or changelog out of a doc; or when deduplicating overlapping docs and wiring a root doc to its sub-docs.

  skills/engineering/write-docs/SKILL.md on GitHub (opens in a new tab)

• write-spec

  Break large features into independently verifiable, human-reviewable slices under a feature directory in specs/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices befo…

  skills/engineering/write-spec/SKILL.md on GitHub (opens in a new tab)

• write-tests

  Write tests that pin real behavior instead of implementation details, config values, or lucky samples. Use when adding tests for new behavior, writing a regression test, fixing a brittle or flaky test, reviewing a test diff, or when a test breaks after a refactor or config change that didn't change behavior.

  skills/engineering/write-tests/SKILL.md on GitHub (opens in a new tab)

• renderer

  Build, debug, or review WebGPU renderer work — three.js/TSL scene layers, node materials, or raw WGSL passes and compute. Use when changing GPU resource layouts, render or compute passes, node materials, bind groups, buffers, shaders, frame orchestration, depth/overlay composition, capability handling, performance, or browser-verified renderer visuals.

  skills/graphics/renderer/SKILL.md on GitHub (opens in a new tab)

• compare-screenshots

  Compare screenshots to judge which image is less wrong, not to match a baseline. Use when a UI, game, document, render, chart, or generated asset needs objective visual telemetry, side-by-side inspection, crop/zoom review, or a fresh second opinion before accepting or rejecting a visual change. Also use on a single capture with no counterpart, to measure whether the frame is flat, empty, or badly…

  skills/visual/compare-screenshots/SKILL.md on GitHub (opens in a new tab)

• preview-shots

  Open image shots (screenshots, snapshot baselines, montages, renders) in ONE macOS Preview window so the user can eyeball them. Use when the user asks to open / show / pull up / review shots in Preview or Finder, or right after producing visual artifacts the user should look at before signing off.

  skills/visual/preview-shots/SKILL.md on GitHub (opens in a new tab)

• screenshot-critique

  Use the unprimed sub agent as a second set of eyes before accepting visual work — MANDATORY before declaring any user-reported visual bug fixed or claiming a visual change verified; primed eyes pass defects fresh eyes catch.

  skills/visual/screenshot-critique/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• gentle-aiby Gentleman-Programming Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more. Choose persistent memory, Or… 7.8k stars · 20 skills
• evoby evo-hq turns your codebase into an autoresearch loop — discovers what to measure, instruments the benchmark, then runs tree search with parallel s… 1.5k stars · 7 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 97.3k stars · 13 skills
• archifyby tt-a1i Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more. 84.1k stars · 2 skills