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 23 hours ago
3,223 skills
- testing-anti-patternsMicrock/ordinary-claude-skillsUse when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependenciesTestingNo warnings★ 408↓ —
- fastapi-protranhieutt/software_development_departmentProduction FastAPI patterns — async endpoints, SQLAlchemy 2.0 async, Pydantic V2, dependency injection, JWT auth, testing. Use for Python 3.11+ FastAPI backends. NOT for Django (→ `django-patterns`) or Node.js (→ `backend-patterns`).TestingNo warnings★ 74↓ —
- Test Skill AComeOnOliver/skillshubA test skill in pkg-aTestingNo warnings★ 64↓ —
- skilladam-optimizeruc-datalab/SkillAdamOptimize an existing SKILL.md from a usage-intent description with SkillAdam. Use when a user asks to test, improve, patch, review, validate, or iteratively optimize an Agent Skill, with optional selective hunk review.TestingNo warnings★ 100↓ —Also in 1 other repo
- team-releasetranhieutt/software_development_departmentOrchestrates the release team of release-manager, qa-engineer, devops-engineer, and producer to execute a release from candidate to production deployment. Use when coordinating a release across QA, DevOps, and release management.TestingNo warnings★ 74↓ —
- test-skillComeOnOliver/skillshubUse when testing per-client skill rulesTestingNo warnings★ 64↓ —
- swarming-to-greenoaustegard/claude-skillsRuns a long swarm of hundreds to thousands of cheap headless coding workers that drive a large failing-test backlog to green. Failures are clustered by signature, each worker fixes one cluster in its own git worktree, a serial no-regression merge gate lands the fixes, the loop resumes across restarts for hours, and it federates across sibling sessions over git branches when one container's CPU is not enough. Use for "fix these thousands of failing tests with a Haiku swarm", "drive the test suite to green with hundreds of agents", "build this compiler or interpreter against a conformance suite", "launch, relaunch or check in on the swarm loop", "the swarm is stuck, idle or rejecting everything", "parallel agents fixing tests keep hitting merge conflicts and regressions", "add sibling containers to the swarm", or "compare models on the tail the swarm could not fix". Ships the harness, a per-project TOML config, a fake-worker selftest, check-in signals and the 2026-10-12 haiku-cc failure catalogue.TestingNo warnings★ 154↓ —Also in 1 other repo
- with-hooksComeOnOliver/skillshubUse when testing valid hooksTestingNo warnings★ 64↓ —
- wjs-x-increasing-followerjianshuo/claude-skillsUse when 王建硕 wants to systematically grow his X (Twitter) followers by running numbered, A/B-testable growth experiments and tracking which ones actually work. Every action gets a number, a hypothesis, a target metric, a before-state (for rollback), and a verdict. The North-Star metric is the new-follower ÷ profile-visit ratio (conversion) — every profile change is judged against it. Daily it ingests the X Analytics CSV export, scores each running experiment, and recommends keep / rollback. Triggers — "涨粉", "增加 X 粉丝", "X 涨粉实验", "follower growth", "A/B test my profile", "今天的涨粉检查", "/wjs-x-increasing-follower".TestingNo warnings★ 137↓ —
- with-modelComeOnOliver/skillshubUse when testing valid model configurationTestingNo warnings★ 64↓ —
- justfile-authorNickCrew/Claude-CortexUse this skill when authoring or refactoring a justfile (and matching Makefile wrapper) for one of Nick's projects. Triggers when the user asks to "create a justfile", "add a justfile to this project", "set up just for…", "wire up tmux services", "scaffold the task runner", or when working in a repo that lacks a justfile but obviously needs one. Produces a justfile using zsh syntax with the standard svc-* tmux service family, the canonical build/lint/dev/test recipes, a thin Makefile passthrough wrapper that auto-installs just, and per-service tx-start.sh helpers. Do NOT use for editing existing third-party justfiles or non-Nick projects unless the user explicitly opts in.TestingNo warnings★ 61↓ —
- ci-cdmgifford/accessibility-skillsLoad this skill when configuring or reviewing CI/CD pipelines, GitHub Actions workflows, or automated testing setups. Ensures accessibility regressions are caught before code reaches production by enforcing quality gates, structured reporting, and layered automated + manual testing across all pages and user preferences.TestingNo warnings★ 57↓ —
- skilladam-optimizeruc-datalab/SkillAdamOptimize an existing SKILL.md from a usage-intent description with SkillAdam. Use when a user asks to test, improve, patch, review, validate, or iteratively optimize an Agent Skill, with optional selective hunk review.TestingNo warnings★ 100↓ —Also in 1 other repo
- jestComeOnOliver/skillshub🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.TestingNo warnings★ 64↓ —
- team-featuretranhieutt/software_development_departmentOrchestrates a cross-functional feature team of product-manager, ux-designer, frontend-developer, backend-developer, and qa-engineer to deliver a complete feature from specification to tested implementation. Use when a feature requires full-stack coordinated delivery.TestingNo warnings★ 74↓ —
- ci-speedupmblode/agent-skillsSpeeds up CI and the merge path: finds where changes wait between push and deploy, then fixes the critical path, check placement, merge queue or post-merge checks with auto-revert, flaky tests, and deploy rate. Use when "CI is slow", "speed up CI", "do we need a merge queue", "main keeps going red", "flaky tests block merges", agents open PRs faster than they merge, or building a self-healing merge loop.TestingNo warnings★ 163↓ —
- new-loopAI-Builder-Club/skillsSpin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold domains/<loop>/README.md, then do ONE real test run and record it in the loop's Timeline and LOG.md. Use when the user says "set up a new loop", "create a domain", "start a new beat/workstream", or names a recurring job they want the agent to own.TestingNo warnings★ 1.3K↓ —
- axe-rulesmgifford/accessibility-skillsLoad this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.TestingNo warnings★ 57↓ —
- light-dark-modemgifford/accessibility-skillsLoad this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level colour preferences via CSS media queries.TestingNo warnings★ 57↓ —
- verifier-setupAI-Builder-Club/skillsSet a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-local` skill + script, and the installed driver skill. Use when someone says "set up verification", "make this repo verifiable", "scaffold a verify skill", "set up the verifier".TestingNo warnings★ 1.3K↓ —
- bug-reportingmgifford/accessibility-skillsLoad this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.TestingNo warnings★ 57↓ —
- windows-qa-engineerCodeAlive-AI/ai-driven-developmentUse when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP. Triggers on "test this Windows app", "QA the app", "run smoke test", "click the button", "fill the form", "check the UI", "Windows automation", "UFO QA", "verify the dialog", or any Windows desktop UI testing task. Not for web/browser testing (use Playwright), mobile testing, or non-Windows platforms.TestingNo warnings★ 166↓ —
- setup-codebase-harnessAI-Builder-Club/skillsMaster skill — set up the full agent harness for any repo so an agent can work it reliably: legible (map-not-manual docs + custom lints), executable (one-command dev stack), verifiable (e2e gate + a verify-before-ship loop), plus commit hygiene and entropy control. Use when onboarding a new/unfamiliar codebase to agent-driven development — "set up the harness", "make this repo agent-ready", "harness this codebase".TestingNo warnings★ 1.3K↓ —
- color-contrastmgifford/accessibility-skillsLoad this skill whenever the project contains text, UI components, icons, form controls, data visualisations, or focus indicators — in short, almost every project. Under no circumstances hard-code colour values without verifying contrast ratios. Absolutely always ensure text meets 4.5:1, large text meets 3:1, and non-text UI elements meet 3:1 against adjacent colours. Test in light mode, dark mode, and forced-colors (high contrast) mode.TestingNo warnings★ 57↓ —