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
- goose-product-photosgooseworks-ai/goose-skillsMake product photos (studio, lifestyle or on a model) of a brand's real products with GooseWorks in this chat. Start brand work with brand_knowledge_browse and follow the next_step in every answer.MediaNo warnings★ 1.3K↓ —
- workhashgraph-online/awesome-codex-pluginsUse for execution, debugging, verification, planning, and shipping when the user's Emulo working profile should guide the task. Do not use for design/UI/UX work, marketing or social writing, or Emulo setup/mining.DesignNo warnings★ 1.5K↓ —Also in 2 other repos
- drive-desktop-appreticlehq/reticleDrive and verify an Electron or Tauri desktop app from the inside, including the main-process and Rust IPC calls a browser tool cannot see. Use when a desktop app needs testing, when a feature works in the browser but not in the packaged app, when an IPC or invoke call needs proving, when a desktop screenshot or visual diff is wanted, or when you need a headless run of a desktop UI in CI.TestingNo warnings★ 1.2K↓ —
- seonix-seoNewhashgraph-online/awesome-codex-pluginsWork on the SEO of a website that is connected to Seonix through the seonix MCP server - audit it, find what to fix, read Search Console traffic, check a draft. Use when the user asks to improve SEO, organic traffic, rankings or content for a site that is in Seonix, mentions Seonix, Site Health, the fix plan or Search Console data from Seonix, or asks which pages or queries to work on next.MarketingNo warnings★ 1.5K↓ —
- verify-cli-runreticlehq/reticleProve that a command-line tool actually did what it said, instead of trusting its exit code and its output. Snapshots the filesystem before and after, names the expected consequence in advance, and returns one of four verdicts with what could not be seen. Use after running a build, a migration, a scaffolder, a formatter, a codegen step, or an AI coding CLI; when a command printed success and you are about to report "done"; when you are about to write "exit code 0, so it worked"; or when a tool claims it edited files. Needs nothing installed.EngineeringNo warnings★ 1.2K↓ —
- openspec-proposeMemeMeow-Studio/MemeMeowPropose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.DesignNo warnings★ 1.3K↓ —
- scrapecreators-apigooseworks-ai/goose-skillsProvider reference for collecting public profiles, posts, comments, transcripts, trends, and ad-library data from major social platforms through ScrapeCreators. Use as a dependency of research workflows, not as the final user-facing deliverable.BrowserNo warnings★ 1.3K↓ —
- test-error-statesreticlehq/reticleForce the states a happy-path run never reaches (a failing API, an empty list, a slow request, a timeout, an expired session, a toast that auto-dismisses) and check the UI actually handles them. Use when error handling was written but never run, when a loading or empty state needs verifying, when a bug only happens on a slow connection, or when a timer, poll, debounce or retry needs testing without sleeping.TestingNo warnings★ 1.2K↓ —
- releasehyhmrright/brooks-lintCut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.WritingNo warnings★ 1.6K↓ —
- releasehyhmrright/brooks-lintCut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.WritingNo warnings★ 1.6K↓ —
- brooks-reviewhyhmrright/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↓ —
- minutes-searchsilverstein/minutesSearch past meeting transcripts and voice memos for specific topics, people, decisions, or ideas. Use this whenever the user asks "what did we discuss about X", "find that meeting where we talked about Y", "what did Alex say", "did we decide on", "what was that idea about", or any question that could be answered by searching their meeting history. Also use for "do I have any notes about" or "check my meetings for".PlanningNo warnings★ 1.6K↓ —Also in 1 other repo
- minutes-debriefsilverstein/minutesPost-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.OtherNo warnings★ 1.6K↓ —Also in 1 other repo
- postgresql-development-cloudbaseUpdatedTencentCloudBase/CloudBase-AI-ToolkitUse when building, debugging, or evaluating CloudBase PostgreSQL / CloudBase PG / PG mode apps, including Postgres schema setup, queryPgDatabase/managePgDatabase, JS SDK v3 app.rdb() CRUD/RPC, PG HTTP API fallback, RLS-style permissions, username-password auth, and Web CMS/admin CRUD flows backed by CloudBase PG.DataNo warnings★ 1.2K↓ —Also in 4 other repos
- minutes-mcp-recallsilverstein/minutesRoute meeting-recall questions to the right Minutes MCP tool.OtherNo warnings★ 1.6K↓ —Also in 1 other repo
- research-marketgooseworks-ai/goose-skillsMarket research and brand watch: which market the brand is in, how big the reachable part is, what's changing, how buyers buy and what they pay, what people are saying now, and what it means for positioning. Use when the marketer asks for market research, "how big is my market", "what's changing in my category", "what do others charge", "what are people saying about us", "is there demand for <idea>", or "watch my brand / tell me if something blows up" (alerts only, risk first). Also writes positioning choices and finished messages ("position my product", "write our positioning"). Researches first, asks only decisions at the end, and saves the output to the brand. Not for who the buyers are and their own words — use research-audience; not for a deep look at rivals — use research-competitors.ScienceNo warnings★ 1.3K↓ —
- 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↓ —
- oma-designfirst-fluke/oh-my-agentAI design specialist skill with DESIGN.md management, anti-pattern enforcement, optional Stitch MCP integration, and component library guidance. Covers typography, color systems, motion design (motion/react, GSAP, Three.js), responsive-first layouts, and accessibility (WCAG 2.2).DesignNo warnings★ 1.4K↓ —
- blog-publishhuytieu/COG-second-brainWrite and publish a post to your own static blog end to end: content checklist (embedded links, optional TL;DR), per-post ASCII art, an agent-readable markdown twin, deploy, and social distribution. Use when you say "write a blog post", "publish this to my blog", or "push this post to socials".WritingNo warnings★ 1.3K↓ —Also in 1 other repo
- email-lifecyclegooseworks-ai/goose-skillsLifecycle email, SMS and push: audits the list and deliverability, then writes the flows this kind of business needs first, loadable as-is in your own tool, plus segments, cadence and this week's broadcasts. Never sends anything. Use when: set up my welcome and abandoned-cart emails; trial onboarding or waitlist launch emails; win back lapsed customers; plan this week's emails and texts; push notifications for my app; why are my emails going to spam; plan our Black Friday email and SMS sends; a send went wrong. Not for cold outreach to prospects — use write-outreach; not the editorial newsletter issue — use make-content; not the whole cross-channel Black Friday plan — use plan-campaign.ProductivityNo warnings★ 1.3K↓ —
- mariadb-operator-pr-reviewmariadb-operator/mariadb-operatorPerform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator PR number or URL and wants any kind of judgment on it — "review this PR", "what do you think of #1234", "is this safe to merge", "assess this diff", "take a look at this change" — even if they don't literally say "review".EngineeringNo warnings★ 1K↓ —
- metronomefcakyon/claude-codex-settingsGuides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.DesignNo warnings★ 1.2K↓ —
- deployment-config-guidealibaba/skill-upAsk for missing deployment settings and summarize the requested configuration without deploying it.DevOpsNo warnings★ 1.4K↓ —Also in 1 other repo
- blueprinthashgraph-online/awesome-codex-pluginsTurn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".PlanningNo warnings★ 1.5K↓ —
image-processing
jezweb/claude-skills
From the author
Process images for web development — resize, crop, trim whitespace, convert formats (PNG/WebP/JPG), optimise file size, generate thumbnails, create OG card images. Uses Pillow (Python) — no ImageMagick needed. Trigger with 'resize image', 'convert to webp', 'trim logo', 'optimise images', 'make thumbnail', 'create OG image', 'crop whitespace', 'process image', or 'image too large'.
Install
npx skills add jezweb/claude-skills --skill image-processing -a claude-code
Installs to .claude/skills/image-processing/ · 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