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 3 hours ago
49,415 skills
- make-static-ads-claims-extractgooseworks-ai/goose-skillsStep of the make-static-ads playbook: pulls every claim-bearing span out of an ad — the copy around the image, the on-image words in the prompt, badges, and what the picture implies — and keeps or cuts each by the brand-brain rule. Runs before spend on the finished prompt (Pass A) and on every render (Pass B). Run make-static-ads instead; not for direct use.MarketingNo warnings★ 1.3K↓ —
- 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↓ —
- brooks-audithyhmrright/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↓ —
- helphashgraph-online/awesome-codex-pluginsShow KERNEL help. The unified skill system, state operations, agents, current plugin status. Triggers: help, how, what, skills, commands.OtherNo warnings★ 1.5K↓ —
- jlcpcbhashgraph-online/awesome-codex-pluginsJLCPCB PCB fabrication and assembly — BOM/CPL generation, basic vs extended parts, assembly constraints, design rules, ordering workflow. Use with KiCad for JLCPCB manufacturing. Use this skill when the user mentions JLCPCB, wants to order PCBs or assembled boards, needs prototype bare PCBs and stencils, wants to know JLCPCB design rules and capabilities, or is asking about PCB manufacturing costs or turnaround times. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.DesignNo warnings★ 1.5K↓ —
- company-watchhashgraph-online/awesome-codex-pluginsWatches a company or topic on podcasts and YouTube: what was said lately (shows, counts, momentum, quotes), then an Arcmira monitor to keep following it.OtherNo warnings★ 1.5K↓ —
- 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↓ —
- make-static-ads-copy-variantsgooseworks-ai/goose-skillsStep of the make-static-ads playbook: after an image is approved, makes more versions of the same picture with different hooks, headlines or fonts by a quoted re-render with the approved render attached as the brand's own image, so copy can be tested without new visuals. Offered, never default. Run make-static-ads instead; not for direct use.MarketingNo warnings★ 1.3K↓ —
- 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↓ —
- website-structurekostja94/marketing-skillsWhen the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.MarketingNo warnings★ 1.1K↓ —
- oma-architectureUpdatedfirst-fluke/oh-my-agentEvaluate system boundaries and architectural tradeoffs. Use for architecture decisions, design reviews, and ADRs.PlanningNo warnings★ 1.4K↓ —Also in 4 other repos
- product-hunt-launchkostja94/marketing-skillsWhen the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.PlanningNo warnings★ 1.1K↓ —
- 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↓ —
- goose-graphics-create-formatgooseworks-ai/goose-skillsCreates a new graphics format spec (custom canvas dimensions + content rules) and publishes it to the Gooseworks library so any agent can render against it. Use when the existing community formats (carousel, story, infographic, slides, poster, chart, tweet, plus community additions) don't fit the user's canvas — e.g., LinkedIn banner 1584×396, story cover 1080×1920, event flyer 8.5×11in. Mirrors goose-graphics-create-style but for formats.DocumentsNo warnings★ 1.3K↓ —
- research-audience-people-and-contactsgooseworks-ai/goose-skillsFor a list of companies, picks 1-3 current people per company in different buying roles, confirms each title with a dated source, finds a public contact route, labels email status honestly and flags regions with contact rules. Never contacts anyone. Use alone when you already have a vetted company list and the buyer titles; otherwise run research-audience.ScienceNo warnings★ 1.3K↓ —
- social-share-generatorkostja94/marketing-skillsDeprecated compatibility entry for Social Share construction. This component is now maintained in Bricks; install and use component-builder to build a new Social Share.OtherNo warnings★ 1.1K↓ —
- seo-auditkostja94/marketing-skillsWhen the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.MarketingNo warnings★ 1.1K↓ —
- indie-hacker-strategykostja94/marketing-skillsWhen the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.MarketingNo warnings★ 1.1K↓ —
- brooks-healthUpdatedhyhmrright/brooks-lintCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).TestingNo warnings★ 1.6K↓ —
- 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↓ —
- 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↓ —
- audit-decisionsdzhng/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↓ —
- render-narrated-ugc-wardrobe-stitchgooseworks-ai/goose-skillsAssemble a narrated-UGC "stitch reply" ad from a config: one voiceover carries a verbatim testimonial while about 30 short clips (one creator across about 5 outfits and 3 settings, plus product B-roll) are trimmed to windows cut from the voiceover's word timings and joined. The voiceover sits over a ducked music bed, word-by-word captions run throughout, a landing-page scroll is animated from a screenshot, and the brand's real end card closes it (never AI-rendered text). Free, deterministic assembly using the shared stitch-videos-ffmpeg helper; the voiceover, creator stills and clips come from create-vo-elevenlabs, create-image-gpt-image-fal, create-image-fal and create-video-fal. Use for the narrated-ugc-wardrobe-stitch format.MediaNo warnings★ 1.3K↓ —
discovery-research-synthesis
rampstackco/claude-skills
ScienceUpdated Oct 27, 2026
From the author
Turning research artifacts into actionable PM insight. Customer interviews, user research notes, support ticket reviews, sales call transcripts, survey data, in-app feedback, all synthesized into the decisions they are meant to inform. The discipline of moving from raw discovery data to clear product direction without losing signal in the synthesis or fabricating insight that was not actually there. Triggers on research synthesis, customer interview synthesis, user research analysis, discovery readout, research insights, sales call analysis, support ticket analysis, qualitative data analysis. Also triggers when a team has done research but cannot turn it into decisions, when synthesis is producing pretty decks but no roadmap movement, or when an upcoming PM decision needs to be grounded in research already conducted.
Install
npx skills add rampstackco/claude-skills --skill discovery-research-synthesis -a claude-code
Installs to .claude/skills/discovery-research-synthesis/ · 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 (11)
- README.md
- SKILL.md
- references/common-discovery-synthesis-failures.md
- references/from-pattern-to-product-implication.md
- references/pattern-naming-patterns.md
- references/research-types-and-when-each-fits.md
- references/synthesis-review-and-validation.md
- references/synthesis-sequence-walkthrough.md
- references/tagging-and-clustering-discipline.md
- references/when-to-gather-more-data.md
- references/writing-for-decisions-not-decks.md