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 11 hours ago
48,362 skills
- writing-relayflowsAgentWorkforce/relayInfrastructure for coding agentsWritingNo warnings★ 1.1K↓ —
- audit-decisionsNewdzhng/skillsAudit the decisions an implementing agent made, not its diff — a pure audit that traces the session's history into a decisions ledger, changes no code, and never blocks an unsupervised run. Working code still embeds architecture the user never chose; surface it because future work inherits it. Use when the user wants to review the decisions the AI made on their behalf, before merging or committing AI-implemented work, when integrating a delegated subagent's pass, or when a fix "works" but might be a point fix.PlanningNo warnings★ 1.4K↓ —
- architectNewhashgraph-online/awesome-codex-pluginsSettle structure before writing logic. Ground in the current code, get competing design sketches (types, signatures, modules, trust boundaries) through arena, implement against the merged sketch, scrap it on a friction pattern. Use for "architect this", "design X first".PlanningNo warnings★ 1.5K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.WritingNo warnings★ 1.3K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.WritingNo warnings★ 1.3K↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivityNo warnings★ 1.3K↓ —
- openspec-archive-changeMemeMeow-Studio/MemeMeowArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.ProductivityNo warnings★ 1.3K↓ —
- 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↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivityNo warnings★ 1.3K↓ —Also in 1 other repo
- 01-auto-arenaagentscope-ai/OpenJudgeAutomatically evaluate and compare multiple AI models or agents without pre-existing test data. Generates test queries from a task description, collects responses from all target endpoints, auto-generates evaluation rubrics, runs pairwise comparisons via a judge model, and produces win-rate rankings with reports and charts. Supports checkpoint resume, incremental endpoint addition, and judge model hot-swap. Use when the user asks to compare, benchmark, or rank multiple models or agents on a custom task, or run an arena-style evaluation.TestingNo warnings★ 1K↓ —
- 00-arena-routeragentscope-ai/OpenJudgeUse when the user wants to compare or benchmark multiple LLMs/agents arena-style but it's unclear which specific workflow fits — a general-purpose win-rate comparison on a custom task, or a benchmark specifically about reference/citation hallucination rate. Also use when the user mentions model arena, agent arena, pairwise model comparison, win-rate ranking, or comparing models on a task and hasn't specified whether that task is generic or about citation accuracy. This skill is the entry router for the arena-eval suite: it asks one diagnostic question when needed, then recommends the workflow or workflows needed to cover the request.PlanningNo warnings★ 1K↓ —
- cwd-rolluphoangsonww/Claude-Code-Agent-MonitorRoll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects.EngineeringNo warnings★ 1.1K↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- operating-livekit-agentsfcakyon/claude-codex-settingsDeploys and operates a LiveKit agent in production: shipping a version to LiveKit Cloud and rolling it back, secrets and configuration, the worker process model and prewarming, safe async inside worker processes, provider timeouts and degradation, graceful shutdown, SDK upgrades, and observability. Use when the user says "deploy my agent", "roll back the deployment", "tail the agent logs", "the first call after a restart is slow", "attached to a different loop / event loop is closed", "prewarm the VAD", "shut down without dropping calls", "upgrade livekit-agents safely", "correlate logs by session", or is changing an agent codebase that is already live. Not for designing the agent (building-livekit-agents) or reproducing one bad conversation locally (debugging-livekit-agents).DevOpsNo warnings★ 1.2K↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
pods-submission
brycewang-stanford/Awesome-Journal-Skills
ScienceUpdated Sep 27, 2026
From the author
Use when auditing an ACM PODS research submission for EasyChair readiness, covering the chosen cycle's abstract-then-paper deadlines, the acmsmall[review,anonymous] format and 15-page budget, the at-submission proof appendix, lightweight double-anonymity, the declared conflicts of interest, PACMMOD-track publication, and desk-risk triage before the AoE cutoff.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-submission -a claude-code
Installs to .claude/skills/pods-submission/ · 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