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,409 skills from 2,375 repositories · updated 14 hours ago
48,362 skills
- email-to-tasksmohitagw15856/pm-claude-skillsConvert an email (or a whole thread) into real tasks — the actual asks extracted from the prose, each with owner, deadline, and the done-test, so nothing lives in the inbox as its own reminder. Use when asked what am I actually being asked to do here, turn this thread into a task list, extract the action items from this email, or I keep re-reading this thread. Produces the ask extraction with quoted sources, the task list in owner-verb-deadline form, and the reply that confirms the commitments.ProductivityNo warnings★ 1.5K↓ —
- risk-registermohitagw15856/pm-claude-skillsBuild and maintain a project or product risk register. Use when asked to create a risk register, identify project risks, build a risk matrix, or document risks and mitigations for a programme. Produces a complete risk register with likelihood/impact scoring, RAG status, ownership, and prioritised mitigations.OtherNo warnings★ 1.5K↓ —
- grant-proposalmohitagw15856/pm-claude-skillsWrite a structured grant proposal or funding application for any grant type. Use when asked to write a grant proposal, funding application, research grant, charitable grant, or innovation fund application. Produces a complete proposal with project summary, rationale, methodology, impact, and budget narrative.ScienceNo 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↓ —
- 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.2K↓ —
- channel-economicsalirezarezvani/claude-skillsUse for a direct vs partner channel review: fully loaded cost to serve, channel ROI and the best channel mix under constraints. Runs cost_to_serve_calculator.py, channel_roi_analyzer.py and channel_mix_optimizer.py.EngineeringNo warnings★ 29.2K↓ —
- react-doctoramplifthq/openmeldUse when the user requests React Doctor or a React code-health audit, or when a concrete React diagnostic question would benefit from its scan. Not a default step after React changes or before committing.EngineeringNo warnings★ 1.4K↓ —
- asc-submission-healthrorkai/app-store-connect-cli-skillsDiagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.EngineeringNo warnings★ 1.1K↓ —
- brooks-healthhyhmrright/brooks-lintCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).TestingNo warnings★ 1.6K↓ —
- local-fileshashgraph-online/awesome-codex-pluginsDevelopment-file storage rule for skills that write plans, reports, specs, handovers, or work ledgers. Names the directories Quiver writes and how each one is kept out of git on first write, unless the directory is already tracked or the project says to track it.WritingNo warnings★ 1.5K↓ —
- clean-gone-branchesfcakyon/claude-codex-settingsThis skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".OtherNo warnings★ 1.2K↓ —
- openmeld-cliamplifthq/openmeldUse OpenMeld when a task needs Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work. Also use for OpenMeld setup and Wake replies.EngineeringNo warnings★ 1.4K↓ —Also in 3 other repos
- deal-deskalirezarezvani/claude-skillsUse before closing a deal that needs a discount beyond AE authority, has a redlined MSA or unclear per-deal economics. Scores it with deal_scorer.py, names approvers with discount_approval_router.py and flags risky terms with terms_redliner.py. Never auto-approves.OtherNo warnings★ 29.2K↓ —
- pr-descriptionmohitagw15856/pm-claude-skillsWrite a clear pull-request description that gets reviewed fast and merged with confidence, from a git diff, branch summary, or commit list. Use when opening a PR, summarizing a change for review, documenting code changes, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.WritingNo warnings★ 1.5K↓ —
- seo-aeo-georampstackco/claude-skillsOptimize content and site structure for AI-driven search experiences including AI overviews, large language model citations, generative answer engines, and AI assistants. Use this skill whenever the user wants to optimize for AI search, get cited by language models, appear in AI overviews, build llms.txt, structure content for AI extraction, or future-proof their SEO for the shift from blue links to AI answers. Triggers on AEO, GEO, AI search, AI SEO, AI overview, generative search, LLM optimization, llms.txt, AI citation, ChatGPT search, Perplexity, Gemini, Claude search, AI assistant optimization, answer engine. Also triggers when the user expresses concern about AI eating their organic traffic or wants to understand how to remain visible as search shifts.MarketingNo warnings★ 1K↓ —
- tos-decodermohitagw15856/pm-claude-skillsDecode a terms of service or privacy policy into what you're actually agreeing to, ranked by real-world impact. Use when someone asks 'what am I agreeing to', 'decode this privacy policy', 'is this ToS bad', or 'should I click accept'. Produces a ranked findings table with a 'should I care?' verdict per finding, covering data resale, arbitration and class-action waivers, unilateral changes, content licenses, and what deletion really means.OtherNo warnings★ 1.5K↓ —
- design-buildhashgraph-online/awesome-codex-pluginsExecute a design plan produced by /design -- implements each node against its embedded measurement spec and gates every task on the project's build or tests under a bounded retry budget. Runs with Figma disconnected; the plan carries every number it needs. --auto runs the whole loop without a prompt.DesignNo warnings★ 1.5K↓ —
- openship-deployfcakyon/claude-codex-settingsThis skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades through the CLI.DevOpsNo warnings★ 1.2K↓ —
- month-end-closealirezarezvani/claude-skillsUse when running, planning or speeding up a month-end (or quarter-end) close — building or reviewing the close checklist and calendar, reconciling a bank statement or sub-ledger to the general ledger, writing or reviewing flux (variance) explanations, or finding why the close takes too many days. Orders close tasks by dependency and finds the critical path, proves each reconciliation and ages what is left, and refuses to sign off material fluctuations explained with boilerplate.WritingNo warnings★ 29.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 .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↓ —
- heading-structurekostja94/marketing-skillsWhen the user wants to write or optimize H1-H6, fix heading hierarchy, improve content structure, rewrite an H1, or align headings with page intent. This skill owns actual heading changes; page-metadata may only check and report metadata-to-heading alignment.WritingNo warnings★ 1.1K↓ —
- minutes-weeklysilverstein/minutesWeekly meeting synthesis — themes, decision arcs, stale commitments, and what deserves your attention next week. Use when the user says "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", or at the end of a work week.EngineeringNo warnings★ 1.6K↓ —Also in 1 other repo
- gtm-strategykostja94/marketing-skillsWhen the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.MarketingNo warnings★ 1.1K↓ —
- paper-search-usagefcakyon/claude-codex-settingsThis skill should be used when the user asks to "search for papers", "find research papers", "search arXiv", "search PubMed", "look up a DOI", "download a paper", "search IEEE", or "search Scopus".ScienceNo warnings★ 1.2K↓ —
email-lifecycle
gooseworks-ai/goose-skills
ProductivityUpdated Oct 27, 2026
From the author
Lifecycle email, SMS and push: audits the list and deliverability, then writes the flows this kind of business needs first, loadable as-is in your own tool, plus segments, cadence and this week's broadcasts. Never sends anything. Use when: set up my welcome and abandoned-cart emails; trial onboarding or waitlist launch emails; win back lapsed customers; plan this week's emails and texts; push notifications for my app; why are my emails going to spam; plan our Black Friday email and SMS sends; a send went wrong. Not for cold outreach to prospects — use write-outreach; not the editorial newsletter issue — use make-content; not the whole cross-channel Black Friday plan — use plan-campaign.
Install
npx skills add gooseworks-ai/goose-skills --skill email-lifecycle -a claude-code
Installs to .claude/skills/email-lifecycle/ · 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
Provenance77
Maintenance100
Licence100
Adoption50
Files (14)
- SKILL.md
- references/benchmarks.md
- references/copy-craft.md
- references/deliverability.md
- references/flow-library.md
- references/intake.md
- references/loadable-flow-format.md
- references/modes-and-incidents.md
- references/run-memory.md
- references/segments-cadence-offers.md
- references/sms-push-whatsapp.md
- references/worked-flows.md
- +2 more