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,103 skills from 2,358 repositories · updated 17 minutes ago
48,054 skills
- taisly-social-media-postinghashgraph-online/awesome-codex-pluginsConnect AI agents to Taisly through MCP to publish and schedule videos, inspect history, and manage reposts.MarketingNo warnings★ 1.5K↓ —Also in 1 other repo
- research-market-edge-casesgooseworks-ai/goose-skillsStep of the research-market playbook: rules for run edge cases such as no browser, stalled workers, earlier reports and late reads. Run research-market instead; not for direct use.ScienceNo warnings★ 1.3K↓ —
- oma-debugfirst-fluke/oh-my-agentBug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.EngineeringNo warnings★ 1.4K↓ —
- cell-submissionbrycewang-stanford/Awesome-Journal-SkillsUse as the final preflight before submitting to Cell — a complete checklist across significance, narrative, Highlights/eTOC/Graphical Abstract, Summary, figures, STAR Methods, data, references, and required files. Bundles the checklist and cover-letter templates.ProductivityNo warnings★ 1.4K↓ —
- vis-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing IEEE VIS evaluations, covering how to match evidence to the contribution type (perceptual study, controlled user study, algorithm benchmark, design-study validation, qualitative work), controlled experiment design with power and effect sizes, CVD-safe and perceptually grounded encoding choices, task taxonomies, and provenance so a TVCG reviewer trusts the result.DesignNo warnings★ 1.4K↓ —
- icdt-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ICDT (International Conference on Database Theory) regular-paper submission for Microsoft CMT readiness, covering the two-step abstract-then-paper deadline in the correct submission cycle, the lipics-v2021 15-page limit excluding references, the clearly-marked appendix read at the PC's discretion, anonymous submission since 2024, the complete-proofs / full-version expectation, and which submission problems are unfixable after the AoE cutoff.DataNo warnings★ 1.4K↓ —
- correctNewhashgraph-online/awesome-codex-pluginsFind mistake classes agents keep repeating in this repository and block each with the strongest mechanism available (structure, then types and lint, then tests, docs last). Use for "/correct", "agents keep making the same mistake here", or after a repeated correction.TestingNo warnings★ 1.5K↓ —
- ultralytics-platformfcakyon/claude-codex-settingsThis skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model endpoint", "run Moondream on Platform", "auto-annotate a Platform dataset", "run hosted AI inference", "why is my run not showing on platform", or mentions platform.ultralytics.com, ul:// URIs, ultralytics-platform, or ULTRALYTICS_API_KEY.DevOpsNo warnings★ 1.2K↓ —
- second-brain-metricsundefined-ui/second-brain-osRecord a dated snapshot of the vault's health numbers and compare against previous snapshots so trends are visible. Use this skill for a monthly or quarterly check, when the user asks whether the vault is improving, or asks to track its numbers over time. Do NOT use for a one-off graph analysis, which is second-brain-graph, or for structural repairs.OtherNo warnings★ 1.2K↓ —
- audit-decisionsNewdzhng/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↓ —
- 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↓ —
- pulsealirezarezvani/claude-skillsUse for what people are saying right now about a topic (trends, sentiment, complaints, tool comparisons) across Reddit, Hacker News and the web in a recent window. Returns a cited briefing with engagement signals.OtherNo warnings★ 29.2K↓ —
- gate-checkundefined-ui/second-brain-osFind the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).ProductivityNo warnings★ 1.2K↓ —
- nsdi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems reviewers can see where the design wins, loses, and breaks.DevOpsNo warnings★ 1.4K↓ —
- fse-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.WritingNo warnings★ 1.4K↓ —
- itcs-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding what counts as evidence for an ITCS theory claim — proofs as the primary evidence, worked examples and separations that make a model concrete, and the rare, well-scoped illustrative computation or simulation — and how to keep any computational content checkable and subordinate to the mathematics.MediaNo warnings★ 1.4K↓ —
- auto-researchdzhng/skillsRun fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts, configurations, or other artifacts against a goal or benchmark, or when a long research run needs a planned hypothesis queue, focused trials, and durable findings.ScienceNo warnings★ 1.4K↓ —
- kdd-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when splitting a KDD paper across its 8 content pages, the optional appendix after the references, and the cited repository, under the camera-ready rule capping references plus appendix at 3 of 12 pages. Covers appendix triage, reviewer-discretion reality, and the one-page cross-cycle resubmission change summary.ScienceNo warnings★ 1.4K↓ —
- uai-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what reviewers must see in the body versus what may sit in material they are not required to read, all under double-blind and single-file constraints.DocumentsNo warnings★ 1.4K↓ —
- write-outreach-draft-sequencegooseworks-ai/goose-skillsStep of the write-outreach playbook: the brief a helper follows to write one segment's email and LinkedIn sequence, first lines and replies from rows and an angle prepared earlier. Run write-outreach instead; not for direct use.WritingNo warnings★ 1.3K↓ —
- cinematic-shotdzhng/skillsShoot software UI like a film. A sequence of hero shots, each a steep, oblique, extreme close-up of the interface floating in black, with a razor-thin focal plane, a slow motivated camera drift, and UI that acts on its own, hard-cut on the action, ending on one line of copy and a still logo. Use when asked for a launch video, product film, feature trailer, teaser, promo clip, hero shot, or any "cinematic" footage of an app or UI. This skill covers camera, framing, light, and edit. It is stack-agnostic.DesignNo warnings★ 1.4K↓ —
- gentle-ai-chained-prGentleman-Programming/gentle-shellTrigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.EngineeringNo warnings★ 1.5K↓ —
- executive-reporthoangsonww/Claude-Code-Agent-MonitorGenerate a concise stakeholder report from CCAM sessions, analytics, cost, alerts, and workflow intelligence. Use for release summaries, leadership updates, operational reviews, or a scoped Markdown report with evidence.DataNo warnings★ 1.1K↓ —
- plan-campaign-brief-and-assetsgooseworks-ai/goose-skillsStep of the plan-campaign playbook: writes angles per channel, the asset list, measurement plan, hand-offs and replan triggers, then assembles the plan. Run plan-campaign instead; not for direct use.MarketingNo warnings★ 1.3K↓ —
explore-unknowns
dzhng/skills
WritingUpdated yesterday
From the author
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.
Install
npx skills add dzhng/skills --skill explore-unknowns -a claude-code
Installs to .claude/skills/explore-unknowns/ · 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
Provenance78
Maintenance100
Licence100
Adoption51
Files (7)
- SKILL.md
- references/after-the-walk.md
- references/stage-1-known-knowns.md
- references/stage-2-known-unknowns.md
- references/stage-3-unknown-knowns.md
- references/stage-4-unknown-unknowns.md
- references/stage-5-hand-over-the-map.md