Agent skills you can check before you install
Public SKILL.md skills from GitHub repositories with 50+ stars and from the vendors themselves, scanned and scored. Install any of them with one command in Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI.
36,618 skills from 1,661 repositories · updated 3 minutes ago
2,631 skills
- delivery-probe-echoNewzby/commonplaceProbe skill for the delivery test. Use only when asked to run the delivery-probe-echo check; takes one argument.TestingNo warnings★ 91↓ —
- delivery-probe-readzby/commonplaceProbe skill for the delivery test. Use only when asked to run the delivery-probe-read check.TestingNo warnings★ 91↓ —
- delivery-probe-delegatezby/commonplaceProbe skill for the delivery test. Use only when asked to run the delivery-probe-delegate check.TestingNo warnings★ 91↓ —
- smell-checkZhen-Bo/smell-checkRuns a smell-first audit on a user-chosen path set: measures structure metrics, applies a named size profile, and reports code smells and test smells with evidence strength. Use for smell audit, code smell scan, whole-repo audit, tech debt scan, test smell check, maintainability audit, or duplication and nesting checks. Do not use for PR review, merge advice, implementing fixes, writing new features, or lint/format-only passes.TestingNo warnings★ 240↓ —
- tdd-prdGulajavaMinistudio/awesome-copilot-idGenerates comprehensive Product Requirements Documents (PRDs) with BDD Given-When-Then acceptance scenarios, success metrics, and manages CONTEXT.md.TestingNo warnings★ 86↓ —
- cross-browser-qaTheGoat395/Codex-SkillsVerify browser-engine compatibility.TestingNo warnings★ 132↓ —
- zhangyi-probeaph199686/zhangyi-studio张翼验证探针：用只读模拟脚本对机制做结构性验证——假设预登记、种子与样本量协议、置信区间下界闸门、指标口径审查、独立复现。铁律：探针能否决结构问题，永远不能证明好玩。输出探针裁决书。Use when the user wants to simulate/test/verify a mechanic with data, run balance simulations, validate a design numerically, or asks whether a system will work. 用户想用数据模拟验证机制、跑平衡测试、做数值验证、或问'这个系统跑起来会怎么样'时使用。TestingNo warnings★ 119↓ —
- zhangyi-playtestaph199686/zhangyi-studio张翼试飞：真人玩家验证的设计、执行与解读——按研发节点路由该测什么、招募与样本甄别、深度访谈、体验走查、尖叫度测试、留存流失归因。天条：不伪造玩家声音，结论必带样本来源/样本量/口径三要素。输出试飞裁决书。Use when the user wants to playtest with real players, run user interviews, recruit testers, design a beta test, or interpret retention/feedback data. 用户想做真人试玩测试、玩家访谈、招募测试者、设计封测、或解读留存/反馈数据时使用。TestingNo warnings★ 119↓ —
- rust-best-practicesapollographql/skillsGuide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.TestingNo warnings★ 118↓ —
- ank-tddhaksolot/ankDrive an implementation test-first, red before green, against a claimed task's frozen criterion. Use when implementing a task in a repository with a .ank/ directory.TestingNo warnings★ 91↓ —
- mini-program-verification-skillNocodeMrLi/mini-program-engineering-skill-suiteVerify mini-program implementations and fixes with risk-calibrated evidence across static checks, unit tests, integration tests, state matrices, simulators, real devices, cloud environments, and release artifacts. Use when users ask to test, validate, accept, regression-check, quality-check, confirm readiness, or determine whether a mini-program feature is actually complete. Binds results to a source and build fingerprint, records commands and observable evidence, separates passed, failed, blocked, and not-run layers, prioritizes the next highest-information check, and never converts local success into device, cloud, release, or formal acceptance claims.TestingNo warnings★ 91↓ —
- tdditseffi/agentic-osTest-driven development - write failing test first, then minimal code. Use before implementing any feature or bugfix.TestingNo warnings★ 117↓ —
- assumption-prioritizationitseffi/agentic-osPrioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.TestingNo warnings★ 117↓ —
- lite-toolsejboy/agent-scriptsUse compact wrappers when running routine Maven builds and tests, supported npm/Node test workflows, or Go tests. Select mvn-lite for supported Maven build and test workflows, npm-lite for npm run verify, npm run test:unit, or node --test, and go-lite for go test.TestingNo warnings★ 117↓ —
- mini-program-implementation-skillNocodeMrLi/mini-program-engineering-skill-suiteImplement bounded features and fixes in existing or new mini-program codebases while preserving repository rules, user-owned changes, approved behavior, assets, framework conventions, and evidence boundaries. Use when users ask to write or modify mini-program code, implement a confirmed specification or architecture, add a scoped feature, remove behavior semantically, update internal documentation required by a change, or carry out a well-defined small fix that does not require root-cause investigation. Establishes a baseline and change boundary, applies test-driven small steps, distinguishes source from generators and build artifacts, verifies the affected contract, and never reports source completion as device validation, formal acceptance, upload, or release.TestingNo warnings★ 91↓ —
- mini-program-release-skillNocodeMrLi/mini-program-engineering-skill-suiteGovern mini-program release readiness and evidence across source branches, semantic versions, build artifacts, test flags, debug paths, sensitive data, permissions, privacy declarations, platform uploads, review submissions, staged versions, production releases, and rollback plans. Use when users ask for a release checklist, packaging, export, version bump, upload readiness, submission readiness, launch status, rollback preparation, or a precise judgment of what has and has not shipped. Defaults to read-only preflight, requires separate explicit authorization for every external state change, and never treats a Git push, successful build, platform upload, review submission, approval, or production publication as interchangeable.TestingNo warnings★ 91↓ —
- grillingGulajavaMinistudio/awesome-copilot-idGrill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.TestingNo warnings★ 86↓ —
- dif-triage-experimentsdif-sh/difTriage every running dif.sh experiment and rollout from the dif cloud overview. Shows what needs action, then ramps rollouts, turns off or kills harmful variants, and concludes winners and inconclusive tests by editing dif/ files, with one branch and one PR per experiment in autonomous mode. Use when the user asks to triage experiments, review all experiments, see what needs action, ramp, turn off, kill, find winners, or check the dif cloud overview.TestingNo warnings★ 114↓ —Also in 1 other repo
- dif-author-experimentdif-sh/difAuthoring and iterating on dif.sh experiments — drafting frontmatter, choosing variants and weights, declaring audiences, and validating the file. Use whenever the user wants to create, draft, edit, or fix a dif experiment, or mentions A/B test, variant, audience, hypothesis, surface, exclusion group, or the commands dif new, dif validate, or dif build.TestingNo warnings★ 114↓ —Also in 1 other repo
- ship-checkjoetawil7/first-passThe definition of done. Run before calling any change done, fixed, verified, ready or shippable, for features and bug fixes alike. Checks the pre-mortem was answered, proves the tests fail on the old code, gets a fresh breaker review, runs CI's own checks in a clean checkout, checks the user-facing words, and writes the evidence report. Also use when asked "is it done", "is it ready", "did you verify it" or "can we merge".TestingNo warnings★ 113↓ —
- quickjoetawil7/first-passQuick mode for the rest of the session. Instead of CI's full checks, a change runs only the checks it can affect (format, lint, types and build, its own tests, and every unit, integration, flow and browser test that reaches the code it touched), and the rest of the suite is left for a full run such as a pull request's CI. Runs only when the user types it, and `/first-pass:quick off` turns it off.TestingNo warnings★ 113↓ —
- fix-the-classjoetawil7/first-passBug-fix routine that fixes the whole class of bug, not just the reported instance. Use for any bug report, failing production behaviour, monitoring alert, audit finding or review finding that does real harm (a smaller review finding goes on the item's list, as ship-check says), and whenever the same kind of bug has been seen before. Reproduces it with a failing test, names the failure class, searches the task's scope for the same pattern (the whole codebase when the user's own prompt asks for the fix, not when it is picked from a task's list), fixes or records every hit, and adds the rule, invariant, helper or check that stops it coming back.TestingNo warnings★ 113↓ —
- source-indexllopresto87/CypressAnswers impact, affected-tests, anchors and symbols queries on a plant's code via docs/graph/source-index.py, without a model.TestingNo warnings★ 113↓ —
- test-firstllopresto87/CypressThe test-shaping technique applied inside the test-first protocol — pick the lowest test level that exercises the behavior (unit, integration, contract, e2e, golden, property-based, evaluation), name the test after the spec contract, and assert one outcome per test. The workflow itself (entry conditions, RED-GREEN-REFACTOR-COMMIT gates, variants, exceptions) is the test-first protocol.TestingNo warnings★ 113↓ —