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 4 hours ago
48,055 skills
- mcp-server-builderalirezarezvani/claude-skillsUse when exposing an API as an MCP server or scaffolding a new MCP server in Python or TypeScript, before hand-writing tool wrappers. Generates tools from OpenAPI with openapi_to_mcp.py and validates them with mcp_validator.py.WritingNo warnings★ 29.2K↓ —
- analyticsmicrosoft/power-platform-skillsUse when a Process Mining overview, initial process selection, or an analytical follow-up needs routing.DataNo warnings★ 1.1K↓ —
- sno-mem-cursorsno-ai/sno-stationUse Sno memory from Cursor through four explicit commands.ProductivityNo warnings★ 1.1K↓ —
- asc-ad-hoc-distributionrorkai/app-store-connect-cli-skillsPrepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.MarketingNo warnings★ 1.1K↓ —
- design-systemdaveebbelaar/bamaAccent color and design system for a macOS app, from the app's accent and the accent picker in Settings to Swift tokens in code plus a design/DESIGN-SYSTEM.md that says which token to use when. Use when the user wants a brand or accent color, wants people to pick a color, when an app has more than a few screens, when screens drift apart or animations feel inconsistent, or when the user asks for themes, a style guide, or design tokens.DesignNo warnings★ 1.4K↓ —
- health-checkhoangsonww/Claude-Code-Agent-MonitorRun comprehensive health checks on the Claude Code Agent Monitor system. Validates dashboard API, database, WebSocket, hooks, and disk usage. Use to verify the monitoring setup is working correctly.DataNo warnings★ 1.1K↓ —
- all-hands-deckmohitagw15856/pm-claude-skillsBuild an all-hands that lands with everyone from intern to VP — the mixed-altitude structure (the story for all, the numbers for some), the wins-with-names section done right, the hard-news slide handled straight, and the Q&A design that gets real questions. Use when asked build the all-hands deck, make the monthly town hall not boring, how do we share the numbers with everyone, or announce this change at all-hands. Produces the segment structure, the altitude-mixed content rules, the hard-news handling, and the Q&A mechanics.DocumentsNo warnings★ 1.5K↓ —
- 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↓ —
- casefilehashgraph-online/awesome-codex-pluginsUse when tracking security investigations, bug bounty findings, CTF leads, audit evidence, exploit chains, dead ends, or reports in the Casefile ledger through Codex.SecurityNo warnings★ 1.5K↓ —
- 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↓ —
- asc-app-create-uirorkai/app-store-connect-cli-skillsCreate a new App Store Connect app record via browser automation. Use when there is no public API for app creation and you need an agent to drive the New App form.DesignNo warnings★ 1.1K↓ —
- asc-whats-new-writerrorkai/app-store-connect-cli-skillsGenerate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.WritingNo warnings★ 1.1K↓ —
- 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↓ —
- brooks-testhyhmrright/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↓ —
- write-outreachgooseworks-ai/goose-skillsCold outreach a person sends to business buyers: email and LinkedIn sequences, a first line per prospect, reply and objection answers, and a read of replies. Use when the marketer says "write a cold email sequence", "what do I send to this list", "write LinkedIn messages for these leads", "how do I reply to this prospect" or "handle this objection", "reply to this demo request", "win back or reconnect with accounts that churned or went quiet", or "why is nobody replying to my outreach". Drafts only; the marketer sends from their own tool. Not for finding the people — use research-audience; not for emails to subscribers or users, or consumer win-back — use email-lifecycle.WritingNo warnings★ 1.3K↓ —
- interviewalirezarezvani/claude-skillsUse when someone has an agent idea to scope before launch ('help me scope an agent'). Interviews them about the one job and writes a build sheet with build_sheet_builder.py, checked by primitives_validator.py; no API key needed.PlanningNo warnings★ 29.2K↓ —
- followup-sweepmohitagw15856/pm-claude-skillsSweep the user's REAL mail and calendar for dropped balls — threads awaiting their reply, promises they made, and replies they're owed — then draft the nudges. Use when asked what am I forgetting, what have I not replied to, who owes me a reply, or chase my open threads in Cowork. Reads sent/received mail via the Gmail connector and recent events via Calendar, finds the open loops, and produces a follow-up-list artifact plus ready-to-send draft nudges.ProductivityNo warnings★ 1.5K↓ —
- brooks-debthyhmrright/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↓ —
- scenario-sparc3dscenario-labs/skillsUse when turning images or photos into 3D meshes with Sparc3D models on Scenario via MCP: single-image or multi-view image-to-3D, watertight meshes for game assets, AR/VR, or 3D printing, mesh-only versus PBR-textured output, face count targets, resolution tiers, or reconstructing human heads and busts with the Portrait variants. Keywords: Sparc3D 2.1 and 2.0, Hitem3D, image to 3D, img23d, multiview, watertight, PBR, GLB, OBJ, STL, FBX.MediaNo warnings★ 1.5K↓ —
- product-showcasejezweb/claude-skillsGenerate a comprehensive marketing website for a web app — multi-page with real screenshots, animated GIF walkthroughs, feature deep-dives, and workflow demonstrations. Browses the running app, captures screens and sequences, and produces a deployable site that actually teaches people what the product does. Especially useful for complex or agentic apps that are hard to explain. Triggers: 'showcase site', 'product page', 'show off the app', 'marketing site', 'demo site', 'product showcase', 'explain the app', 'how do I market this'.DevOpsNo warnings★ 1.1K↓ —
- oma-skill-creationfirst-fluke/oh-my-agentCreate or revise OMA skills and their references. Use for skill routing, execution contracts, conditional loading, and authoring validation.OtherNo warnings★ 1.4K↓ —
- asc-id-resolverrorkai/app-store-connect-cli-skillsResolve App Store Connect IDs (apps, builds, app and digital-goods versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.OtherNo warnings★ 1.1K↓ —
- improve-search-visibility-page-and-foundation-checkgooseworks-ai/goose-skillsStep of the improve-search-visibility playbook: audits site indexing, crawling, technical and page issues at the requested scope, or checks pages behind lost visibility questions. Run improve-search-visibility instead; not for direct use.BrowserNo warnings★ 1.3K↓ —
- ops-inspectorTencentCloudBase/CloudBase-AI-ToolkitAIOps-style CloudBase inspection skill. Use when users need health checks, log diagnosis, alarm interpretation (CPU alert normal?, peak QPS), metrics via queryEnv(action=metrics), fault playbooks for 429 / AI model 429 / function timeout / function 404 / ACCESS_TOKEN_INVALID / zero invocations, or a scheduled patrol that reports only new or worse findings. Triggers on 巡检, 诊断, 告警, 峰值 QPS, 限频, 调用量为 0, 定时巡检, 每天检查, 值守, troubleshooting.OtherNo warnings★ 1.2K↓ —Also in 4 other repos
ipsn-workflow
brycewang-stanford/Awesome-Journal-Skills
From the author
Use when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a claude-code
Installs to .claude/skills/ipsn-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