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,492 skills from 2,391 repositories · updated 7 hours ago
48,451 skills
- oma-docsNewfirst-fluke/oh-my-agentCheck documentation references, sync docs to code changes, and detect translation drift. Use for documentation maintenance in a repository.EngineeringNo warnings★ 1.4K↓ —
- oma-academic-writingfirst-fluke/oh-my-agentDraft and revise academic prose against a rubric, evidence, and citation requirements. Use for essays, reports, literature reviews, or academic style audits.WritingNo warnings★ 1.4K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint tTestingNo warnings★ 1.6K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint TestingNo warnings★ 1.6K↓ —
- using-aegisGanyuanRan/AegisUse when starting a turn or checking Aegis skill routing.OtherNo warnings★ 1.4K↓ —
- ui-ux-governanceGanyuanRan/AegisUse when designing, changing, or reviewing user-facing interfaces or interaction flows, including API changes that alter visible states or recovery. Backend-only work without user-facing effects stays on its existing route.DesignNo warnings★ 1.4K↓ —
- receiving-code-reviewGanyuanRan/AegisUse when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.EngineeringNo warnings★ 1.4K↓ —
- communicating-conciselyGanyuanRan/AegisUse when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.OtherNo warnings★ 1.4K↓ —
- test-driven-developmentGanyuanRan/AegisUse when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.TestingNo warnings★ 1.4K↓ —
- subagent-driven-developmentGanyuanRan/AegisUse when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise inline. Ad-hoc 2+ tasks without a plan use dispatching-parallel-agents.MarketingNo warnings★ 1.4K↓ —
- oma-architecturefirst-fluke/oh-my-agentEvaluate system boundaries and architectural tradeoffs. Use for architecture decisions, design reviews, and ADRs.PlanningNo warnings★ 1.4K↓ —
- oma-explanationfirst-fluke/oh-my-agentCreate an offline HTML explanation of a code change (diff, PR, branch) or of a topic, system, or question. Use when a visual walkthrough document is requested.EngineeringNo warnings★ 1.4K↓ —
- establishing-project-contextGanyuanRan/AegisUse when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.ProductivityNo warnings★ 1.4K↓ —
- verification-before-completionGanyuanRan/AegisUse when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.EngineeringNo warnings★ 1.4K↓ —
- brooks-reviewUpdatedhyhmrright/brooks-lintPR 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.EngineeringNo warnings★ 1.6K↓ —
- brooks-debtUpdatedhyhmrright/brooks-lintTech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.DevOpsNo warnings★ 1.6K↓ —
- brooks-testUpdatedhyhmrright/brooks-lintTest quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.TestingNo warnings★ 1.6K↓ —
- oma-scholarfirst-fluke/oh-my-agentSearch academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.ScienceNo warnings★ 1.4K↓ —
- oma-searchfirst-fluke/oh-my-agentFind external documentation, web sources, or remote code with citations. Local code navigation uses the configured code tools.EngineeringNo warnings★ 1.4K↓ —
- build-and-verifydaveebbelaar/bamaBuild a SwiftUI macOS app from the command line, install it, and check light and dark window snapshots of every page before calling a change done. Use after any UI code change, when a build fails, or when the user asks to run, screenshot, or check the app.DesignNo warnings★ 1.5K↓ —
- brooks-auditUpdatedhyhmrright/brooks-lintArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.PlanningNo warnings★ 1.6K↓ —
- ux-designdaveebbelaar/bamaUX pass for one feature of a macOS app, covering names, flow, where it opens (inline, popover, sheet, window, alert), states, words, hover help, accessibility, and AI features. Use before coding a story that adds a screen, an action, or text, when user-stories or improve-loop call it, or when the user asks for a UX review, clearer wording, better names, or whether something should be a modal.DesignNo warnings★ 1.5K↓ —
- oma-voicefirst-fluke/oh-my-agentGenerate or transcribe speech with Voicebox or VoiceStudio, or process existing audio locally. Use for narration, transcripts, timed speech, and loudness conversion; video editing uses oma-video.MediaNo warnings★ 1.4K↓ —
- brooks-sweepUpdatedhyhmrright/brooks-lintFull-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without code changes; single-dimension reviews (use the focused skill instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.TestingNo warnings★ 1.6K↓ —
rss-camera-ready
brycewang-stanford/Awesome-Journal-Skills
PlanningUpdated Sep 27, 2026
From the author
Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的 Claude Code/Codex 期刊技能包，从选题、识别策略到表格规范与审稿回复全流程，助你快速发论文。
The frontmatter could not be read (invalid YAML: YAMLParseError: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Use when convert); the folder name is shown instead.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a claude-code
Installs to .claude/skills/rss-camera-ready/ · 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