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,105 skills from 2,358 repositories · updated 6 hours ago
48,055 skills
- cell-fitbrycewang-stanford/Awesome-Journal-SkillsUse when triaging a study before any writing — stress-tests whether it clears Cell's bar (a complete, mechanistic, hypothesis-driven story with multiple converging lines of evidence) or belongs at a sibling. Use this first to decide Cell vs Molecular Cell vs Cell Reports vs Cell Reports Medicine before investing in framing or figures.TestingNo warnings★ 1.4K↓ —
- iso27701Sushegaad/Claude-Skills-Governance-Risk-and-ComplianceExpert ISO 27701 Privacy Information Management System (PIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 27701:2025, ISO/IEC 27701:2019, privacy information management, PIMS certification, PII controller or processor obligations, privacy risk assessment, Statement of Applicability for privacy, privacy by design, data subject rights, DPIA, records of processing activities, transitioning from ISO 27701:2019, GDPR alignment with ISO 27701, or any privacy management system topic. Also trigger for questions about Annex A.1 (controller controls), A.2 (processor controls), A.3 (shared security controls), or implementing a standalone PIMS without ISO 27001. When in doubt, use this skill — it covers the full ISO 27701 lifecycle from gap assessment through certification.SecurityNo warnings★ 1K↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- test-auditfcakyon/claude-codex-settingsThis skill should be used when the user asks to "write a test", "review these tests", "audit tests", "prune low-value tests", or "find duplicate tests", and whenever writing, changing, reviewing, or sweeping tests. Gates new tests and audits low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.TestingNo warnings★ 1.2K↓ —
- write-skillsdzhng/skillsCreate or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.WritingNo warnings★ 1.4K↓ —
- close-specdzhng/skillsWhen a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).PlanningNo warnings★ 1.4K↓ —
- audit-agentsdzhng/skillsAudit or rewrite AGENTS.md so it holds only lasting principles. Run it only when the user asks for it by name; never invoke it on your own.OtherNo warnings★ 1.4K↓ —
- launch-videodzhng/skillsMake a showreel-grade motion-graphics launch video, with music, that introduces a CLI, library, or product from its repo. Use when asked for a launch, promo, sizzle, or showreel video, an animated intro for a project, or a video to post on X/social.MediaNo 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↓ —
- 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↓ —
- 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↓ —
- ctxctxrs/ctxUse ctx as working memory for prior agent work. Before starting or continuing work in an unfamiliar area, resuming earlier work, or revisiting an investigation, search prior sessions to ground yourself in earlier context. Use ctx blame to trace a line, file, commit, or PR to the agent session that produced it. Use when prior decisions, constraints, attempts, tool calls, transcript evidence, or code provenance may matter. Use ctx graph queries on indexed projects to follow calls and dependencies and understand what a change might affect.FinanceNo warnings★ 1.2K↓ —Also in 1 other repo
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- rendererdzhng/skillsArchitecture rules for GPU rendering with TypeGPU/WebGPU. Use when adding or changing render passes, shaders, frame orchestration, GPU resources, culling, terrain, shadows, or visual performance work.MediaNo warnings★ 1.4K↓ —
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.EngineeringNo warnings★ 1.4K↓ —
vis-experiments
brycewang-stanford/Awesome-Journal-Skills
DesignUpdated Sep 27, 2026
From the author
Use when designing or auditing IEEE VIS evaluations, covering how to match evidence to the contribution type (perceptual study, controlled user study, algorithm benchmark, design-study validation, qualitative work), controlled experiment design with power and effect sizes, CVD-safe and perceptually grounded encoding choices, task taxonomies, and provenance so a TVCG reviewer trusts the result.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-experiments -a claude-code
Installs to .claude/skills/vis-experiments/ · 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 (1)
- SKILL.md