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,534 skills from 2,407 repositories · updated 20 minutes ago
48,435 skills
- cav-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted CAV (Computer Aided Verification) paper for its Springer LNCS open-access camera-ready, covering de-anonymization for the previously double-blind categories, the LNCS llncs template and Springer metadata (ORCID, author order, running heads), the copyright/open-access forms, integrating reviewer-required changes without scope creep, permanentizing artifact links, and the AEC badge handoff.ScienceNo warnings★ 1.4K↓ —
- imc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing ACM IMC measurements, covering representative vantage points, honest ground truth, longitudinal design for a moving Internet, safe and ethical active measurement, coverage-bias quantification, provenance pinning, and matching the measurement to the shape of each claim about the real Internet.DesignNo warnings★ 1.4K↓ —
- atc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds, fair baselines, end-to-end plus microbenchmark results, tail-latency and variance reporting, workload realism, and honest cost accounting.ScienceNo warnings★ 1.4K↓ —
- acl-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted ACL main-conference or Findings paper for camera-ready, covering the extra content page, de-anonymization and acknowledgements, AI-assistance disclosure, keeping the Limitations section, ACL Anthology metadata and CC BY 4.0 publication, meta-review-driven edits, and presentation-mode logistics.ScienceNo warnings★ 1.4K↓ —
- sci-citationbrycewang-stanford/Awesome-Journal-SkillsUse when converting a reference list to Science (AAAS) numbered style — italic numbers cited in order of appearance, a single continuous list that the Supplementary Materials share, full author lists rather than "et al." in the bibliography, and abbreviated journal titles. Late-stage style pass for the flagship AAAS weekly.ScienceNo warnings★ 1.4K↓ —
- imc-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted ACM IMC paper for the proceedings, covering systematic de-anonymization, finalizing the Ethics and artifact-availability statements, permanentizing dataset and code links to DOI-issuing archives, satisfying the availability shepherd, Community Contribution Award eligibility, and ACM production checks.ScienceNo warnings★ 1.4K↓ —
- nejm-submissionbrycewang-stanford/Awesome-Journal-SkillsUse as the final preflight before submitting to NEJM — a complete clinical checklist across significance, registration, reporting guidelines, abstract, statistics, display items, ethics, references, and required files. Bundles a checklist and a clinical cover-letter template.ScienceNo warnings★ 1.4K↓ —
- popl-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when preparing a POPL submission for the single July HotCRP deadline — auditing the 25-pages-of-text acmsmall cap, summary-rejection format rules, full double-blind hygiene for theory papers with public proof repositories, dual-submission exposure, and the final-days upload order before the AoE cutoff.ProductivityNo warnings★ 1.4K↓ —
- jama-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when running the final pre-submission preflight for a JAMA manuscript — word/format limits, required statements, checklist and flow-diagram files, disclosures, and portal steps. Verifies completeness; it does NOT write or analyze content.WritingNo warnings★ 1.4K↓ —
- sci-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after Science 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.ScienceNo warnings★ 1.4K↓ —
- osdi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.ProductivityNo warnings★ 1.4K↓ —
- stoc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.ProductivityNo warnings★ 1.4K↓ —
- launch-nemo-rlNVIDIA/skillsPlaybook for launching, monitoring, stopping, and debugging NeMo-RL recipes on a Kubernetes cluster via the nrl-k8s CLI. Covers ephemeral vs long-lived RayCluster modes, iterating on runs, and debugging hung or failed training jobs.DevOpsNo warnings★ 3.9K↓ —
- nsdi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.ProductivityNo warnings★ 1.4K↓ —
- focs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.ProductivityNo warnings★ 1.4K↓ —
- podc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-vs-Brief-Announcement decision along the way.ProductivityNo warnings★ 1.4K↓ —
- icml-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning or sequencing an ICML manuscript workflow end to end - from topic selection and drafting through OpenReview submission, double-blind review, author response, camera-ready, PMLR publication, public original-submission release, and rerouting decisions. Use when you need the next ICML skill, the official page to reopen, or the blocking gap for the current stage.ProductivityNo warnings★ 1.4K↓ —
- itcs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.ProductivityNo warnings★ 1.4K↓ —
- vis-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.ProductivityNo warnings★ 1.4K↓ —
- pnas-figuresbrycewang-stanford/Awesome-Journal-SkillsUse to finalize PNAS display items — column-width sizing (~9 / 11.4 / 18 cm), minimum font sizes, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, image integrity, and color-mode notes. Enforces figure rigor before submission.MediaNo warnings★ 1.4K↓ —
- lancet-fitbrycewang-stanford/Awesome-Journal-SkillsUse when scoping a project and before any writing, to stress-test whether a study clears The Lancet's bar — clinically or public-health important, globally relevant, and likely to change practice or policy, often with an equity lens. Decides The Lancet vs a Lancet family title vs another general medical journal.TestingNo warnings★ 1.4K↓ —
- cell-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.OtherNo warnings★ 1.4K↓ —
- runway-plannermohitagw15856/pm-claude-skillsTurn burn and cash into a clear runway picture and a raise decision — months left, default-alive vs default-dead, and what to cut or change. Use when asked to calculate runway, model burn rate, decide when to raise, figure out if the company is default-alive, or plan a scenario with hiring/cuts. Produces the runway math, a default-alive verdict, and dated trigger points for raising or acting. Not financial advice.PlanningNo warnings★ 1.5K↓ —
- rubric-buildermohitagw15856/pm-claude-skillsCreate a clear grading rubric with criteria and performance-level descriptors that make scoring fair, fast, and consistent. Use when asked to build a rubric, create grading criteria, design an assessment scoring guide, or make grading more objective. Produces an analytic rubric table (criteria × performance levels) with concrete, observable descriptors and a points scheme — plus a short version students can self-check against.DesignNo warnings★ 1.5K↓ —
brooks-review
hyhmrright/brooks-lint
EngineeringUpdated 15 hours ago
From the author
PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.
Install
npx skills add hyhmrright/brooks-lint --skill brooks-review -a claude-code
Installs to .claude/skills/brooks-review/ · 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
- pr-review-guide.md