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.
45,604 skills from 2,205 repositories · updated 7 hours ago
3,223 skills
- preview-manual-testmodem-dev/ossrulesDiscover, wait for, sign in, create specific user data, and assert a PR preview deploy. Use on medium or high risk PRs, after pushing a ready-for-review PR, or when the user asks to test the preview URL.TestingNo warnings★ 64↓ —
- python-testingmturac/everything-openai-codexPython testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.TestingNo warnings★ 83↓ —
- springboot-tddmturac/everything-openai-codexTest-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.TestingNo warnings★ 83↓ —
- ipsaeBioTender-max/awesome-bio-agent-skillsBinder design ranking using ipSAE (interprotein Score from Aligned Errors). Use this skill when: (1) Ranking binder designs for experimental testing, (2) Filtering BindCraft or RFdiffusion outputs, (3) Comparing AF2/AF3/Boltz predictions, (4) Predicting binding success rates, (5) Need better ranking than ipTM or iPAE. For structure prediction, use chai or alphafold. For QC thresholds, use protein-qc.TestingNo warnings★ 206↓ —
- hypogenicBioTender-max/awesome-bio-agent-skillsAutomated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.TestingNo warnings★ 206↓ —
- verifyoliver-kriska/claude-elixir-phoenixVerify a rewrite slice against its obligations: preflight, capture fresh test evidence, audit translationese and parity, update the ledger. Use after /phx:work finishes a rewrite slice, or before claiming parity.TestingNo warnings★ 571↓ —
- pm-testswei63w/pm-managerList missing unit-test companions for core/changed sources. Do not write tests into the business tree unless the user confirms.TestingNo warnings★ 87↓ —
- llm-testingalicewe1/alice_skillAlice 集成技能包 · 放进去就能用 · Drop-in skill suite for AI coding agentsTestingNo warnings★ 52↓ —
- cuopt-developerNVIDIA/skillsModify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.TestingReview first★ 3.7K↓ —
- django-tddmturac/everything-openai-codexDjango testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.TestingNo warnings★ 83↓ —
- testinglubusIN/frappe-skillsWrite and run tests for Frappe apps including unit tests, integration tests, and UI tests. Use when adding test coverage, debugging test failures, or setting up CI for Frappe projects.TestingNo warnings★ 68↓ —
- frappe-managerlubusIN/frappe-skillsUse Frappe Manager (FM) for Docker-based development and testing environments. Use when setting up local dev, running isolated tests, or managing agent-driven Frappe development workflows.TestingNo warnings★ 68↓ —
- shiphashgraph-online/awesome-codex-pluginsRun a project in phases. The first /ship asks one batch of project questions, proposes a split into phases, and on one approval saves a roadmap, a decision log, and one file per phase under .claude/ship/, then starts the first phase. Each phase runs end to end -- its questions, research, a spec and a plan written without approval prompts, the build through /work --auto, build, test, and smoke checks, /quiver:review, an automatic fix of the findings the review confirmed, and a plain-language report -- and a finished phase starts the next ready one in the same run. The run ends at a stopped phase or when you choose a fresh session. Every stage is saved in the phase file, so /clear then /ship continues where a run stopped. Nothing is pushed and no pull request is opened.TestingReview first★ 1.4K↓ —
- workhashgraph-online/awesome-codex-pluginsExecute a work plan or specification systematically -- read the plan, set up a branch, implement tasks with continuous testing, commit incrementally, and ship a PR. Use when you have a plan file, spec, or task list ready to execute. --auto answers the routine gates (branch, final commit, PR handoff, workspace cleanup, third failed fix attempt) in advance and stops only for a blocker, a Critical finding, or a merge conflict.TestingReview first★ 1.4K↓ —
- rust-best-practicesNewmorganlinton/BeautifulRustWrite idiomatic, robust, maintainable Rust. Use this skill whenever you write, review, refactor, debug, or explain Rust code: new crates, modules, functions, structs, traits, error types, async code, unsafe or FFI code, Cargo.toml, tests, or rustdoc. Trigger on any mention of Rust, cargo, crates, .rs files, the borrow checker, lifetimes, traits, clippy, or rustfmt, even when the user does not ask for "best practices" or "idiomatic" code. Synthesized from the Google Rust Style Guide, the Rust API Guidelines, Effective Rust, Rust Design Patterns, and Microsoft's Pragmatic Rust Guidelines.TestingNo warnings★ 396↓ —
- mapstagehopechen067/MapStageMapStage — 历史视频的叙事地图舞台（MapLibre GL JS 5.6）。古卷底图 preset、路线行进、地名三态、按口播自动取景、平台合规（不画省界国界、无雾无暗角、台湾海南南海完整）、seek(t) 逐帧时间契约，供 HyperFrames / Remotion / Playwright 截帧。用户说「/mapstage」「做一段 X 从 A 到 B 的路线移动」「出一张全国定位图」「调古卷底图」「地图镜头」时使用。TestingNo warnings★ 489↓ —
- module-audit-agentwednesday-solutions/ai-agent-skillsUse when asked to audit a module, check its health, or assess whether it should be refactored. Runs structural query, risk check, and test generation automatically.TestingNo warnings★ 172↓ —
- designing-distributed-system-testsshenli/distributed-system-testingAI-agent skills for distributed-systems testingTestingNo warnings★ 231↓ —
- frappe-ops-app-lifecycleImpertio-Studio/Frappe_Claude_Skill_PackageUse when scaffolding a new Frappe app, configuring app settings, building assets, running tests, deploying, updating, or publishing to marketplace. Prevents broken app structure from incorrect scaffolding, missing setup.py fields, and failed builds. Covers bench new-app, app directory structure, setup.py/pyproject.toml, hooks.py config, bench build, bench run-tests, app publishing. Keywords: app lifecycle, new-app, scaffolding, setup.py, pyproject.toml, hooks.py, bench build, app publishing, marketplace, create app, publish app, app structure, how to start new app, app directory layout..TestingNo warnings★ 195↓ —
- frappe-testing-cicdImpertio-Studio/Frappe_Claude_Skill_PackageUse when setting up CI/CD pipelines for Frappe apps, configuring GitHub Actions test workflows, or adding linting and security scanning. Prevents broken CI from incorrect test matrix configuration, missing MariaDB/Redis services, and uncaught code quality issues. Covers GitHub Actions workflows, test matrix (Python/Node versions), semgrep rules, pre-commit hooks, linting (ruff, eslint), CI test environment setup. Keywords: CI/CD, GitHub Actions, test matrix, semgrep, pre-commit, linting, ruff, eslint, continuous integration, automated tests, GitHub Actions, CI pipeline, pre-commit, code quality check..TestingNo warnings★ 195↓ —
- absolute-initmaddhruv/absoluteOne-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write `.absolute.config.json` (project, committed) and `~/.absolute/config.json` (user defaults + per-project overrides). Every other absolute-* command reads it instead of re-detecting; non-blocking — commands proceed without it and soft-recommend it. Triggers on "absolute init", "set up absolute", "initialize absolute", "configure absolute", "first-time setup", "remember my conventions for this repo".TestingNo warnings★ 223↓ —
- absolute-simplifymaddhruv/absoluteUse when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on: "simplify", "simplify this", "simplify my code/changes", "clean up", "clean this up", "clean up my changes", "refactor this", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", "make it more readable", "polish before commit", or "absolute simplify". Acts on your working diff; for repo-wide dead code use absolute-prune; for lint/type debt use absolute-debt.TestingNo warnings★ 223↓ —
- absolute-deflakemaddhruv/absoluteFlaky test fixes: detect nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnose the root cause, fix it — never retry/skip/sleep — and verify across many randomized runs. Triggers on "absolute deflake", "fix flaky tests", "CI is flaky", "this test fails randomly/intermittently".TestingNo warnings★ 223↓ —
- absolute-workmaddhruv/absoluteEnd-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge. Handles features, bugs, refactors, greenfield projects, planning breakdowns, and migrations. Triggers on "absolute work", "build this end-to-end", "plan and build", "break this into tasks", "grill me on this plan", "pick up this ticket", "run this migration".TestingNo warnings★ 223↓ —