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 13 hours ago
48,362 skills
- saying-nomohitagw15856/pm-claude-skillsDecline a request, push back on scope, or protect priorities without burning the relationship. Use when asked how to say no, turn down a request, push back on your boss/stakeholder, decline extra work, or protect the roadmap from a pet feature. Produces a graceful, firm response — the no, the honest why, an alternative or trade-off, and the exact wording, tuned to who's asking.PlanningNo warnings★ 1.5K↓ —
- iros-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an IROS paper for the PaperPlaza upload — author PINs and metadata, the content-page limit with references counted in, IEEE two-column format, the 2026 double-anonymous rule, the 60-second/10 MB video attachment and its own deadline, dual-submission traps shared with ICRA and RA-L, and return-without-review triggers.MediaNo warnings★ 1.4K↓ —
- itcs-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column >= 11pt format with no hard page limit, the first-10-pages merits window, complete proofs of all central claims, the lightweight double-blind sweep, and the archival-prior-publication check.ScienceNo warnings★ 1.4K↓ —
- doca-pcc-countersNVIDIA/skillsUse this skill when the user is invoking the DOCA PCC Counters tool — the `pcc_counters.sh` bash script under the DOCA tools directory — to arm and read the fixed firmware/hardware PCC (Programmable Congestion Control) diagnostic counters (CNP, RTT, WRED-drop, etc.) on a ConnectX / BlueField device via mst + the mlx5 debugfs `diag_cnt` interface. The script takes two positional args — `set | query` and an mst device path — with no `--help` or subcommands. Trigger even without "pcc_counters.sh" or "PCC counters": "how do I read the CNP / RTT / WRED-drop counters", "PCC counter stuck at zero", "the script says Bad Device", or "is congestion control dropping packets on this port?". Route elsewhere for writing a custom PCC algorithm (doca-pcc), factory firmware PCC config, DOCA install, or fleet-wide CC tuning.DesignNo warnings★ 3.8K↓ —
- run-qafcakyon/claude-codex-settingsThis skill should be used when user asks to "run QA", "verify real playback", "test provider connections", or "check website, extension or Android flows" with tracked journeys.TestingNo warnings★ 1.2K↓ —
- cloudbase-document-database-in-wechat-miniprogramTencentCloudBase/CloudBase-AI-ToolkitUse CloudBase document database WeChat MiniProgram SDK to query, create, update, and delete data. Supports complex queries, pagination, aggregation, and geolocation queries.DataNo warnings★ 1.2K↓ —Also in 5 other repos
- docs-page-generatorkostja94/marketing-skillsDeprecated compatibility entry for Documentation Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Documentation Page.OtherNo warnings★ 1.1K↓ —
- jama-statisticsbrycewang-stanford/Awesome-Journal-SkillsUse when preparing or auditing the statistical analysis and reporting of a JAMA manuscript so it survives JAMA's dedicated statistical review. Enforces effect sizes with 95% CIs, multiplicity control, and pre-specification; it does NOT choose the study design or write prose.DesignNo warnings★ 1.4K↓ —
- 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
- dogfoodfcakyon/claude-codex-settingsSystematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.TestingNo warnings★ 1.2K↓ —
- issta-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ISSTA project timeline from venue fit through the January research-paper deadline, the March author response, the April first decision, the May Major-Revision sprint, the June final decision, artifact evaluation, and the October symposium, with backward-planning offsets for a testing/analysis tool paper and its artifact.ProductivityNo warnings★ 1.4K↓ —
- isca-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the template check, the double-blind sweep including PDF metadata and anonymized artifact links, and HotCRP form completion before AoE.DocumentsNo warnings★ 1.4K↓ —
- mlsys-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response, notification, camera-ready, the March artifact-evaluation submission, and the May conference, with backward planning built around scarce GPU time and team ownership.ProductivityNo warnings★ 1.4K↓ —
- basinfcakyon/claude-codex-settingsBuild and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL. Use for streaming data into R2 Iceberg tables, managing catalogs, or querying those tables; also use for requests using the former Data Platform, Pipelines, R2 Data Catalog, or R2 SQL names.DevOpsNo warnings★ 1.2K↓ —
- agentlas-buildagentlas-ai/Agentlas-OSUse when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.DesignNo warnings★ 1.6K↓ —
- nejm-statisticsbrycewang-stanford/Awesome-Journal-SkillsUse to enforce NEJM's clinical statistical reporting — confidence intervals over bare P values, the pre-specified intention-to-treat primary analysis, multiplicity control for secondary endpoints, pre-specified subgroups with interaction tests, missing-data handling, and absolute risk with NNT alongside relative measures.TestingNo warnings★ 1.4K↓ —
- mind-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when running the final pre-submission preflight for Mind via ScholarOne — preparation for triple-anonymous review, the ~8,000-word limit, the 50–200-word abstract, line numbering, the one-article-per-12-months rule, file format, and the MIND house style. Final checks; it does not draft content.WritingNo warnings★ 1.4K↓ —
- design-fixhashgraph-online/awesome-codex-pluginsCompare one already-implemented screen or component against its Figma source and fix the deviations you pick -- reads the node live through the figma-bridge MCP, or from the Node Specs of an existing /design plan, then diffs box, layout, typography, fill, stroke, radius, effects, and content against the code that renders it. Reports first, fixes only what you select, and never touches Figma.DesignNo warnings★ 1.5K↓ —
- kdd-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a KDD submission against the data-mining lineage (prior KDD volumes, ICDM, SDM, WSDM, CIKM, WWW) and the ML flagships, handling venue misattribution traps, cross-cycle resubmission overlap, concurrent arXiv work, and the mechanism-contrast style of novelty argument that ACM SIGKDD reviewers expect.ScienceNo warnings★ 1.4K↓ —
- minutes-lintsilverstein/minutesHealth-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.OtherNo warnings★ 1.6K↓ —Also in 1 other repo
- minutes-prepsilverstein/minutesInteractive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review history with someone before a meeting.EngineeringNo warnings★ 1.6K↓ —Also in 1 other repo
- stripe-best-practicesfcakyon/claude-codex-settingsGuides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.SecurityNo warnings★ 1.2K↓ —
- nanoresearch-planningOpenRaiser/NanoResearchProduce an experiment blueprint from a research hypothesisPlanningNo warnings★ 1.3K↓ —
- 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↓ —
user-feedback-aggregation
rampstackco/claude-skills
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.
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 (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