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,415 skills from 2,407 repositories · updated 2 hours ago
49,415 skills
- research-audience-segment-passgooseworks-ai/goose-skillsStep of the research-audience playbook: the worker brief for researching one buyer group, returning notes in a fixed shape. Run research-audience instead; not for direct use.ScienceNo warnings★ 1.3K↓ —
- ap-intakeSpielewoy/autoprompt-skillReport the compatibility redirect to `C0`; this retired role cannot perform new work.OtherNo warnings★ 1.2K↓ —
- no-ai-slophuytieu/COG-second-brainEdit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.WritingNo warnings★ 1.3K↓ —
- cell-star-methodsbrycewang-stanford/Awesome-Journal-SkillsUse to build Cell's mandatory STAR Methods — the Key Resources Table, the three Resource Availability subsections, Experimental Model and Subject Details, Method Details, and Quantification and Statistical Analysis, in the exact required order.OtherNo warnings★ 1.4K↓ —
- cikm-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation logistics.ScienceNo warnings★ 1.4K↓ —
- asplos-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.ProductivityNo warnings★ 1.4K↓ —
- influencer-marketingkostja94/marketing-skillsWhen the user wants to plan, implement, or optimize influencer marketing strategy. Also use when the user mentions "influencer marketing," "KOL," "creator partnership," "brand ambassador," "sponsored content," "influencer campaign," "micro-influencer," "influencer outreach," "creator collaboration," or "influencer deal." For creator programs, use creator-program.MarketingNo warnings★ 1.1K↓ —
- atc-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) submission is evaluated — the two-round extended-abstract model, the round-one gate by two reviewers, the round-two read by 3-4 reviewers, double-blind reviewing, rebuttal, conditional acceptance with shepherding, and how ATC differs from OSDI/SOSP/NSDI.EngineeringNo warnings★ 1.4K↓ —
- cav-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how a CAV (Computer Aided Verification) submission is evaluated, covering the two-stage reviewing process (two reviews then an early-reject filter, then two more reviews with a rebuttal), the partial double-anonymity by category, the accept/reject outcome, the optional non-conditional artifact evaluation, and how CAV differs from TACAS and FMCAD.EngineeringNo warnings★ 1.4K↓ —
- simplifyfcakyon/claude-codex-settingsThis skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code across reuse, simplification, efficiency, and altitude, or grants an explicit one-commit bypass. Not for correctness bugs.EngineeringNo warnings★ 1.2K↓ —
- ase-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how an ASE (IEEE/ACM Automated Software Engineering) research submission is evaluated, covering double-anonymous review, the early-rejection stage before rebuttal, the Accept / Revision / Reject outcomes, the criteria-bound revision round, and how ASE's process differs from FSE's PACMSE Major Revision, ICSE's cycles, and ISSTA's rounds.EngineeringNo warnings★ 1.4K↓ —
- vis-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an IEEE VIS paper for a task-grounded visualization contribution on the first page, a design rationale that ties each visual encoding and interaction to a task, evaluation matched to the contribution type, honest limitations, and disciplined use of the VGTC/TVCG 9+2 page budget for a paper that will be read as an IEEE TVCG journal article.WritingNo warnings★ 1.4K↓ —
- vldb-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a VLDB paper, covering workload and dataset realism at scale, competitor tuning fairness, scalability curves versus single points, tail-latency and throughput reporting, ablations that isolate the mechanism, and the loss-case disclosure PVLDB reviewers look for first.ScienceNo warnings★ 1.4K↓ —
- wacv-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing WACV experiments, covering Applications-track systems evidence (latency, power, robustness under real constraints) versus Algorithms-track matched-baseline novelty, comparative assessment under the deployed condition, uncertainty over seeds and sessions, ablations, and evidence that survives the two-round review.DevOpsNo warnings★ 1.4K↓ —
- aaai-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.ScienceNo warnings★ 1.4K↓ —
- aaai-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.ScienceNo warnings★ 1.4K↓ —
- wsdm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a WSDM paper - offline ranking and recommendation metrics with bias controls, temporal-split protocols for interaction logs, baseline selection from recent WSDM/SIGIR/KDD editions, ablations that isolate the mechanism, efficiency reporting, and online-evidence framing.ScienceNo warnings★ 1.4K↓ —
- sosp-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks with end-to-end and failure runs, reporting tails and overheads honestly, and isolating the mechanism the design credits.DesignNo warnings★ 1.4K↓ —
- vis-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers routinely watch, the one-week supplemental deadline extension, double-blind supplemental anonymization, and how to split a visualization paper between the reviewed pages and the archive.MediaNo warnings★ 1.4K↓ —
- socc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing ACM SoCC evaluations, covering real or realistic deployments over simulation, production or representative workloads and traces, tail-latency and cost as first-class metrics, fair tuned baselines, scale and multi-tenancy behavior, reproducible measurement pipelines, and matching evidence to the shape of each cloud claim.DevOpsNo warnings★ 1.4K↓ —
- push-to-forked-prhoangsonww/Claude-Code-Agent-MonitorPush the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is usually the upstream). Invoke when the user says things like "push straight to PROtherNo warnings★ 1.1K↓ —Also in 2 other repos
- stoc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when judging whether computation belongs in a STOC (ACM Symposium on Theory of Computing) paper at all — STOC accepts on theorems, with no empirical-evaluation expectation — and when it does, scoping it as certified proof computation, constructive search, or clearly labeled illustration rather than benchmarking.MediaNo warnings★ 1.4K↓ —
- second-brain-metricsundefined-ui/second-brain-osRecord a dated snapshot of the vault's health numbers and compare against previous snapshots so trends are visible. Use this skill for a monthly or quarterly check, when the user asks whether the vault is improving, or asks to track its numbers over time. Do NOT use for a one-off graph analysis, which is second-brain-graph, or for structural repairs.OtherNo warnings★ 1.4K↓ —
- chart-choicemohitagw15856/pm-claude-skillsPick the chart the data and the point actually need — the question-to-chart mapping (comparison, trend, composition, distribution, relationship), the honesty rules (axes, baselines, dual-axis traps), and the one-chart-one-point discipline. Use when asked what chart should I use, make this data visual, why does this chart feel misleading, or fix this graph for the deck. Produces the chart verdict with its reasoning, the honesty checklist applied, and the labeling that lets the chart travel without its author.DocumentsNo warnings★ 1.5K↓ —
vldb-experiments
brycewang-stanford/Awesome-Journal-Skills
From the author
Use when designing or auditing the evaluation of a VLDB paper, covering workload and dataset realism at scale, competitor tuning fairness, scalability curves versus single points, tail-latency and throughput reporting, ablations that isolate the mechanism, and the loss-case disclosure PVLDB reviewers look for first.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-experiments -a claude-code
Installs to .claude/skills/vldb-experiments/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Safety checks on SKILL.md
No warnings.
Why 88
Files (1)
- SKILL.md