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,088 skills from 2,358 repositories · updated 11 minutes ago
49,086 skills
- navan-data-syncjeremylongshore/tons-of-skills-marketplaceSynchronize Navan booking, expense, identity, and file-delivered data according to each documented source contract. Use when building durable ETL or correcting sync drift. Trigger with "Navan data sync", "Navan ETL", or "reconcile Navan feeds".DataNo warnings★ 2.9K↓ —
- cursor-team-setupjeremylongshore/tons-of-skills-marketplaceSet up Cursor for teams: plan selection, member management, shared rules, admin dashboard, and onboarding. Triggers on "cursor team", "cursor organization", "cursor business", "cursor enterprise setup", "cursor admin".PlanningNo warnings★ 2.9K↓ —
- golang-concurrencysamber/cc-skills-golangGolang concurrency design — goroutine lifecycle and leak prevention, channels and `select`, channel ownership and direction, `sync.Mutex`/`RWMutex`/`sync.Map`/`sync.Once`/atomics, `errgroup`, `singleflight`, worker pools, and fan-out/fan-in pipelines. Use when writing or reviewing concurrent Go code, when choosing between channels and mutexes, when protecting a shared map or counter, or when a goroutine has no clear exit. Not for defensive coding unrelated to concurrency such as nil panics, slice aliasing, or numeric overflow (→ See `samber/cc-skills-golang@golang-safety` skill), and not for debugging a specific hung, crashing, or racing program after the fact (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).DesignNo warnings★ 3.8K↓ —
- doca-debugNVIDIA/skillsUse this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca_* symbol, a runtime call returning DOCA_ERROR_*, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime → program → driver), verbosity controls (--sdk-log-level, DOCA_LOG_LEVEL, the doca-{lib}-trace flavor), container-debug constraints, or how to capture state for a Developer Forum post. Trigger even when the user does not say "DOCA debug" — implicit phrasings include "undefined reference to doca_*", "how do I get more logs", "packets aren't reaching the wire", "doca_caps returned nothing", or "hugepages empty in the container". Refuse and route elsewhere for library-specific debug (Flow pipe trace, RDMA QP, Comch stats), env-class pkg-config or hugepages symptoms, the DOCA_ERROR_* taxonomy and lifecycle interpretation, and performance or incident-response work — those belong to other skills.EngineeringNo warnings★ 3.8K↓ —
- gsd:threaddavepoon/buildwithclaudeManage persistent context threads for cross-session workProductivityNo warnings★ 3.7K↓ —
- doca-dmaNVIDIA/skillsUse this skill when the user is doing hands-on DOCA DMA programming — bringing up a doca_dma context, configuring the single doca_dma_task_memcpy task type, sizing buffers via the doca_dma_cap_task_memcpy_* queries, setting LOCAL_READ_ONLY / LOCAL_READ_WRITE permissions on source / destination doca_mmap regions (plus doca_mmap_export_* for cross-peer copies), driving the progress engine, or debugging DOCA_ERROR_* returns. Trigger even when the user does not explicitly mention "DOCA DMA" or "doca_mmap" — typical implicit phrasings include "memcpy host buffer to BlueField without using the CPU", "offload a bulk copy to the DPU", "copy returns NOT_PERMITTED on first submit", "buffer too big for one DMA task", "task submitted but no completion", or "scatter-gather copy between two memory regions". Refuse and route elsewhere for cross-network copies (DOCA RDMA), producer/consumer messaging (DOCA Comch), DOCA Core / progress-engine internals, or DOCA install — those belong to other skills.EngineeringNo warnings★ 3.8K↓ —
- apollo-cost-tuningjeremylongshore/tons-of-skills-marketplaceOptimize Apollo.io costs and credit usage. Use when managing Apollo credits, reducing API costs, or optimizing subscription usage. Trigger with phrases like "apollo cost", "apollo credits", "apollo billing", "reduce apollo costs", "apollo usage".EngineeringNo warnings★ 2.9K↓ —
- navan-rate-limitsjeremylongshore/tons-of-skills-marketplaceConfigure Navan integration concurrency and retry controls from the tenant contract and observed responses. Use when controlling throughput or throttling. Trigger with "Navan rate limit", "throttle Navan sync", or "Navan backpressure".LegalNo warnings★ 2.9K↓ —
- maintain-formal-verification-skillmichael-denyer/pstack-claudeBring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.EngineeringNo warnings★ 3.8K↓ —
- finta-cost-tuningjeremylongshore/tons-of-skills-marketplaceOptimize Finta plan selection and feature usage. Trigger with phrases like "finta cost", "finta pricing", "finta plan selection".PlanningNo warnings★ 2.9K↓ —
- golang-safetysamber/cc-skills-golangDefensive Golang coding against accidental bugs — nil panics, typed-nil interfaces, `append` backing-array aliasing, silent int64-to-int32 truncation, float `==` comparison, `defer` inside loops, defensive copies of slices and maps, and usable zero values. Use when a Go program panics on a nil map write or nil pointer dereference, when reviewing code for nil-safety, numeric conversion overflow, or resource lifecycle, or when designing a type whose zero value must be safe. Not for designing concurrent access with goroutines, channels, or sync primitives (→ See `samber/cc-skills-golang@golang-concurrency` skill), not for exploitable vulnerabilities such as injection, weak crypto, or leaked secrets (→ See `samber/cc-skills-golang@golang-security` skill), and not for debugging an already-failing program (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).SecurityNo warnings★ 3.8K↓ —
- lspcode-yeongyu/oh-my-openagentUse when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.OtherNo warnings★ 70.6K↓ —
- coda-automationdavepoon/buildwithclaudeAutomate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.ProductivityNo warnings★ 3.7K↓ —
- lindy-rate-limitsjeremylongshore/tons-of-skills-marketplaceManage Lindy AI credits, rate limits, and usage optimization. Use when hitting rate limits, optimizing credit consumption, or implementing usage controls. Trigger with phrases like "lindy rate limit", "lindy credits", "lindy quota", "lindy throttling", "lindy API limits".EngineeringNo warnings★ 2.9K↓ —
- lindy-cost-tuningjeremylongshore/tons-of-skills-marketplaceOptimize Lindy AI costs through credit management, model selection, and agent consolidation. Use when reducing spend, analyzing credit usage patterns, or optimizing budget allocation across agents. Trigger with phrases like "lindy cost", "lindy billing", "reduce lindy spend", "lindy budget", "lindy credits".OtherNo warnings★ 2.9K↓ —
- statsmodelsforyourhealth111-pixel/Vibe-SkillsStatistical modeling toolkit. OLS, GLM, logistic, ARIMA, time series, hypothesis tests, diagnostics, AIC/BIC, for rigorous statistical inference and econometric analysis.TestingNo warnings★ 3.8K↓ —
- hex-common-errorsjeremylongshore/tons-of-skills-marketplaceDiagnose and fix Hex common errors and exceptions. Use when encountering Hex errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "hex error", "fix hex", "hex not working", "debug hex".EngineeringNo warnings★ 2.9K↓ —
- figma-rate-limitsjeremylongshore/tons-of-skills-marketplaceHandle Figma REST API rate limits with exponential backoff and request queuing. Use when encountering 429 errors, implementing retry logic, or optimizing API request throughput for Figma. Trigger with phrases like "figma rate limit", "figma throttling", "figma 429", "figma retry", "figma backoff".DesignNo warnings★ 2.9K↓ —
- devil-advocatejeremylongshore/tons-of-skills-marketplaceConstructive critic and stress-tester for ideas and proposals. Use when the user needs to challenge assumptions, find weaknesses, anticipate objections, or strengthen an argument. Trigger with "challenge", "critique", "push back", "poke holes", "stress test", "what am I missing", or "play devil's advocate".TestingNo warnings★ 2.9K↓ —
- hypothesis-testerjeremylongshore/tons-of-skills-marketplaceStructured hypothesis formulation, experiment design, and results interpretation for Product Managers. Use when the user needs to validate an assumption, design an A/B test, or evaluate results. Trigger with "hypothesis", "A/B test", "experiment", "validate assumption", "test this", or "should we ship".TestingNo warnings★ 2.9K↓ —
- groq-hello-worldjeremylongshore/tons-of-skills-marketplaceCreate a minimal working Groq chat completion example. Use when starting a new Groq integration, testing your setup after installing the SDK, or learning the basic Groq API request/response pattern before building something larger. Trigger with phrases like "groq hello world", "groq example", "groq quick start", "simple groq code".TestingNo warnings★ 2.9K↓ —
- groq-sdk-patternsjeremylongshore/tons-of-skills-marketplaceApply production-ready Groq SDK patterns for TypeScript and Python. Use when implementing Groq integrations, refactoring SDK usage, or establishing team coding standards for Groq. Trigger with phrases like "groq SDK patterns", "groq best practices", "groq code patterns", "idiomatic groq".EngineeringNo warnings★ 2.9K↓ —
- doca-compressNVIDIA/skillsHardware compression offload with DOCA Compress on a BlueField DPU, ConnectX NIC, or host: DEFLATE compress and decompress, plus LZ4 decompress (stream and block; LZ4 encode is NOT supported), instead of CPU zlib / zstd. Trigger on "offload this gzip", "decompress incoming network data on the NIC", "compress task returns INVALID_VALUE on alloc_init", "submitted a task but no completion arrives", or "decompress LZ4 on the BlueField", even without naming DOCA Compress. Covers enabling compress-deflate, decompress-deflate, decompress-lz4-stream and decompress-lz4-block tasks on a doca_compress context, sizing source / destination doca_buf against the per-task cap query, mmap permissions, offload vs CPU decisions, a round-trip smoke, and DOCA_ERROR_* from Compress calls. Refuse and route elsewhere for zstd / Snappy / brotli, LZ4 encode (a CPU LZ4 library), pure mmap-to-mmap copies (doca-dma), or DOCA Core lifecycle internals.ProductivityNo warnings★ 3.8K↓ —
- drill-statusdavepoon/buildwithclaudeShow drill-me learning progress — topics studied, cards due for review, weakest concepts, and what to study next. Use when the user asks what's due, how their learning is going, or for their drill-me status.EngineeringNo warnings★ 3.7K↓ —
kiro-spec-quick
gotalab/cc-sdd
PlanningUpdated Oct 22, 2026
From the author
Quick spec generation with interactive or automatic mode
Install
npx skills add gotalab/cc-sdd --skill kiro-spec-quick -a claude-code
Installs to .claude/skills/kiro-spec-quick/ · 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