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.
17.855 de skill-uri din 631 de depozite · actualizat acum 31 de minute
1.872 de skill-uri
- r-cli-appposit-dev/skillsBuild command-line apps in R using the Rapp package. Use when creating a CLI tool in R, adding argument parsing to an R script, turning an R script into a command-line app, shipping CLIs in an R package, or using Rapp (the alternative Rscript front-end). Also use for shebang scripts, exec/ directory in R packages, or subcommand-based R tools.InginerieFără avertismente★ 545↓ —
- verify-sourcesbitwize-music-studio/claude-ai-music-skillsCaptures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.InginerieFără avertismente★ 580↓ —
- setupbitwize-music-studio/claude-ai-music-skillsDetects your Python environment and guides you through installing plugin dependencies. Use on first-time setup or when MCP server fails to start.InginerieFără avertismente★ 580↓ —
- narrow-bare-rescueoliver-kriska/claude-elixir-phoenixNarrow bare rescue in Elixir so real errors like KeyError and typos; Use to audit rescues and refactor error handling.InginerieFără avertismente★ 569↓ —
- documentoliver-kriska/claude-elixir-phoenixUse when asked to document Elixir code: add or fill in @moduledoc and @doc for modules and functions. Documents tested code only; may add a README section or ADR. Not for docs lookup or audits.InginerieFără avertismente★ 569↓ —
- r-cliposit-dev/skillsComprehensive R package for command-line interface styling, semantic messaging, and user communication. Use this skill when working with R code that needs to: (1) Format console output with inline markup and colors, (2) Display errors, warnings, or messages with cli_abort/cli_warn/cli_inform, (3) Show progress indicators for long-running operations, (4) Create semantic CLI elements (headers, lists, alerts, code blocks), (5) Apply themes and customize output styling, (6) Handle pluralization in user-facing text, (7) Work with ANSI strings, hyperlinks, or custom containers. Also use when migrating from base R message/warning/stop, debugging cli code, or improving existing cli usage.InginerieFără avertismente★ 545↓ —
- entroly-agent-reviewjuyterman1000/entrolyHand off coding work between AI agents or models and record an independent review tied to the exact repository state. Use when switching from a writer such as Claude to a reviewer such as Codex.InginerieFără avertismente★ 479↓ —Apare și în 1 alt depozit
- xcode-project-analyzerAvdLee/Xcode-Build-Optimization-Agent-SkillAudit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.InginerieFără avertismente★ 1,3 K↓ —
- shiny-py-optimizeposit-dev/skillsDiagnose and fix performance problems in Shiny for Python apps — slow startup, sluggish interactions, blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny for Python app is slow, hangs, recomputes too much, times out, or must support more users; when the user asks to "speed up", "optimize", or "make faster" a Python Shiny app; or when preparing a prototyped app for real-world traffic.InginerieFără avertismente★ 545↓ —
- techdebtoliver-kriska/claude-elixir-phoenixAnalyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.InginerieFără avertismente★ 569↓ —
- super-reviewActualizatEricTechPro/super-boardReviewer lane of the super-board pipeline and standalone PR/branch readiness review — forms its own hypotheses before reading the builder's summary, remembers prior findings and re-checks each with file:line proof, runs an adversarial truth-check on non-trivial diffs, and classes every finding (Gap, Bug, Verification miss, Scope drift, Over-engineering via `ponytail:ponytail-review`). Merges only through `super-board-merge-gate.sh`, pinned to the reviewed head SHA, and routes other fixes to Super Build or Super QA via the board. Use when the user says "Super Review", "review this branch", "review loop", "make sure this is merge-ready", "PR review", or asks for code, architecture, security, QA evidence, or release-readiness judgment.InginerieFără avertismente★ 468↓ —
- liveview-patternsoliver-kriska/claude-elixir-phoenixBuild LiveView: async data (assign_async), PubSub (check connected?); Use when handling interactions, debugging…InginerieFără avertismente★ 569↓ —
- windbg-user-ttd-reverse-debugging-triagemicrosoft/win-dev-skillsUse when an app, service, or user-mode driver host TTD recording is available and earlier calls, writes, or lifetimes matter. Not for kernel replay or history from a normal dump.InginerieFără avertismente★ 477↓ —
- windbg-user-mutex-held-across-co-awaitmicrosoft/win-dev-skillsUse when app, service, or user-mode driver C++ coroutine code holds a thread-affine lock across suspension and later hangs or fails. Not for all coroutine crashes or choosing lock performance.InginerieFără avertismente★ 477↓ —
- gh-review-requestsgetsentry/skillsFetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".OficialInginerieFără avertismente★ 1,1 K↓ —
- iterate-prgetsentry/skillsIterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.OficialInginerieFără avertismente★ 1,1 K↓ —
- wechat-official-reviewDevin-AXIS/iPolloWorkTurn bounded draft, publication, and comment evidence into a concise WeChat Official Account operating review and next-step plan.InginerieFără avertismente★ 7,2 K↓ —
- typo-finderzhuyansen/agent-skills-hubFind typos and repeated words in documentation without changing technical terms or code.InginerieFără avertismente★ 463↓ —
- 128-java-genericsjabrena/plinthUse when you need to review, improve, or refactor Java code for generics quality — including avoiding raw types, applying the PECS (Producer Extends Consumer Super) principle for wildcards, using bounded type parameters, designing effective generic methods, leveraging the diamond operator, understanding type erasure implications, handling generic inheritance correctly, preventing heap pollution with @SafeVarargs, and integrating generics with modern Java features like Records, sealed types, and pattern matching. This should trigger for requests such as Improve the code with Generics; Apply Generics; Refactor the code with Generics; Improve generic type safety in Java APIs; Fix raw types and unchecked casts in Java code. Part of Plinth ToolkitInginerieFără avertismente★ 455↓ —
- 124-java-secure-codingjabrena/plinthUse when you need to apply Java secure coding best practices — including validating untrusted inputs, defending against injection attacks with parameterized queries, minimizing attack surface via least privilege, applying strong cryptographic algorithms, handling exceptions securely without exposing sensitive data, managing secrets at runtime, avoiding unsafe deserialization, and encoding output to prevent XSS. This should trigger for requests such as Review Java code for secure coding; Find input validation risks in Java code; Review Java code for injection vulnerabilities; Improve secure error handling in Java services; Harden Java code against common security flaws. Part of Plinth ToolkitInginerieFără avertismente★ 455↓ —
- 164-java-profiling-verifyjabrena/plinthUse when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading; Compare before and after profiling results; Check for performance regressions after refactoring. Part of Plinth ToolkitInginerieFără avertismente★ 455↓ —
- 163-java-profiling-refactorjabrena/plinthUse when you need to refactor Java code based on trusted profiling analysis findings — including reviewing repository-owned or maintainer-sanitized docs/profiling-problem-analysis and docs/profiling-solutions files, identifying specific performance bottlenecks, and implementing targeted code changes to address CPU, memory, or threading issues. This should trigger for requests such as Refactor the code with profiling; Apply profiling; Optimize hot path; Reduce allocations found in profiling; Fix CPU bottlenecks from profiling analysis. Part of Plinth ToolkitInginerieFără avertismente★ 455↓ —
- 110-java-maven-best-practicesjabrena/plinthUse when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should trigger for requests such as Review pom.xml to improve it; Apply Maven best practices to pom.xml; Improve Maven POM configuration; Review Maven dependency management and plugin configuration; Modernize Maven build conventions for a Java project. Part of Plinth ToolkitInginerieFără avertismente★ 455↓ —
- 501-frameworks-micronaut-corejabrena/plinthUse when building or reviewing Micronaut applications — Micronaut.run bootstrap, @Singleton/@Prototype, @Factory beans, @ConfigurationProperties, environments, @Requires, @Controller vs services, @Scheduled, graceful shutdown, @ExecuteOn for blocking work, and Jakarta-consistent APIs. This should trigger for requests such as Review Java code for Micronaut application structure and beans; Apply best practices for Micronaut configuration, @Requires, and factories; Improve scheduling, shutdown, or threading in Micronaut services. ; Review Micronaut dependency injection scopes and factories; Configure Micronaut @Requires conditions for environments. Part of Plinth ToolkitInginerieFără avertismente★ 455↓ —