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 18 hours ago
48,622 skills
- apify-sdk-patternsjeremylongshore/tons-of-skills-marketplaceProduction-ready patterns for Apify SDK and apify-client in TypeScript. Use when building Actors with Crawlee, managing datasets/KV stores, or implementing robust client wrappers with retry and validation. Trigger with "apify SDK patterns", "apify best practices", "apify client wrapper", "crawlee patterns", "idiomatic apify".BrowserNo warnings★ 2.9K↓ —
- skill-xhs-publisherZJU-REAL/Easel将图文/视频内容发布到小红书（XHS）。基于 Playwright + 持久化登录态，headless 即可运行， 流程与选择器移植自成熟开源实现 xiaohongshu-mcp（含发布成功校验、上传完成等待、话题联想绑定、 新旧发布按钮兼容、反检测）。适用场景：发布图文笔记、发布视频、扫码登录、发布前预检。TestingNo warnings★ 4.3K↓ —
- skill-trend-riderZJU-REAL/Easel给定一个热点事件或话题，结合创作者账号定位，输出蹭热点的具体内容方案。 包含切入角度、内容形式、标题建议、风险提醒。 当用户说"这个热点怎么蹭"、"蹭热点"、"怎么结合"、"热点和我有关吗"、 "追热点"、"热点方案"、"借势"、"怎么追这个热点"、"热点怎么切"时触发。 和 skill-trending-topics 的区别：trending-topics 发现和筛选热点， trend-rider 拿到一个具体热点后规划怎么蹭、怎么切内容。OtherNo warnings★ 4.3K↓ —
- gsd:notedavepoon/buildwithclaudeZero-friction idea capture. Append, list, or promote notes to todos.ProductivityNo warnings★ 3.7K↓ —
- skill-community-opsZJU-REAL/Easel评论区运营与舆情危机应对：为一批评论生成分层回复模板（赞美/提问/求购/杠精/黑粉） 与分级处理规则，从评论中挖掘选题反哺内容，负面事件时做危机分级 + 声明草稿 + 统一口径。 当用户说"回复评论"、"评论区运营"、"评论怎么回"、"钓评论"、"引导互动"、 "评论区选题"、"舆情"、"危机公关"、"差评"、"黑粉"、"被骂了"、"道歉声明"、 "统一口径"、"负面缠上来了"、"翻车了怎么办"时触发。 和 skill-quality-gate 的区别：quality-gate 是发布前合规质检， community-ops 是发布后的评论互动与危机响应。OtherNo warnings★ 4.3K↓ —
- 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↓ —
- golang-uber-digsamber/cc-skills-golangImplements dependency injection in Golang using uber-go/dig — reflection-based container, Provide/Invoke, dig.In/dig.Out parameter and result objects, named values, value groups, optional dependencies, scopes, and Decorate. Apply when using or adopting uber-go/dig, when the codebase imports `go.uber.org/dig`, or when wiring an application graph at startup. For higher-level lifecycle and modules, see `samber/cc-skills-golang@golang-uber-fx` skill.OtherNo warnings★ 3.7K↓ —
- 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↓ —
- 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↓ —
- principle-test-behavior-not-implementationbacknotprop/pstackApply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.TestingNo warnings★ 3.3K↓ —Also in 1 other repo
- kiro-spec-designgotalab/cc-sddCreate comprehensive technical design for a specificationDesignNo warnings★ 3.7K↓ —
- tao-train-dinoNVIDIA/skillsDINO (DETR with Improved DeNoising Anchor Boxes) for 2D object detection. Transformer-based detector with denoising training, multi-scale features, and optional distillation support. Use when training, evaluating, exporting, distilling, quantizing, or running inference for a TAO DINO detector. Trigger phrases include "train DINO", "DETR object detection", "TAO 2D detection", "DINO with distillation".OtherNo warnings★ 3.8K↓ —
- doca-benchNVIDIA/skillsRun `doca_bench` (DOCA 2.7.0 or newer) to measure throughput, bulk latency, precision latency, or maximum bandwidth for RDMA, Compress, AES-GCM, SHA, DMA, EC, Ethernet, Comch, or GPUNetIO on a host or BlueField Arm. Use it to discover enabled benchmark libraries, capture a reproducible command/version/device/environment baseline, compare stable runs against a declared tolerance, or diagnose configuration, device-binding, workload-precondition, and measurement failures. Trigger for requests such as measuring BlueField compression speed, NIC RDMA throughput, crypto latency, or a pre-upgrade baseline. Do not use for application end-to-end timing, custom benchmark code, DOCA installation, or binary patches.FinanceNo warnings★ 3.8K↓ —
- postwiredavepoon/buildwithclaudePublish and schedule to TikTok, Instagram, YouTube, LinkedIn, X, Bluesky, Mastodon, Facebook, Threads, Reddit, Telegram and Discord through one PostWire API call — writing a separate, native version of the post for each network instead of sending identical text everywhere. Use when the user wants to publish or schedule one idea across several platforms, wants per-network captions, or wants to know why a post was rejected before it is sent.MarketingNo warnings★ 3.7K↓ —
- golang-swaggersamber/cc-skills-golangGolang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example, swaggerignore). Apply when adding or maintaining Swagger/OpenAPI docs in a Go project, or when the codebase imports github.com/swaggo/swag, github.com/swaggo/gin-swagger, github.com/swaggo/echo-swagger, github.com/swaggo/http-swagger, or github.com/swaggo/files.SecurityNo warnings★ 3.7K↓ —
- lindy-sdk-patternsjeremylongshore/tons-of-skills-marketplaceLindy integration patterns for webhook handling, HTTP actions, and Run Code. Use when building integrations, calling Lindy agents from code, or implementing the Run Code action with Python/JavaScript. Trigger with phrases like "lindy integration patterns", "lindy best practices", "lindy webhook patterns", "lindy Run Code", "lindy HTTP Request".EngineeringNo warnings★ 2.9K↓ —
- meetingdavepoon/buildwithclaudeConvene a meeting of AI personas (3 to 10 participants) who debate a subject and reach a synthesis. Teams adapt to the theme (dev, design, product, business, life). The user can mix teams, add custom personas on the fly, and size the meeting up or down. Full debate written to a markdown file in the current directory, only the Boss's final synthesis is shown in the console.DesignNo warnings★ 3.7K↓ —
- dag-librarycode-yeongyu/oh-my-openagentStores a DAG definition once and re-runs it by name, instead of pasting the definition into every run. Use when the user wants to save a DAG, run a saved one, or schedule the same multi-agent graph repeatedly.OtherNo warnings★ 70.6K↓ —
- exa-local-dev-loopjeremylongshore/tons-of-skills-marketplaceBuild and test an Exa adapter locally using schema fixtures, recorded content-free envelopes, and an explicit opt-in live lane. Use when operating or reviewing this Exa boundary. Trigger with "Exa local dev loop", "review Exa local dev loop", or "fix Exa local dev loop".TestingNo warnings★ 2.9K↓ —
- yt-briefjeremylongshore/tons-of-skills-marketplaceCreate a YouTube production brief with viewer outcome, angle, demo scope and CTA. Use when developing a selected video idea before packaging. Trigger with "write a video brief" or "brief this idea".MediaNo warnings★ 2.9K↓ —
- thermosmichael-denyer/pstack-claudeLaunch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.SecurityNo warnings★ 3.7K↓ —
- slopmopdavepoon/buildwithclaudeTrigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to `sm swab`, `sm scour`, `sm buff`, `sm sail`, `sm refit`, or `sm doctor` so remediation follows the established rails. Also trigger when filing issues about slop-mop friction — use `sm barnacle file` / `/slopmop:sm-barnacle`, never `gh issue create`.TestingNo warnings★ 3.7K↓ —
- tddbacknotprop/pstackUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.TestingNo warnings★ 3.3K↓ —Also in 3 other repos
- alchemy-cost-tuningjeremylongshore/tons-of-skills-marketplaceGovern Alchemy compute usage and spend with current account evidence, workload attribution, budgets, and reversible optimizations. Use when forecasting or reducing Alchemy cost. Trigger with "Alchemy cost", "Alchemy compute units", or "reduce Alchemy spend".OtherNo warnings★ 2.9K↓ —
golang-naming
samber/cc-skills-golang
TestingUpdated 22 hours ago
From the author
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
Install
npx skills add samber/cc-skills-golang --skill golang-naming -a claude-code
Installs to .claude/skills/golang-naming/ · 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 (7)
- SKILL.md
- evals/evals.json
- references/functions-methods.md
- references/identifiers.md
- references/packages-files.md
- references/testing.md
- references/types-errors.md