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.
48,168 skills from 2,325 repositories · updated 21 hours ago
48,168 skills
- rulescode-yeongyu/oh-my-openagentUse when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or environment configuration.OtherNo warnings★ 70.5K↓ —
- veida-imagedavepoon/buildwithclaudeGenerate an image from a text prompt with no API key, no account and no cost, using the free anonymous tier of Veida (veida.ai). Use when the user asks for a picture, an illustration, a blog cover, a mockup or an avatar and no image provider is configured. Two HTTP calls; returns a hosted image URL.MediaNo warnings★ 3.7K↓ —
- create-planforyourhealth111-pixel/Vibe-SkillsCreate a concise plan. Use when a user explicitly asks for a plan related to a coding task.PlanningNo warnings★ 3.8K↓ —
- vscode-release-notes-writerforyourhealth111-pixel/Vibe-SkillsGuidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.WritingNo warnings★ 3.8K↓ —
- whybacknotprop/pstackUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.DevOpsNo warnings★ 3.3K↓ —
- ulw-executecode-yeongyu/oh-my-openagentExecutes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.WritingNo warnings★ 70.5K↓ —
- ops-statusdavepoon/buildwithclaudeLightweight green/red status panel for every configured integration. No gather, no actions.OtherNo warnings★ 3.7K↓ —
- doca-flowNVIDIA/skillsDOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation before hardware programming, Flow/DOCA version match, and Flow API errors. First app: follow the local bundle (doca-setup, doca-programming-guide, doca-flow, doca-public-knowledge-map). Stage 1 pull nvcr.io/nvidia/doca/doca (NGC catalog tag, never invent); Stage 2 needs a real NIC. Then ls samples inside the container; never emit main.c, a Dockerfile, or hand-typed -l flags. Route software-only host pipelines, plain DPDK `rte_flow`, kernel TC, OVS, BFB bring-up, and DPU OS installation elsewhere. DPU OS installation is destructive and always requires explicit confirmation.EngineeringNo warnings★ 3.8K↓ —
- subagent-driven-developmentforyourhealth111-pixel/Vibe-SkillsUse when executing implementation plans with independent tasks in the current sessionPlanningNo warnings★ 3.8K↓ —
- doca-dtsNewNVIDIA/skillsDeploy and configure the NVIDIA DOCA Telemetry Service (DTS) as it is actually run: (A) BlueField (built-in static pod), (B) Host (docker) on x86_64 / aarch64, or (C) DPF (DPUService / helm chart) — plus the shared configuration layer (`dts_config.ini`, providers, exporters, level labels) that all three share. The user's DEPLOYMENT TYPE decides everything; pick it first. Trigger even without "DTS" for "prometheus on the DPU shows nothing on 9100", "telemetry container exits right after start", "add ethtool counters to the telemetry DPUService", "how do I upgrade the built-in telemetry on BlueField", or "level labels per rack/pod". Refuse and route elsewhere for installing DOCA itself, the `doca_telemetry` / `doca_telemetry_exporter` library API, installing the DPF cluster, Grafana / Prometheus server setup or dashboard / PromQL authoring, and BFB / BSP imaging — those belong to other skills or to external products.DevOpsNo warnings★ 3.8K↓ —
- ossfuzztrailofbits/skillsEnrolls a project in OSS-Fuzz, Google's free continuous fuzzing service for open source, and drives it locally. Covers project.yaml, Dockerfile and build.sh setup, the helper scripts, reproducing OSS-Fuzz crash reports, and the acceptance criteria. Use when setting up continuous fuzzing for an open-source project, reproducing an OSS-Fuzz bug report, or testing an OSS-Fuzz build before submitting it.TestingNo warnings★ 7.9K↓ —
- biopythonforyourhealth111-pixel/Vibe-SkillsPrimary retained Python toolkit for molecular biology sequence work. Preferred for sequence manipulation, FASTA/FASTQ/GenBank parsing, Bio.Entrez, BLAST workflows, alignments, structures, and phylogenetics. For biological database evidence lookup, use bio-database-evidence. For single-cell workflows use scanpy. For direct literature REST API, use pubmed-database.DataNo warnings★ 3.8K↓ —
- sharpenbacknotprop/pstackMake a task deeper, not bigger, then rewrite the prompt. Use for /sharpen.ProductivityNo warnings★ 3.3K↓ —
- golang-observabilitysamber/cc-skills-golangGolang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See `samber/cc-skills-golang@golang-benchmark` and `samber/cc-skills-golang@golang-performance` skills).DevOpsNo warnings★ 3.7K↓ —
- doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.OfficialWritingNo warnings★ 185.7K↓ —Also in 6 other repos
- kiro-debuggotalab/cc-sddInvestigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.EngineeringNo warnings★ 3.7K↓ —Also in 7 other repos
- gsd:remove-workspacedavepoon/buildwithclaudeRemove a GSD workspace and clean up worktreesOtherNo warnings★ 3.7K↓ —
- speckit-checklistforyourhealth111-pixel/Vibe-SkillsGenerate custom quality checklists for validating requirements completeness and clarity. Use to create unit tests for English that ensure spec quality before implementation.PlanningNo warnings★ 3.8K↓ —
- pyzoteroforyourhealth111-pixel/Vibe-SkillsInteract with Zotero reference management libraries using the pyzotero Python client. Retrieve, create, update, and delete items, collections, tags, and attachments via the Zotero Web API v3. Use this skill when working with Zotero libraries programmatically, managing bibliographic references, exporting citations, searching library contents, uploading PDF attachments, or building research automation workflows that integrate with Zotero.DocumentsNo warnings★ 3.8K↓ —Also in 1 other repo
- finta-hello-worldjeremylongshore/tons-of-skills-marketplaceSet up your first fundraise pipeline in Finta with investors and deal stages. Use when starting a new fundraise, importing investor lists, or learning Finta's pipeline management features. Trigger with phrases like "finta hello world", "finta first pipeline", "start fundraise in finta", "finta quick start".FinanceNo warnings★ 2.9K↓ —
- inkjeremylongshore/tons-of-skills-marketplaceContent Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar.MarketingNo warnings★ 2.9K↓ —
- tweetclawdavepoon/buildwithclaudeUse TweetClaw as an OpenClaw plugin for X/Twitter automation: search tweets, search tweet replies, post tweets/replies, export followers, look up users, handle media, monitor tweets, deliver webhooks, run giveaway draws, and manage approval-gated visible actions.OtherNo warnings★ 3.7K↓ —
- tracedocsdavepoon/buildwithclaudeTurn any codebase into evidence-grounded Markdown docs plus a machine-readable index.json. Every claim cites its source; never invents deployment steps.DevOpsNo warnings★ 3.7K↓ —
- modern-pythontrailofbits/skillsConfigures Python projects with modern tooling (uv, ruff, ty). Use when creating projects, writing standalone scripts, or migrating from pip/Poetry/mypy/black.EngineeringNo warnings★ 7.9K↓ —
brand-language-codifier
aaron-he-zhu/aaron-marketing-skills
From the author
Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel's voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry's voice-dossier; not for finished copy or blog posts — use content-writer; not for the message hierarchy itself — use message-system-architect; not for claim adjudication — use offer-claims-registry. 品牌语气/词汇表/命名税/禁用词/品牌语言规范
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill brand-language-codifier -a claude-code
Installs to .claude/skills/brand-language-codifier/ · 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 90
Files (1)
- SKILL.md