Skill-uri pentru agenți pe care le poți verifica înainte să le instalezi
Skill-uri SKILL.md publice din depozite GitHub cu peste 50 de stele și de la producători, scanate și evaluate. Instalează oricare dintre ele cu o singură comandă în Claude Code, Cursor, Codex, GitHub Copilot sau Gemini CLI.
8.582 de skill-uri din 252 de depozite · actualizat acum 27 de minute
956 de skill-uri
- gsd:reviewdavepoon/buildwithclaudeRequest cross-AI peer review of phase plans from external AI CLIsInginerieFără avertismente★ 3,7 K↓ —
- holoscan-install-wheelNVIDIA/skillsInstall Holoscan SDK 5.x CUDA 13 Python wheels in an isolated environment, choosing the full stack or version-matched components.InginerieFără avertismente★ 3,7 K↓ —
- nemo-relay-get-startedNVIDIA/skillsUse this skill when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation before production setup.InginerieFără avertismente★ 3,7 K↓ —
- doca-telemetry-exporterNVIDIA/skillsUse this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is installed — defining a doca_telemetry_exporter_schema and event types, creating sources, picking a publish surface (typed events / opaque events / the metrics counter-gauge-histogram API / OTLP logs / NetFlow), walking the schema-then-source lifecycle, or debugging DOCA_ERROR_* failures from the exporter API. Trigger even when the user does not explicitly mention "DOCA Telemetry Exporter" or "doca_telemetry_exporter_*" — typical implicit phrasings include "publishing counters from my DOCA app", "BAD_STATE when I report an event", "consumer/DTS sees nothing but my report succeeded", "how do I export NetFlow/IPFIX records", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service (DTS), plain stdout logging via doca_log, or real-time event subscription back into the app via doca-comch — those belong to other skills.InginerieFără avertismente★ 3,7 K↓ —
- reviewdavepoon/buildwithclaudePower-user audit of Origin's pending surfaces. Most users want `/brief` for revisions. That handles the daily flow. Use `/review` only for explicit deep-walk audits after bulk imports, or when you want to walk the full queue rather than the top 3 shown in /brief. Invoked as `/review captures` or `/review revisions`.InginerieFără avertismente★ 3,7 K↓ —
- closedavepoon/buildwithclaudeCommit the session to durable vault memory and prepare a clean resume pointInginerieFără avertismente★ 3,7 K↓ —
- 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.InginerieFără avertismente★ 3,7 K↓ —
- gsd:code-reviewdavepoon/buildwithclaudeReview source files changed during a phase for bugs, security issues, and code quality problemsInginerieFără avertismente★ 3,7 K↓ —
- gsd:eval-reviewdavepoon/buildwithclaudeRetroactively audit an executed AI phase's evaluation coverage — scores each eval dimension as COVERED/PARTIAL/MISSING and produces an actionable EVAL-REVIEW.md with remediation planInginerieFără avertismente★ 3,7 K↓ —
- spenddavepoon/buildwithclaudeShow current Claude Code spend by project and branch via BudgetClawInginerieFără avertismente★ 3,7 K↓ —
- gsd:review-backlogdavepoon/buildwithclaudeReview and promote backlog items to active milestoneInginerieFără avertismente★ 3,7 K↓ —
- dispatchdavepoon/buildwithclaudeDelegate tasks to OpenAI Codex CLI and Google Antigravity CLI from Claude Code. Say 'check with codex' or 'ask gemini for a second opinion' and Claude runs the other agent, keeps a topic-aware session, and critiques the result.InginerieFără avertismente★ 3,7 K↓ —
- gsd:code-review-fixdavepoon/buildwithclaudeAuto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.InginerieFără avertismente★ 3,7 K↓ —
- thumbgatedavepoon/buildwithclaudeA single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClawInginerieFără avertismente★ 3,7 K↓ —
- ops-triagedavepoon/buildwithclaudeCross-platform issue triage. Pulls from Sentry (MCP), Linear (MCP), GitHub Issues (gh). Cross-references against code to find already-fixed issues. Auto-resolves fixed ones. Dispatches agents for active issues.InginerieFără avertismente★ 3,7 K↓ —
- wan27-mediadavepoon/buildwithclaudeGenerate images and videos with Wan27, discover available models, estimate credit costs, and retrieve generation results through its MCP tools or CLI. Use when the user chooses Wan27 or wan2-7.io for media creation or task tracking.InginerieFără avertismente★ 3,7 K↓ —
- golang-modernizesamber/cc-skills-golangModernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for structural refactors, extracting functions, or moving code between packages (→ See `samber/cc-skills-golang@golang-refactoring` skill).InginerieFără avertismente★ 3,5 K↓ —
- golang-samber-dosamber/cc-skills-golangDependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, when the codebase imports github.com/samber/do or github.com/samber/do/v2, or when refactoring manual constructor injection into a DI container.InginerieFără avertismente★ 3,5 K↓ —
- golang-performancesamber/cc-skills-golangGolang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (→ See `samber/cc-skills-golang@golang-benchmark` skill) or debugging workflow (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).InginerieFără avertismente★ 3,5 K↓ —
- golang-code-stylesamber/cc-skills-golangGolang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).InginerieFără avertismente★ 3,5 K↓ —
- golang-pkg-go-devsamber/cc-skills-golangGolang package and module lookup via `godig`, a pkg.go.dev API client (CLI + MCP server). Use for any Go/Golang library's documentation, API signatures, symbols, usage examples, which versions exist, licenses, whether a dependency has CVEs, or who imports a package — prefer this over Context7 for any Go package or module. Read-only, no auth. Not for upgrading dependencies (→ See `samber/cc-skills-golang@golang-dependency-management` skill), choosing a library (→ See `samber/cc-skills-golang@golang-popular-libraries` skill), or local symbols and an already-used dependency's resolved source, call sites, and generic instantiations (→ See `samber/cc-skills-golang@golang-gopls` skill).InginerieFără avertismente★ 3,5 K↓ —
- golang-refactoringsamber/cc-skills-golangGolang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).InginerieFără avertismente★ 3,5 K↓ —
- golang-project-layoutsamber/cc-skills-golangGolang 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).InginerieFără avertismente★ 3,5 K↓ —
- claude-md-reviewwesammustafa/Claude-Code-Everything-You-Need-to-KnowAudit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale facts, and bloat. Use when asked to review, audit, improve, shrink, or fix a CLAUDE.md, and when a project's results feel inconsistent or Claude keeps rediscovering the same context.InginerieFără avertismente★ 3,5 K↓ —