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,456 skills from 2,407 repositories · updated 24 minutes ago
49,454 skills
- 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↓ —
- 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↓ —
- rfp-responderalirezarezvani/claude-skillsUse when an RFP, RFI, RFQ or security or vendor questionnaire arrives. Parses mandatory vs weighted requirements with rfp_parser.py, drafts proof-point answers with response_drafter.py and estimates win chance with winrate_predictor.py.SecurityNo warnings★ 29.3K↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- kdd-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a KDD submission for readiness in either cycle, covering Research vs ADS track declaration, OpenReview profile completeness for all authors, the ACM sigconf 8-content-page budget, double-blind checks, in-paper artifact references, resubmission declarations, and desk-reject triggers specific to ACM SIGKDD.ScienceNo warnings★ 1.4K↓ —
- nejm-abstractbrycewang-stanford/Awesome-Journal-SkillsUse to write the NEJM structured abstract — four headed sections (Background, Methods, Results, Conclusions), ≤250 words, with the trial registration number and funding source, leading the Results with the primary outcome reported as an effect size with a 95% CI. Late-stage polish skill.WritingNo warnings★ 1.4K↓ —
- icse-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April conference, plus rerouting timelines after rejection.ProductivityNo warnings★ 1.4K↓ —
- iros-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.ProductivityNo warnings★ 1.4K↓ —
- jama-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which jama-* sub-skill to invoke next, or when sequencing a clinical manuscript from scope check through revision for JAMA (Journal of the American Medical Association). Routes — does not replace — the specialized skills.ProductivityNo warnings★ 1.4K↓ —
- 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↓ —
- imc-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM IMC submission for HotCRP readiness, covering the paper-registration step, the acmart template with BBL upload, the full/short page limits, double-blind anonymity including vantage-point details, the mandatory Ethics section, the artifact-availability declaration, cycle choice, and desk-reject triage before the AoE cutoff.ScienceNo warnings★ 1.4K↓ —
- ipsn-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.ProductivityNo warnings★ 1.4K↓ —
- iccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.ProductivityNo warnings★ 1.4K↓ —
- icde-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication.ProductivityNo warnings★ 1.4K↓ —
- icdm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the August notification, the no-rebuttal review, the possible short-paper acceptance branch, IEEE camera-ready, and in-person presentation on a single annual deadline.ProductivityNo warnings★ 1.4K↓ —
- hri-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE HRI full-paper submission for PCS readiness — the mandatory abstract-then-paper two-step deadline, choosing the correct one of the five tracks, the 8-page acmart anonymous format, the double-blind sweep across PDF and video, the human-participants ethics acknowledgment, and desk-reject triage before the AoE cutoff.DocumentsNo warnings★ 1.4K↓ —
- iclr-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.ProductivityNo warnings★ 1.4K↓ —
- dac-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline, the 6+1-page ACM double-column page budget with its references-only last page, the double-blind anonymization sweep, TPC conflict-of-interest declaration, and desk-reject triage before the mid-to-late-November cutoff.DesignNo warnings★ 1.4K↓ —
- eccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when running an ECCV campaign end to end — the even-year calendar from February registration to the September conference, the retargeting triangle to CVPR and ICCV seen from the ECCV seat, where the 2026 cycle stands today, and backward planning a 2028 submission from the March deadline.ProductivityNo warnings★ 1.4K↓ —
brief-builder
mohitagw15856/pm-claude-skills
PlanningUpdated 4 hours ago
From the author
Interview the user with sharp, one-at-a-time questions to turn a vague request into a tight, complete brief any other skill can run on. Use when a request is fuzzy, under-specified, or 'help me think this through', or before running a skill that needs inputs the user hasn't given. Produces a structured brief (goal, audience, constraints, success criteria) and hands off to the right skill — by interrogating, not guessing.
Install
npx skills add mohitagw15856/pm-claude-skills --skill brief-builder -a claude-code
Installs to .claude/skills/brief-builder/ · 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 (1)
- SKILL.md