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,417 skills from 2,407 repositories · updated 21 minutes ago
49,415 skills
- 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↓ —
- research-audience-account-sourcinggooseworks-ai/goose-skillsStep of the research-audience playbook: finds candidate accounts matching the fit definition, confirms gates, applies exclusions and dedupes. Run research-audience instead; not for direct use.ScienceNo warnings★ 1.3K↓ —
- 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↓ —
- add-clidashnanocoai/nanoclawAdd clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.EngineeringNo warnings★ 31.1K↓ —
- 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↓ —
- 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↓ —
- analyze-performance-call-and-learngooseworks-ai/goose-skillsStep of the analyze-performance playbook: calls ended tests, scores last week's calls, writes this week's kill/scale/hold calls and drafts learnings for the brand brain. Run analyze-performance instead; not for direct use.TestingNo warnings★ 1.3K↓ —
- analyze-performance-rank-and-readgooseworks-ai/goose-skillsStep of the analyze-performance playbook: ranks creative by angle, hook and format with spend gates, writes short per-channel reads and drafts what to make next. Run analyze-performance instead; not for direct use.WritingNo warnings★ 1.3K↓ —
- 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↓ —
- 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.3K↓ —
- add-table-to-offline-profilemicrosoft/power-platform-skillsInternal mobile-app workflow read and executed only by mobile orchestrators to add one Dataverse table to an existing Mobile Offline Profile.ProductivityNo warnings★ 1.1K↓ —
- skill-fusionmohitagw15856/pm-claude-skillsFuse two skills from this library into one hybrid brief for a task that sits between them — the meta-skill. Use when a task straddles two skills (a PRD that's also a pitch; a postmortem that must double as a board update) and running them separately would produce two documents where one is needed. Produces the fused operating brief: combined structure, merged quality bar, precedence rules for where the parents disagree, and the fused output itself if input was provided.PlanningNo warnings★ 1.5K↓ —
- run-organic-social-plan-calendargooseworks-ai/goose-skillsStep of the run-organic-social playbook: turns the audit, research and dated moments into a two-week grid of empty post slots. Run run-organic-social instead; not for direct use.PlanningNo warnings★ 1.3K↓ —
- run-paid-campaigns-apply-and-loggooseworks-ai/goose-skillsStep of the run-paid-campaigns playbook: stages the week's approval items, applies only what the marketer approves and keeps the change log. Run run-paid-campaigns instead; not for direct use.OtherNo warnings★ 1.3K↓ —
- desktop-zeromohitagw15856/pm-claude-skillsClear the desktop that's become a hundred-icon guilt mosaic — the fast triage that empties it today, the honest read of what the desktop was being used for (it's a to-do list wearing icons), and the replacement systems that keep it clear. Use when asked clean up my desktop, my desktop has 200 files on it, why does my desktop keep filling up, or set up a clean-desktop habit. Produces the today-pass, the function-replacement mapping, and the two-minute weekly habit.OtherNo warnings★ 1.5K↓ —
- research-audience-fit-definitiongooseworks-ai/goose-skillsStep of the research-audience playbook: drafts the searchable fit definition, exclusions and list size that the list run then searches on. Run research-audience instead; not for direct use.ScienceNo warnings★ 1.3K↓ —
- analyze-performance-revenue-joingooseworks-ai/goose-skillsStep of the analyze-performance playbook: joins cleaned store or CRM numbers with ad spend to build the business-truth table, MER, new-customer cost and the overclaim ratio. Run analyze-performance instead; not for direct use.MarketingNo warnings★ 1.3K↓ —
- 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↓ —
- add-geolocationmicrosoft/power-platform-skillsInternal implementation skill invoked by /add-native for native background GPS tracking with durable storage and Dataverse sync using @microsoft/power-apps-native-bglocation.OtherNo warnings★ 1.1K↓ —
- relational-database-mcp-cloudbaseTencentCloudBase/CloudBase-AI-Toolkit[Deprecated] Existing CloudBase MySQL only. Do not recommend MySQL for new relational work — use postgresql-development. Read this when the environment already has a MySQL instance and the task is queryMysqlDatabase, manageMysqlDatabase, queryPermissions, or managePermissions (inspect, write SQL, schema, permissions, destroy). Do not provision MySQL.DataNo warnings★ 1.2K↓ —Also in 5 other repos
- gpt-image-2-6hashgraph-online/awesome-codex-pluginsGuide to OpenAI's GPT Image 2.6 on varg (gpt_image_2_6) and the entry point to the GPT Image 2.6 skill set: Flare vs Sunburst, quality vs reasoning_effort, sizes and aspect presets, what fal rejects (xhigh and max effort, SVG, over 16 GIF frames), measured prices, failure modes, the exact varg MCP and REST calls, and prompt recipes for the text-heavy layouts people shared on X: infographic, product launch poster, photo to editorial travel print, photo to Baroque gallery poster, landmark postcard, character turnaround sheet, storyboard sheet and low-res to clean upscale, each credited to its author. Use when someone asks for GPT Image 2.6, gpt-image-2.6, Flare or Sunburst, wants an infographic, poster, art print, character sheet or storyboard with readable text, or asks how to prompt, size or price this model. Not for looping GIFs (gpt-image-gif), sticker packs (gpt-image-sticker-pack), game sprite sheets (gpt-image-sprite-sheet), circle-and-arrow edits (gpt-image-markup-edit) or video (varg-ai).MediaNo warnings★ 1.5K↓ —
- capa-officeralirezarezvani/claude-skillsUse for CAPA work in a medical device QMS: root cause analysis (5-Why, fishbone), corrective action plans, effectiveness checks or CAPA metrics. Tracks CAPAs with capa_tracker.py and analyzes causes with root_cause_analyzer.py.ScienceNo warnings★ 29.3K↓ —
- minutes-weeklysilverstein/minutesWeekly meeting synthesis — themes, decision arcs, stale commitments, and what deserves your attention next week. Use when the user says "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", or at the end of a work week.EngineeringNo warnings★ 1.6K↓ —Also in 1 other repo
paid-ads-strategy
kostja94/marketing-skills
MarketingUpdated yesterday
From the author
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads," "PMF testing," "PMF validation," "test product-market fit with ads," "ad spend," "ad budget," "ROAS," "paid acquisition," "Quality Score," or "ad-to-page alignment." For Google Ads execution, use google-ads. For Meta Ads execution, use meta-ads. For landing page alignment, use landing-page-generator.
Install
npx skills add kostja94/marketing-skills --skill paid-ads-strategy -a claude-code
Installs to .claude/skills/paid-ads-strategy/ · 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
Provenance76
Maintenance100
Licence100
Adoption49
Files (1)
- SKILL.md