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 3 hours ago
48,362 skills
- ase-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ASE (IEEE/ACM Automated Software Engineering) paper, covering real subject systems, fair runnable tool baselines, task-matched effectiveness metrics, ablations that isolate a learned component, oracle and correctness validation, contamination-aware LLM handling, and provenance for mining.ScienceNo warnings★ 1.4K↓ —
- rss-submissionbrycewang-stanford/Awesome-Journal-SkillsJournal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的 Claude Code/Codex 期刊技能包，从选题、识别策略到表格规范与审稿回复全流程，助你快速发论文。PlanningNo warnings★ 1.4K↓ —
- socc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with backward-planning offsets for a cloud-systems measurement paper and honest handling of the two-rounds-per-year cadence and the no-cross-round-resubmission rule.ProductivityNo warnings★ 1.4K↓ —
- popl-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a POPL campaign calendar — backward-scheduling theory and mechanization from the July deadline, riding the October notification into the conditional-acceptance revision and artifact evaluation, landing the January conference, and retargeting across the SIGPLAN/PACMPL deadline wheel if July slips.ProductivityNo warnings★ 1.4K↓ —
- uai-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a UAI submission for OpenReview readiness, covering the February paper deadline, the 8-page main part with unlimited appendices in one PDF, the 15 MB file cap, the optional 50 MB supplementary ZIP, double-blind rules, the reviewer-volunteer agreement, dual-submission checks, and desk-reject triage before upload.DocumentsNo warnings★ 1.4K↓ —
- sosp-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification, stacking the August camera-ready with artifact evaluation, and retargeting rejections across the SOSP/OSDI/EuroSys circuit.ProductivityNo warnings★ 1.4K↓ —
- soda-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite deadlines (ALENEX, SOSA), and the January conference.ProductivityNo warnings★ 1.4K↓ —
- first-principles-reviewGanyuanRan/AegisUse when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.EngineeringNo warnings★ 1.4K↓ —
- minutes-listsilverstein/minutesList recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.PlanningNo warnings★ 1.6K↓ —Also in 1 other repo
- dispatching-parallel-agentsGanyuanRan/AegisUse when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.WritingNo warnings★ 1.4K↓ —
- pmla-workflowbrycewang-stanford/Awesome-Journal-SkillsUse as the entry point for any PMLA (Publications of the Modern Language Association) manuscript. Routes to the right PMLA sub-skill based on where you are in the lifecycle and which venue fits — a regular blind-reviewed article or a special feature (Theories and Methodologies, The Changing Profession, Criticism in Translation, Little-known Documents). It dispatches; it does not draft content.ProductivityNo warnings★ 1.4K↓ —
- pnas-citationbrycewang-stanford/Awesome-Journal-SkillsUse to convert references to PNAS's numbered citation style — cited in order of appearance, a numbered reference list, full author lists, abbreviated journal titles. Provides formats for article/book/chapter/dataset/preprint and an author-date → PNAS conversion table. Late-stage style pass.MarketingNo warnings★ 1.4K↓ —
- pldi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.ProductivityNo warnings★ 1.4K↓ —
- pnas-abstractbrycewang-stanford/Awesome-Journal-SkillsUse to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the Significance Statement (why-it-matters, for everyone). Late-stage polish.ScienceNo warnings★ 1.4K↓ —
- pnas-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after PNAS reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Do not run before the main text is actually revised.OtherNo warnings★ 1.4K↓ —
- pnas-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.ProductivityNo warnings★ 1.4K↓ —
- nejm-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after NEJM reviews arrive — often including a dedicated statistical reviewer and an editor letter — to triage the decision, answer statistical comments rigorously, and draft a point-by-point response that quotes each comment, the response, and the revised manuscript text. Do not run before the main text is actually revised.WritingNo warnings★ 1.4K↓ —
- nejm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which nejm-* sub-skill to invoke next, or when sequencing a clinical manuscript from significance test through response to reviewers for The New England Journal of Medicine. Routes — it does not replace — the specialized skills.ProductivityNo warnings★ 1.4K↓ —
- establishing-project-contextGanyuanRan/AegisUse when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.ProductivityNo warnings★ 1.4K↓ —
- ndss-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification, camera-ready, and the Seoul symposium, and placing NDSS honestly inside the security big-four retargeting year.ProductivityNo warnings★ 1.4K↓ —
- nejm-citationbrycewang-stanford/Awesome-Journal-SkillsUse to convert references to NEJM's Vancouver / ICMJE numbered style — numbered in order of appearance, limited author lists then et al., NLM journal abbreviations, and a capped reference count. Late-stage style pass.OtherNo warnings★ 1.4K↓ —
- recording-architecture-decisionsGanyuanRan/AegisUse when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.PlanningNo warnings★ 1.4K↓ —
- mind-workflowbrycewang-stanford/Awesome-Journal-SkillsUse as the entry point for any Mind (philosophy journal) article. Routes to the right Mind sub-skill based on where you are in the lifecycle and whether the piece is an article, discussion note, book review, or critical notice. Mind is analytic philosophy — argument, not data — so the router's first job is to confirm there is a sharp thesis and a sound argument. It dispatches; it does not draft content.ProductivityNo warnings★ 1.4K↓ —
- documenthashgraph-online/awesome-codex-pluginsRecord a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.ScienceNo warnings★ 1.5K↓ —
feature-launch-playbook
rampstackco/claude-skills
PlanningUpdated Oct 27, 2026
From the author
The operational playbook for launching a feature well. Positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses, and the discipline that distinguishes shipping from releasing from actually launching. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when planning a launch (any size, any segment), auditing an existing launch process, fixing the we shipped it but the metric did not move problem, or building a launch checklist for the team.
Install
npx skills add rampstackco/claude-skills --skill feature-launch-playbook -a claude-code
Installs to .claude/skills/feature-launch-playbook/ · 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 (12)
- README.md
- SKILL.md
- references/common-launch-failures.md
- references/customer-comms-playbook.md
- references/internal-alignment-checklist.md
- references/launch-tier-decision.md
- references/monitoring-readiness-checklist.md
- references/positioning-canvas.md
- references/post-launch-measurement-framework.md
- references/rollout-strategy-patterns.md
- references/sales-enablement-template.md
- references/support-readiness-checklist.md