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,105 skills from 2,358 repositories · updated 19 hours ago
49,105 skills
- speckit-specifyforyourhealth111-pixel/Vibe-SkillsCreate or update feature specifications from natural language descriptions. Use when starting new features or refining requirements. Generates spec.md with user stories, functional requirements, and acceptance criteria following spec-driven development methodology.PlanningNo warnings★ 3.8K↓ —
- golang-lintsamber/cc-skills-golangLinting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive. Not for wiring a lint step into a GitHub Actions pipeline (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).DevOpsNo warnings★ 3.8K↓ —
- 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.8K↓ —
- ops-settingsdavepoon/buildwithclaudePost-setup credential manager. Shows current integration status (configured/missing/expired) and lets you update individual credentials without re-running the full setup wizard. Runs a smoke test after each update.TestingNo warnings★ 3.7K↓ —
- hex-prod-checklistjeremylongshore/tons-of-skills-marketplaceExecute Hex production deployment checklist and rollback procedures. Use when deploying Hex integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "hex production", "deploy hex", "hex go-live", "hex launch checklist".DevOpsNo warnings★ 2.9K↓ —
- 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.8K↓ —
- wiki-rebuildAr9av/obsidian-wikiArchive and rebuild wiki knowledge from source, or restore a prior archive. Use for full restart/recovery when incremental repair is inappropriate; this is broader and more destructive than ordinary update or lint.OtherNo warnings★ 3.7K↓ —
- groq-data-handlingjeremylongshore/tons-of-skills-marketplaceUse when you need to keep PII out of Groq API calls, filter model responses, audit-log conversations, or track token cost and usage for a Groq integration. Implements prompt sanitization, PII redaction, response filtering, and usage tracking. Trigger with phrases like "groq data", "groq PII", "groq GDPR", "groq data retention", "groq privacy", "groq compliance".LegalNo warnings★ 2.9K↓ —
- opsdavepoon/buildwithclaudeBusiness operations command center. Routes to the right ops command based on what you need — briefing, inbox, fires, projects, comms, triage, linear, revenue, deploy, or yolo mode.DevOpsNo warnings★ 3.7K↓ —
- ops-inboxdavepoon/buildwithclaudeFull inbox management across all channels — WhatsApp (wacli), Email (Gmail MCP), Slack (MCP), Telegram (user-auth MCP), Discord (webhook + REST read), Notion (MCP — comments, mentions, assigned tasks). Scans FULL inbox (not just unread), identifies messages needing replies, archives handled conversations.ProductivityNo warnings★ 3.7K↓ —
- gitlab-automationdavepoon/buildwithclaudeAutomate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.OtherNo warnings★ 3.7K↓ —
- slides-as-codeforyourhealth111-pixel/Vibe-SkillsBuild research slides with text-first source (Slidev/Marp/Reveal/Quarto) and reproducible export (PDF). Includes structure, figure reuse rules, and quality checklist for top-tier scientific presentations.DocumentsNo warnings★ 3.8K↓ —
- 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.8K↓ —
- 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.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.8K↓ —
- gsd:map-codebasedavepoon/buildwithclaudeAnalyze codebase with parallel mapper agents to produce .planning/codebase/ documentsPlanningNo warnings★ 3.7K↓ —
- whymichael-denyer/pstack-claudeUse 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.8K↓ —
- prompt-lookupforyourhealth111-pixel/Vibe-SkillsActivates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.OtherNo 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-never-block-on-the-humanmichael-denyer/pstack-claudeApply when tempted to ask 'should I do X?' on reversible work.OtherNo warnings★ 3.8K↓ —
- kiro-spec-designgotalab/cc-sddCreate comprehensive technical design for a specificationDesignNo warnings★ 3.7K↓ —Also in 4 other repos
- tao-run-on-slurmNVIDIA/skillsRemote SLURM GPU cluster execution over SSH with sbatch/srun, Pyxis/Enroot containers, and Lustre-backed results. Use when running TAO training/eval/inference jobs on an on-prem or DGX SLURM cluster. Trigger phrases include "run on SLURM", "submit sbatch", "DGX SLURM cluster", "Pyxis/Enroot container", "Lustre dataset".OtherNo warnings★ 3.8K↓ —
- think-harderforyourhealth111-pixel/Vibe-Skills4-phase structured analysis wrapper for vibe pre-routing (compatible with claude-code-settings think-harder semantics).EngineeringNo warnings★ 3.8K↓ —
- design-screenplugin87/ux-ui-agent-skillsDesign or build a page, screen, landing page, website, app or UI from a request - the whole job, end to end. Use this for "design a landing page", "build a settings screen", "make me a website", "design the onboarding", "ออกแบบหน้าเว็บ", "ทำหน้า landing", "ออกแบบ UI", "ทำแอป". It runs the pipeline no single skill covers: the house doctrine, a written Brief Inference so the result is not the statistical mean, a committed visual direction, tokens, build, the objective gates, then an adversarial critic. Hands off to data-dashboard for dense data screens, redesign for existing UI, and image-to-code when a reference image is given.DesignNo warnings★ 3.1K↓ —
golang-project-layout
samber/cc-skills-golang
From the author
Golang project layout and workspace setup — cmd/internal/pkg directory conventions, module and package naming, go.work workspaces, and essential configuration files. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, or discussing package restructuring, package splits, or module splits. Not for restructuring existing code without a layout change (→ See `samber/cc-skills-golang@golang-refactoring` skill).
Install
npx skills add samber/cc-skills-golang --skill golang-project-layout -a claude-code
Installs to .claude/skills/golang-project-layout/ · 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 (8)
- SKILL.md
- assets/.gitignore
- assets/Makefile
- evals/evals.json
- references/config.md
- references/directory-layouts.md
- references/testing-layout.md
- references/workspaces.md