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.
49,415 skills from 2,407 repositories · updated 2 hours ago
49,415 skills
- tddhashgraph-online/awesome-codex-pluginsUse when implementing or fixing production code with tests.TestingNo warnings★ 1.5K↓ —
- writing-testsamplifthq/openmeldGates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; extend the nearest existing test before writing a new standalone one; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network; no time bombs from absolute dates left to age against the real clock; no database a test never uses). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.TestingNo warnings★ 1.4K↓ —
- compliance-osalirezarezvani/claude-skillsUse when running several compliance frameworks at once: which apply, where controls overlap, a mock audit or one evidence checklist. Runs framework_selector.py, cross_framework_mapper.py, audit_simulator.py and evidence_pool_generator.py.LegalNo warnings★ 29.3K↓ —
- docs-lifecycle-scanamplifthq/openmeldUse when closing out a feature, tidying developing/ documentation, or asked to check docs health — runs the lifecycle linter and applies the README deletion rules.OtherNo warnings★ 1.4K↓ —
- vpe-advisoralirezarezvani/claude-skillsUse when delivery is slowing, eng hiring is broken, team structure is unclear or you need to decide when to add an eng manager. Runs delivery_throughput_analyzer.py (DORA), eng_hiring_funnel_calculator.py and eng_team_structure_designer.py.OtherNo warnings★ 29.3K↓ —
- contract-reviewmohitagw15856/pm-claude-skillsReview and summarise any contract or legal agreement. Use when asked to review a contract, check an agreement, flag legal risks, or summarise key clauses. Produces a structured review with key terms, flagged clauses, risk rating, and plain English summary. Not a substitute for qualified legal advice.LegalNo warnings★ 1.5K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint TestingNo warnings★ 1.6K↓ —
- daily-cash-bookmohitagw15856/pm-claude-skillsKeep simple daily money records for a small trader, stall or home business with no accounting software: a cash book, stock count and weekly summary that show whether the business makes money and keep business and household money apart. Use when someone says 'I don't know if my shop makes money', 'how do I keep records for my small business', 'the bank wants records for a loan', or 'I mix business and home money'. Produces a one-page daily cash book, a weekly summary, a simple stock count, and three rules to keep the habit.FinanceNo warnings★ 1.5K↓ —
- resolve-pr-commentsfcakyon/claude-codex-settingsThis skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".EngineeringNo warnings★ 1.2K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint tTestingNo warnings★ 1.6K↓ —
- brandingkostja94/marketing-skillsWhen the user wants to define, audit, or apply brand strategy—purpose, values, positioning, storytelling, voice, narrative (not only visuals). Also use when the user mentions "brand strategy," "brand story," "brand storytelling," "brand voice," "brand identity," "brand guidelines," "brand purpose," "brand values," "origin story," "brand narrative," "brand personality," "brand archetype," "slide deck branding," "PPT brand colors," or "document style guide." For typography, colors, design tokens, and frontend visuals, use brand-visual-generator.DocumentsNo warnings★ 1.1K↓ —
- oma-frontendfirst-fluke/oh-my-agentImplement or modify web UI in React, Next.js, or Angular. Use for components, pages, styles, forms, and frontend state or data flows.DesignNo warnings★ 1.4K↓ —
- new-skillhyhmrright/brooks-lintScaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". Do NOT trigger for: editing an existing skill's content, adding a single eval to an existing skill, or authoring skills for some other plugin.WritingNo warnings★ 1.6K↓ —
- postgresql-development-cloudbaseUpdatedTencentCloudBase/CloudBase-AI-ToolkitUse when building, debugging, or evaluating CloudBase PostgreSQL / CloudBase PG / PG mode apps, including Postgres schema setup, queryPgDatabase/managePgDatabase, JS SDK v3 app.rdb() CRUD/RPC, PG HTTP API fallback, RLS-style permissions, username-password auth, and Web CMS/admin CRUD flows backed by CloudBase PG.DataNo warnings★ 1.2K↓ —Also in 4 other repos
- brooks-audithyhmrright/brooks-lintArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.PlanningNo warnings★ 1.6K↓ —
- brooks-testhyhmrright/brooks-lintTest quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.TestingNo warnings★ 1.6K↓ —
- cpo-advisoralirezarezvani/claude-skillsProduct leadership: PMF measurement, product vision, portfolio investment, product org design, board product reporting. Use whenever the user asks if they have PMF or how to split investment across products.DesignNo warnings★ 29.3K↓ —
- nanoresearch-planningOpenRaiser/NanoResearchProduce an experiment blueprint from a research hypothesisPlanningNo warnings★ 1.3K↓ —
- cmo-advisoralirezarezvani/claude-skillsMarketing leadership: positioning, product-led vs sales-led vs community-led growth, budget split across channels, marketing team design. Use whenever the user asks how to grow, which go-to-market fits or where to spend.DesignNo warnings★ 29.3K↓ —
- relay-80-100-workflowAgentWorkforce/relayUse when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite for in-memory Postgres testing, mock sandbox patterns, test-fix-rerun loops, verify gates after every edit, and the full lifecycle from implementation through passing tests to commit.ProductivityNo warnings★ 1.1K↓ —
- reading-livekit-docsfcakyon/claude-codex-settingsLooks up current LiveKit facts (API signatures, CLI flags, config options, model and provider support, SDK changelogs, pricing) from the docs instead of answering from memory. Use whenever a question touches LiveKit specifics: "does LiveKit support X", "what changed in agents 1.8", "what are the arguments to Y", "how much does LiveKit cost", "find an example of Z in the LiveKit repos", or before writing any LiveKit code. Other LiveKit skills load this one first. Covers the LiveKit Docs MCP server and the `lk docs` CLI.WritingNo warnings★ 1.2K↓ —Also in 1 other repo
- oma-marketfirst-fluke/oh-my-agentResearch customer pain points, trends, and competitors through the OMA market engine. Use for market discovery or voice-of-customer analysis.ScienceNo warnings★ 1.4K↓ —Also in 4 other repos
- seonix-seoNewhashgraph-online/awesome-codex-pluginsWork on the SEO of a website that is connected to Seonix through the seonix MCP server - audit it, find what to fix, read Search Console traffic, check a draft. Use when the user asks to improve SEO, organic traffic, rankings or content for a site that is in Seonix, mentions Seonix, Site Health, the fix plan or Search Console data from Seonix, or asks which pages or queries to work on next.MarketingNo warnings★ 1.5K↓ —
- refactoringciembor/agent-rules-booksApply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.EngineeringNo warnings★ 3.2K↓ —
design-system
daveebbelaar/bama
DesignUpdated 11 hours ago
From the author
Accent color and design system for a macOS app, from the app's accent and the accent picker in Settings to Swift tokens in code plus a design/DESIGN-SYSTEM.md that says which token to use when. Use when the user wants a brand or accent color, wants people to pick a color, when an app has more than a few screens, when screens drift apart or animations feel inconsistent, or when the user asks for themes, a style guide, or design tokens.
Install
npx skills add daveebbelaar/bama --skill design-system -a claude-code
Installs to .claude/skills/design-system/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Instructions onlyNo network use seenLicence: MIT
Safety checks on SKILL.md
No warnings.
Why 88
Security100
Provenance78
Maintenance100
Licence100
Adoption51
Files (2)
- SKILL.md
- agents/openai.yaml