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,105 skills from 2,358 repositories · updated 10 hours ago
48,055 skills
- knowledge-consolidationhuytieu/COG-second-brainBuild frameworks from scattered insights across all braindumps and notesProductivityNo warnings★ 1.3K↓ —Also in 1 other repo
- hri-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE HRI full-paper submission for PCS readiness — the mandatory abstract-then-paper two-step deadline, choosing the correct one of the five tracks, the 8-page acmart anonymous format, the double-blind sweep across PDF and video, the human-participants ethics acknowledgment, and desk-reject triage before the AoE cutoff.DocumentsNo warnings★ 1.4K↓ —
- sqsitsmostafa/aws-agent-skillsAWS SQS message queue service for decoupled architectures. Use when creating queues, configuring dead-letter queues, managing visibility timeouts, implementing FIFO ordering, or integrating with Lambda.DevOpsNo 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↓ —
- reflectalirezarezvani/claude-skillsUse when the user says 'step back', 'zoom out', 'are we on track' or 'sanity check this', or work has gone deep into details without a check on direction. Reassesses direction, assumptions and bias across five dimensions.OtherNo warnings★ 29.2K↓ —Also in 1 other repo
- 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↓ —
- review-cockpithuytieu/COG-second-brainSelf-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework. Plus paired anti-slop design skills for marketing and product UI. Works with Claude Code, Cursor, Kiro, Gemini CLI, Codex.EngineeringNo warnings★ 1.3K↓ —
- iclr-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.ProductivityNo warnings★ 1.4K↓ —
- resuminghashgraph-online/awesome-codex-pluginsResume an interrupted workflow run with verify-first strategy — loads sidecar state, verifies the last step, and continues execution.ProductivityNo warnings★ 1.5K↓ —
- vector-coverhuytieu/COG-second-brainFlat vector editorial cover illustrations in HTML and SVG, rendered to a 2400x960 PNG with headless ChromeBrowserNo warnings★ 1.3K↓ —
- dac-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline, the 6+1-page ACM double-column page budget with its references-only last page, the double-blind anonymization sweep, TPC conflict-of-interest declaration, and desk-reject triage before the mid-to-late-November cutoff.DesignNo warnings★ 1.4K↓ —
- blog-publishhuytieu/COG-second-brainSelf-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework. Plus paired anti-slop design skills for marketing and product UI. Works with Claude Code, Cursor, Kiro, Gemini CLI, Codex.WritingNo warnings★ 1.3K↓ —
- feature-dochuytieu/COG-second-brainSelf-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework. Plus paired anti-slop design skills for marketing and product UI. Works with Claude Code, Cursor, Kiro, Gemini CLI, Codex.DesignNo warnings★ 1.3K↓ —
- daily-briefhuytieu/COG-second-brainGenerate personalized news intelligence with verified sources (7-day freshness requirement)PlanningNo warnings★ 1.3K↓ —
- os-ask-simplekharmanskyi/open-stepsALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer more than a guess. Rewrites the question in plain words and always ends with one marked recommendation. A structural choice first passes six checks, shown as a table: effort now, simpler substitute, extra work later, lock-in, over-engineering, easy to undo. Doing nothing is always weighed.EngineeringNo warnings★ 1.3K↓ —
- os-whats-nextkharmanskyi/open-stepsALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.ProductivityNo warnings★ 1.3K↓ —
- export-open-issueshuytieu/COG-second-brainAudit and export open issues from any project tracker with summary analysis and vault archivalProductivityNo warnings★ 1.3K↓ —Also in 1 other repo
- daily-journalhuytieu/COG-second-brainA passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say "log this to my journal", "add to today's journal", "reflect on today/yesterday", or when finishing a meaningful chunk of work in any session.WritingNo warnings★ 1.3K↓ —
- ergonomicshashgraph-online/awesome-codex-pluginsAudit CLI, API, MCP or SDK discovery, first use and error recovery. Use when: designing an agent-facing tool or investigating misuse, including one command.FinanceNo warnings★ 1.5K↓ —Also in 2 other repos
- migrationhashgraph-online/awesome-codex-pluginsBring an existing codebase into Dryforge, once. Reads the code, asks what code cannot show — business rules, security policy, what is intentional — and writes the project docs at the entry points agents already read. Use when the user invokes the `migration` skill on an existing project. Requires git.SecurityNo warnings★ 1.5K↓ —Also in 3 other repos
- eccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when running an ECCV campaign end to end — the even-year calendar from February registration to the September conference, the retargeting triangle to CVPR and ICCV seen from the ECCV seat, where the 2026 cycle stands today, and backward planning a 2028 submission from the March deadline.ProductivityNo warnings★ 1.4K↓ —
- team-briefhuytieu/COG-second-brainGenerate daily team intelligence brief by cross-referencing GitHub, Linear, Slack, PostHog, meetings, and braindumps with two-way Linear sync-backOtherNo warnings★ 1.3K↓ —
- legal-page-generatorkostja94/marketing-skillsDeprecated compatibility entry for Legal Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Legal Page.LegalNo warnings★ 1.1K↓ —
- asc-xcode-buildrorkai/app-store-connect-cli-skillsBuild, archive, export, and manage Xcode version/build numbers with asc, including portable iOS compilation and packaging. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release testing.TestingNo warnings★ 1.1K↓ —
experimentation-platform-orchestrator
rampstackco/claude-skills
From the author
A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.
Install
npx skills add rampstackco/claude-skills --skill experimentation-platform-orchestrator -a claude-code
Installs to .claude/skills/experimentation-platform-orchestrator/ · 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 (9)
- README.md
- SKILL.md
- references/common-mistakes.md
- references/cost-and-pricing-models.md
- references/governance-and-team-setup.md
- references/mcp-capability-comparison.md
- references/migration-playbook.md
- references/multi-platform-orchestration.md
- references/platform-decision-matrix.md