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 2 hours ago
48,362 skills
- fse-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.WritingNo warnings★ 1.4K↓ —
- cav-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.ProductivityNo warnings★ 1.4K↓ —
- pnas-trackbrycewang-stanford/Awesome-Journal-SkillsUse to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.ScienceNo warnings★ 1.4K↓ —
- sci-fitbrycewang-stanford/Awesome-Journal-SkillsUse before any writing to stress-test whether a result clears Science's (AAAS) desk-reject filter — broad significance and general interest across disciplines. Decides Science vs Science Advances vs a specialist journal before you invest in prose.TestingNo warnings★ 1.4K↓ —
- pnas-databrycewang-stanford/Awesome-Journal-SkillsUse to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.PlanningNo warnings★ 1.4K↓ —
- atc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) campaign end to end — running the year backward from the early-June deadline through the two review rounds, the rebuttal, conditional-acceptance shepherding, the post-acceptance artifact evaluation, and the ACM Open Access camera-ready for the November Hong Kong conference.ProductivityNo warnings★ 1.4K↓ —
- skill-shareComposioHQ/awesome-claude-skillsA skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.OtherNo warnings★ 78.6K↓ —Also in 2 other repos
- pnas-fitbrycewang-stanford/Awesome-Journal-SkillsUse before any writing begins to stress-test whether a result clears PNAS's bar — high quality and broad significance to a general scientific readership — and to make the realistic call between PNAS, Science/Nature, and a specialist field journal.TestingNo warnings★ 1.4K↓ —
- nejm-fitbrycewang-stanford/Awesome-Journal-SkillsUse this first, before any writing, to stress-test whether a clinical study clears NEJM's bar — practice-changing clinical impact, methodological rigor, and generalizability. Decides NEJM vs Lancet/JAMA vs a specialty journal.TestingNo warnings★ 1.4K↓ —
- implement-specdzhng/skillsImplement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints to periodically clean code, handoffs, priorities, and plan bloat before drift accumulates.PlanningNo warnings★ 1.4K↓ —
- nsdi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems reviewers can see where the design wins, loses, and breaks.DevOpsNo warnings★ 1.4K↓ —
- auto-researchdzhng/skillsRun fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts, configurations, or other artifacts against a goal or benchmark, or when a long research run needs a planned hypothesis queue, focused trials, and durable findings.ScienceNo warnings★ 1.4K↓ —
- expo-skill-evalexpo/skillsEvaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional). Use when the user wants to eval an Expo skill, test that a skill produces working code, benchmark a skill with device screenshots, or verify a skill's output renders correctly.OfficialTestingNo warnings★ 4K↓ —
- agent-run-forensicsNewalirezarezvani/claude-skillsUse when asked why an agent did something, what a past session or run changed, whether tests really passed, or to verify a session summary. Answers from the recorded transcript, not memory, with trace_finder.py, trace_timeline.py and claim_checker.py.SecurityNo warnings★ 29.2K↓ —
- analyze-performance-call-and-learngooseworks-ai/goose-skillsStep of the analyze-performance playbook: calls ended tests, scores last week's calls, writes this week's kill/scale/hold calls and drafts learnings for the brand brain. Run analyze-performance instead; not for direct use.TestingNo warnings★ 1.3K↓ —
- daily-journalhuytieu/COG-second-brainA passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say "log this to my journal", "add to today's journal", "reflect on today/yesterday", or when finishing a meaningful chunk of work in any session.WritingNo warnings★ 1.3K↓ —Also in 1 other repo
- analyze-performance-rank-and-readgooseworks-ai/goose-skillsStep of the analyze-performance playbook: ranks creative by angle, hook and format with spend gates, writes short per-channel reads and drafts what to make next. Run analyze-performance instead; not for direct use.WritingNo warnings★ 1.3K↓ —
- write-testsdzhng/skillsWrite tests that pin real behavior instead of implementation details, config values, or lucky samples. Use when adding tests for new behavior, writing a regression test, fixing a brittle or flaky test, reviewing a test diff, or when a test breaks after a refactor or config change that didn't change behavior.TestingNo warnings★ 1.4K↓ —
- taste-skillhuytieu/COG-second-brainAnti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.DesignNo warnings★ 1.3K↓ —Also in 1 other repo
- data-formshuytieu/COG-second-brainPick the right way to represent a dataset so a reader gets the finding in three seconds — a catalog of 20+ chart and diagram forms with when-to-use and failure modes, plus the encoding decisions that make any of them readable (takeaway headline, direct labels, kill the axis, highlight-and-mute, show the caveat). Style-agnostic — use with whatever palette or design system the destination already has. Use when charting survey results, benchmark data, usage metrics, or research findings for a post, brief, deck, or report, and whenever the default bar chart feels like it's burying the point.DocumentsNo warnings★ 1.3K↓ —Also in 1 other repo
- braindumphuytieu/COG-second-brainQuick capture of raw thoughts with intelligent domain classification and competitive intelligence extractionOtherNo warnings★ 1.3K↓ —Also in 1 other repo
- write-specdzhng/skillsBreak large features into independently verifiable, human-reviewable slices under a feature directory in specs/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices before slicing. Pairs with your project's verification harness and screenshot gates (the browser checkpoints), [refactor-clean](../refactor-clean/SKILL.md) (review the materialized spec so the plan describes one-owner architecture, not the feature bolted on), [screenshot-critique](../../visual/screenshot-critique/SKILL.md) and [compare-screenshots](../../visual/compare-screenshots/SKILL.md) (the visual gates), and a code-review pass (audit each slice before it lands).WritingNo warnings★ 1.4K↓ —
- retrohuytieu/COG-second-brainCP-7 retrospective: audit checkpoints, evidence quality, action items, and harvest candidates. Closes the V-model cycle and feeds the next run. Use via /retro after ship, escalate, or significant session.OtherNo warnings★ 1.3K↓ —Also in 1 other repo
- google-apps-scriptjezweb/claude-skillsBuild Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a webhook, schedule a Sheets workflow, or asks 'how do I script this in Sheets'.DocumentsNo warnings★ 1.1K↓ —
email-sequences
rampstackco/claude-skills
ProductivityUpdated Oct 27, 2026
From the author
Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns.
Install
npx skills add rampstackco/claude-skills --skill email-sequences -a claude-code
Installs to .claude/skills/email-sequences/ · 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
Provenance76
Maintenance100
Licence100
Adoption49
Files (4)
- README.md
- SKILL.md
- references/sequence-templates.md
- references/subject-line-patterns.md