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 10 hours ago
48,055 skills
- scenario-texturesscenario-labs/skillsUse when a task involves game textures or materials through the Scenario MCP: seamless or tileable textures, themed texture packs (brick, wood, stone, floors, hand-painted), PBR materials (albedo, metallic, roughness, normal) on 3D assets, retexturing a mesh, material iteration from reference images, texture upscaling that must preserve tiling, or sizing textures for game engines. Keywords: seamless texture, tileable, PBR, material, retexture, texture upscale, surface.ProductivityNo warnings★ 1.5K↓ —
- email-triagemohitagw15856/pm-claude-skillsTriage a Gmail inbox down to only what needs you. Use when asked to triage email, clear an inbox, find what needs a reply, or summarise recent mail. Produces a prioritised list of items needing action — replies, decisions, follow-ups — for a configurable window (default last 8 hours), filtering out receipts, notifications, and newsletters.ProductivityNo warnings★ 1.5K↓ —
- using-git-worktreesGanyuanRan/AegisUse when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.EngineeringNo warnings★ 1.4K↓ —
- icdm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical evaluation for an ICDM (IEEE International Conference on Data Mining) paper - mining-task definition, strong and fairly-tuned baselines, ablations that isolate the named mechanism, scalability curves that test scale claims, and discovery-validity checks that separate real findings from evaluation artifacts.TestingNo warnings★ 1.4K↓ —
- icse-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ICSE research-track paper, covering subject and benchmark selection, baseline fairness, statistical tests and effect sizes as SE reviewers expect them, qualitative-methods rigor, ablations for AI-based techniques, and threats-driven study design.TestingNo warnings★ 1.4K↓ —
- pm-skillsalirezarezvani/claude-skillsUse when a delivery request needs routing across the project-management skills (sprints, portfolio health, Jira, Confluence, comms), or to run a delivery loop. Routes with pm_goal_router.py, bridges Jira data with jira_snapshot_bridge.py and gates with delivery_loop_gate.py.OtherNo warnings★ 29.2K↓ —
- audit-testsdzhng/skillsAudit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests, investigating implementation coupling or test-only production hooks, reviewing the value of proposed coverage, or auditing an entire subsystem. Use write-tests to implement the resulting test changes.TestingNo warnings★ 1.4K↓ —
- write-docsdzhng/skillsWrite and edit project docs (README/markdown) as a glossary of principles, not a mirror of the code. Use when creating or revising a README; when a doc enumerates exact scenes, scenarios, helpers, class ids, file lists, or command/flag matrices the code already holds; when trimming narrative or changelog out of a doc; or when deduplicating overlapping docs and wiring a root doc to its sub-docs.WritingNo warnings★ 1.4K↓ —
- runtime-adaptersagentlas-ai/Agentlas-OSUse when creating Codex, Claude Code, Gemini CLI, Cursor, or AGENTS.md runtime adapters from one canonical agent core. Use whenever a generated repo needs multiple AI runtimes without duplicating instructions.EngineeringNo warnings★ 1.6K↓ —
- key-state-attributesno-ai/sno-stationChoose one offered state attribute for a stored statement about a named thing.OtherNo warnings★ 1.1K↓ —
- kdd-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising a KDD paper into the venue's register, where the first page names a data regime, a mechanism, and scale evidence, efficiency adjectives trace to design decisions, and two-column sigconf pages punish sprawl. Covers Research vs ADS voice, dataset-size discipline, assertive contribution bullets, and 8-page compression.WritingNo warnings★ 1.4K↓ —
- llm-runtime-architectureagentlas-ai/Agentlas-OSUse when designing how one canonical agent core runs across Codex, Claude Code, Antigravity, Cursor, and AGENTS.md-compatible tools.PlanningNo warnings★ 1.6K↓ —
- research-audiencegooseworks-ai/goose-skillsAudience research: who the buyers are, in their own words, where they gather and how to reach them — plus named prospect lists when asked. Use when the marketer says "research our audience", "who should we target", "mine our reviews", "why do people buy us or leave", "where does our audience hang out"; or for lists: "find 50 right-fit leads with emails", "find retailers or accounts to pitch", "score these leads / who do we call first", "who's looking for an alternative to X", "tell me when a past champion changes jobs". Reads the brand's own customer data first and delivers a readable report saved to the brand. Never contacts anyone. Not for market size or trends — use research-market; not for writing the messages — use write-outreach.ScienceNo warnings★ 1.3K↓ —
- fixing-flaky-testsamplifthq/openmeldGuides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.TestingNo 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↓ —
- setupfcakyon/claude-codex-settingsThis skill should be used when user asks to "set up QA", "create real integration tests", or "add project QA journeys" for websites, extensions, Android apps or backends.TestingNo warnings★ 1.2K↓ —
- 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↓ —
- marketing-pagesdzhng/skillsBest-practice rulebook for a marketing site's pages, organized by page class — campaign landers, product pages, programmatic SEO trees, editorial. Use when writing or updating a landing/marketing page, wiring a campaign lander to an attribution identifier, changing site-wide nav/footer links, touching sitemap/robots/agent-readable surfaces, or auditing a public site's indexing, reachability, and conversion setup.MarketingNo warnings★ 1.4K↓ —
- chro-advisoralirezarezvani/claude-skillsUse for people strategy: hiring plans, comp bands, org structure, performance or retention. Models hiring with hiring_plan_modeler.py and benchmarks pay with comp_benchmarker.py.PlanningNo warnings★ 29.2K↓ —
- writing-guidelinesvercel-labs/agent-skillsReview docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".OfficialWritingNo warnings★ 33.4K↓ —
- executing-plansGanyuanRan/AegisUse when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.PlanningNo warnings★ 1.4K↓ —
- cinematic-shotdzhng/skillsShoot software UI like a film. A sequence of hero shots, each a steep, oblique, extreme close-up of the interface floating in black, with a razor-thin focal plane, a slow motivated camera drift, and UI that acts on its own, hard-cut on the action, ending on one line of copy and a still logo. Use when asked for a launch video, product film, feature trailer, teaser, promo clip, hero shot, or any "cinematic" footage of an app or UI. This skill covers camera, framing, light, and edit. It is stack-agnostic.DesignNo warnings★ 1.4K↓ —
- implement-specdzhng/skillsImplement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints to periodically clean code, handoffs, priorities, and plan bloat before drift accumulates.PlanningNo warnings★ 1.4K↓ —
- create-prfcakyon/claude-codex-settingsThis skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".EngineeringNo warnings★ 1.2K↓ —
cvpr-workflow
brycewang-stanford/Awesome-Journal-Skills
From the author
Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the resubmission ladder across ICCV, ECCV, and the next CVPR.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-workflow -a claude-code
Installs to .claude/skills/cvpr-workflow/ · 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