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,622 skills from 2,355 repositories · updated 12 hours ago
48,622 skills
- designing-experimentsforyourhealth111-pixel/Vibe-SkillsDesign experiments and quasi-experiments before analysis. Use when choosing study design, treatment/control structure, outcomes, assumptions, validation plans after scientific experiment failure, or which of DiD, ITS, synthetic control, or regression discontinuity fits the research question. For fitting models or estimating effects on existing data, use performing-causal-analysis instead.DesignNo warnings★ 3.8K↓ —
- navan-debug-bundlejeremylongshore/tons-of-skills-marketplaceAssemble a content-free Navan integration support bundle for operators or vendor escalation. Use when triage needs reproducible evidence. Trigger with "collect Navan diagnostics", "Navan support bundle", or "sanitize Navan logs".EngineeringNo warnings★ 2.9K↓ —
- render-automationdavepoon/buildwithclaudeAutomate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.MediaNo warnings★ 3.7K↓ —
- gsd:workstreamsdavepoon/buildwithclaudeManage parallel workstreams — list, create, switch, status, progress, complete, and resumeOtherNo warnings★ 3.7K↓ —
- gsd:verify-workdavepoon/buildwithclaudeValidate built features through conversational UATOtherNo warnings★ 3.7K↓ —
- gsd:insert-phasedavepoon/buildwithclaudeInsert urgent work as decimal phase (e.g., 72.1) between existing phasesOtherNo warnings★ 3.7K↓ —
- golang-grpcsamber/cc-skills-golangProvides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.TestingNo warnings★ 3.7K↓ —
- principle-type-system-disciplinemichael-denyer/pstack-claudeApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.WritingNo warnings★ 3.7K↓ —
- navan-install-authjeremylongshore/tons-of-skills-marketplaceEstablish a Navan integration access contract without guessing endpoints, grants, or scopes. Use when onboarding a Booking API, Expense API, SFTP, SCIM, SSO, or direct integration. Trigger with "set up Navan access", "authenticate Navan", or "review Navan credentials".LegalNo warnings★ 2.9K↓ —
- principle-subtract-before-you-addmichael-denyer/pstack-claudeApply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.EngineeringNo warnings★ 3.7K↓ —
- principle-foundational-thinkingmichael-denyer/pstack-claudeApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.WritingNo warnings★ 3.7K↓ —
- offensive-wpsSnailSploit/Claude-RedWPS (Wi-Fi Protected Setup) PIN attack methodology — Pixie Dust offline attack against vulnerable chipsets (Ralink, Realtek, Broadcom, MediaTek), online PIN brute-force with reaver/bully, lockout handling, time-of-day evasion, WPS push-button vulnerability windows, and PIN-to-PSK derivation. Use when a target SOHO router exposes WPS — common on consumer ISP gear, often left enabled by default even when WPS attacks have been known for over a decade.SecurityNo warnings★ 10.2K↓ —
- principle-never-block-on-the-humanmichael-denyer/pstack-claudeApply when tempted to ask 'should I do X?' on reversible work.OtherNo warnings★ 3.7K↓ —
- interrogatemichael-denyer/pstack-claudeUse for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Adversaries try to break a change or design, and only findings proven by a run survive.TestingNo warnings★ 3.7K↓ —
- golang-samber-oopssamber/cc-skills-golangStructured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.ProductivityNo warnings★ 3.7K↓ —
- doca-versionNVIDIA/skillsDOCA version handling: detect the installed release and validate the four-way match across pkg-config doca-common, applications/VERSION, doca_caps --version, and bfver/mlnx-release on BlueField; reason about NGC tags; look up whether a capability exists on this release; diagnose build-vs-runtime drift. Use this skill alongside doca-debug when a symptom smells of version skew: "built but nothing on the wire", "undefined reference to a symbol the docs claim exists", "DOCA_ERROR_NOT_SUPPORTED at runtime", "what does latest mean for this tag", or "is my LTS still supported". Once all four sources match, the component's build / run workflow belongs to its own library, service or tool skill. Refuse install / package choice (doca-setup), per-library API questions (matching library skill), DOCA_ERROR_* taxonomy (doca-programming-guide), and the general debug ladder (doca-debug).EngineeringNo warnings★ 3.8K↓ —
- doca-gpunetioNVIDIA/skillsUse this skill when the user is doing hands-on DOCA GPUNetIO programming — wiring a CUDA kernel on an NVIDIA GPU to a doca-eth queue via doca_gpu_eth_rxq / doca_gpu_eth_txq, standing up the per-CUDA-device doca_gpu context, designing the persistent CUDA kernel that drains the GPU-visible queue, running the dual capability check (DOCA cap-query plus cudaGetDeviceProperties), registering cudaMalloc pools via doca_buf_arr_create_*, or debugging DOCA_ERROR_* returns from the GPUNetIO API. Trigger even when the user does not explicitly mention "DOCA GPUNetIO" or "persistent kernel" — typical implicit phrasings include "CUDA kernel reading packets directly from the NIC", "GPU-initiated networking on BlueField", "DOCA_ERROR_DRIVER on doca_gpu_create", "nvidia_peermem not loaded", "kernel-per-packet is too slow", or "which GPU supports GPU-side packet I/O". Refuse and route elsewhere for general CUDA programming, DOCA Ethernet queue bring-up, DOCA DPA, or DOCA install — those belong to other skills.EngineeringNo warnings★ 3.8K↓ —
- principle-encode-lessons-in-structuremichael-denyer/pstack-claudeApply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.WritingNo warnings★ 3.7K↓ —
- kiro-steering-customgotalab/cc-sddCreate custom steering documents for specialized project contextsPlanningNo warnings★ 3.7K↓ —
- gsd:set-profiledavepoon/buildwithclaudeSwitch model profile for GSD agents (quality/balanced/budget/inherit)OtherNo warnings★ 3.7K↓ —
- golang-securitysamber/cc-skills-golangSecurity best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).SecurityNo warnings★ 3.7K↓ —
- speckit-constitutionforyourhealth111-pixel/Vibe-SkillsCreate or update project governing principles and development guidelines. Use at project start to establish code quality, testing standards, and architectural constraints that guide all development.PlanningNo warnings★ 3.8K↓ —
- trailmarktrailofbits/skillsBuilds and queries multi-language source and binary code graphs for security analysis. Includes pre-analysis passes for blast radius, taint propagation, privilege boundaries, entry point enumeration, proxy/unresolved-call tracking, type/reference queries, structural traversal, graph diffs, audit augmentation, declared cross-language/FFI/external links via `.trailmark/links.toml`, and SQL schema graphs. Use when analyzing call paths, mapping attack surface, finding complexity hotspots, enumerating entry points, tracing taint propagation, measuring blast radius, importing SARIF/weAudit/binary findings, linking source graphs across language or RPC boundaries, or building a code graph for audit prioritization. Feature-gate version-specific Trailmark APIs before using them; prefer `trailmark.parse.detect_languages()` or `--language auto` when the target language is unknown or polyglot.SecurityNo warnings★ 7.9K↓ —
- fathom-rate-limitsjeremylongshore/tons-of-skills-marketplaceHandle Fathom API rate limits (60 requests/minute per user). Trigger with phrases like "fathom rate limit", "fathom 429", "fathom throttle".EngineeringNo warnings★ 2.9K↓ —
klaviyo-automation
davepoon/buildwithclaude
MarketingUpdated 19 hours ago
From the author
Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.
Install
npx skills add davepoon/buildwithclaude --skill klaviyo-automation -a claude-code
Installs to .claude/skills/klaviyo-automation/ · 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 90
Security100
Provenance83
Maintenance100
Licence100
Adoption57
Files (1)
- SKILL.md