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,409 skills from 2,375 repositories · updated 60 minutes ago
48,362 skills
- 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↓ —
- triggershashgraph-online/awesome-codex-pluginsCreate and manage triggers that watch for something (a job that finishes, a service that goes down, a failing CI run, a new release, a price crossing a threshold) and hand a task to Codex when it happens. Use when the user wants to be told, or wants something done, "when X happens", and when handling a message that starts with [self-starter].ProductivityNo warnings★ 1.5K↓ —
- design-routerhashgraph-online/awesome-codex-pluginsUse when the user asks to build, design, mock up, scaffold, audit, translate, or improve any interface, flow, screen, page, component, app, UX, onboarding, checkout, dashboard workflow, product flow, design system, asset plan, motion plan, or non-generic UI and the target platform or flow is ambiguous. Routes to ux-design, web, Windows, Apple, Android, cross-platform, design-token, originality, asset/reference, and platform skills. SKIP when the request explicitly names one platform and no UX flow work is implied.DesignNo warnings★ 1.5K↓ —
- second-brain-lintundefined-ui/second-brain-osAudit a second-brain vault for structural problems and repair them: broken wikilinks, orphan pages, empty stubs, frontmatter that violates the schema, near-duplicate pages, and stale index entries. Use this skill whenever the user asks to lint, clean, audit or check the health of their vault, says pages feel messy or links are broken, after a large bulk import, or when a scheduled maintenance run fires. Do NOT use for ingesting new sources, for answering questions from the vault, or for rewriting page content that is structurally fine but reads badly.OtherNo warnings★ 1.2K↓ —
- 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↓ —
- generate-prdhuytieu/COG-second-brainGenerate product requirements documents with optional publishing to Confluence or other wiki platformsPlanningNo warnings★ 1.3K↓ —Also in 1 other repo
- open-designhashgraph-online/awesome-codex-pluginsUse Open Design as an external local-first design workbench for prototypes, decks, mobile screens, dashboards, DESIGN.md systems, and exportable visual artifacts. Keep TSP responsible for team workflow, handoff, and quality gates.DesignNo warnings★ 1.5K↓ —
- git-workflowsTencentCloudBase/CloudBase-AI-ToolkitReusable git delivery workflows derived from local slash commands (commit, push, PR, release notes, GitHub Actions failure triage with worktree-based fixes, and isolating your own changes from a shared dirty workspace).EngineeringNo warnings★ 1.2K↓ —
- second-brain-quizundefined-ui/second-brain-osGenerate questions from the user's own concept pages so they can find out what they saved but never learned, and compare their answers against what the pages say. Use this skill when the user wants to test themselves, revise, make flashcards from their notes, or asks what they have forgotten. Do NOT use for generic quizzing on a topic the vault does not cover, or for answering a question from the vault.TestingNo warnings★ 1.2K↓ —
- minutes-graphsilverstein/minutesPolicy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache.ScienceNo warnings★ 1.6K↓ —Also in 1 other repo
- 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↓ —
- audience-researchScrapeCreators/social-media-research-skillsUse when the user wants to evaluate a creator, influencer, or brand audience using public profile signals, TikTok audience demographics, follower/following data, comments, geography, language, and content fit. Helps judge sponsorship and market fit.ScienceNo warnings★ 5.4K↓ —
- book-drafthashgraph-online/awesome-codex-pluginsPhase 3: Drafting. Voice lock on a sample chapter, then sequential full-context chapter drafting with draft-critique-revise, bible ledger updates, and periodic continuity checks.ProductivityNo warnings★ 1.5K↓ —
- refactor-cleandzhng/skillsRefactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.EngineeringNo warnings★ 1.4K↓ —
- tiktok-adskostja94/marketing-skillsWhen the user wants to set up, optimize, or manage TikTok Ads. Also use when the user mentions "TikTok Ads," "TikTok for Business," "TikTok Pixel," "Events API," "TikTok Spark Ads," or "TikTok video ads." For organic TikTok, use tiktok-captions.MarketingNo warnings★ 1.1K↓ —
- weekly-rollupmohitagw15856/pm-claude-skillsRoll a week of daily reports and agent activity into one honest weekly summary: trajectory against goals, what shipped with proof, the recurring blocker, and what to change next week. Use when asked for a weekly rollup, summarise my week, what did the agent accomplish this week, or a Friday wrap-up from my daily reports. Produces a 12-line weekly rollup in the shared status vocabulary: shipped versus planned, the pattern in the blockers, and one concrete change for next week.PlanningNo warnings★ 1.5K↓ —
- k2fcakyon/claude-codex-settingsBuild and troubleshoot Cloudflare K2 or K2 Streams durable logs. Use for stream setup, producing from Workers or HTTP, configuring retention and inputs, and consuming through subscriptions.DevOpsNo warnings★ 1.2K↓ —
- reviewhashgraph-online/awesome-codex-pluginsThe pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; on the default branch it reviews the unpushed and uncommitted work. A bug-hunting code review complements this review and does not replace it. Also use for 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Takes an optional path, tag, topic, or ref in free text; no first word is a mode — say 'are docs out of date', 'audit the knowledge base', 'close out the feature', or 'capture this pattern' in plain words. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.EngineeringNo warnings★ 1.5K↓ —Also in 1 other repo
- page-croUpdatedalirezarezvani/claude-skillsFix a page that is not converting: section by section audit with fixes ranked by impact. Use whenever a homepage, landing, pricing or feature page gets few signups, sales or clicks.MarketingNo warnings★ 29.2K↓ —
- hep-uploadagentlas-ai/Agentlas-OSPublish an Agentlas package to Agent Cloud or the public Hub.OtherNo warnings★ 1.6K↓ —
- reading-livekit-docsfcakyon/claude-codex-settingsLooks up current LiveKit facts (API signatures, CLI flags, config options, model and provider support, SDK changelogs, pricing) from the docs instead of answering from memory. Use whenever a question touches LiveKit specifics: "does LiveKit support X", "what changed in agents 1.8", "what are the arguments to Y", "how much does LiveKit cost", "find an example of Z in the LiveKit repos", or before writing any LiveKit code. Other LiveKit skills load this one first. Covers the LiveKit Docs MCP server and the `lk docs` CLI.WritingNo warnings★ 1.2K↓ —Also in 1 other repo
- setupfcakyon/claude-codex-settingsThis skill should be used when user encounters "ADC not found", "gcloud auth error", "GCloud MCP error", "Application Default Credentials", "project not set", or needs help configuring GCloud integration.OtherNo warnings★ 1.2K↓ —
- mcp-mocked-markeralibaba/skill-upMCP mocked marker smoke skill used by skill-up e2e tests.TestingNo warnings★ 1.4K↓ —
- 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↓ —
user-feedback-aggregation
rampstackco/claude-skills
PlanningUpdated Oct 27, 2026
From the author
Collecting and synthesizing user feedback across channels (support tickets, NPS, in-app feedback, sales calls, social mentions, customer councils) into a continuous signal that informs product decisions. The triage discipline that distinguishes loudest-voice (whoever complains most wins) from averaged-noise (every signal weighted equally) from triaged-synthesis (signal weighted by source quality, frequency, and decision relevance). Triggers on user feedback, customer feedback aggregation, NPS, support ticket analysis, customer councils, feedback synthesis, voice of customer, feedback triage, in-app feedback. Also triggers when feedback channels overflow with volume that does not produce decisions, when the loudest-voice problem is steering roadmap, or when continuous feedback streams need synthesis discipline.
Install
npx skills add rampstackco/claude-skills --skill user-feedback-aggregation -a claude-code
Installs to .claude/skills/user-feedback-aggregation/ · 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/categorization-and-tagging-at-scale.md
- references/channel-source-weighting.md
- references/channel-types-and-what-each-surfaces.md
- references/closing-the-loop-with-users.md
- references/common-feedback-aggregation-failures.md
- references/detecting-drift-in-feedback.md
- references/frequency-vs-intensity.md
- references/from-feedback-to-product-decision.md
- references/tooling-considerations.md