Zum Inhalt springen
fedi.software

Skills für Agenten

Skills für Claude Code, Codex, Cursor und andere Agenten aus dem Verzeichnis skills.sh: Installationen, Status der Sicherheitsprüfung und der Befehl zum Hinzufügen eines Skills.

Ein Skill ist an keinen Agenten gebunden: npx skills add installiert ihn in jeden unterstützten. Ohne -a findet das CLI die Agenten auf Ihrem Computer und fragt, wohin er soll.

Aktualisiert · Quellen: skills.sh

Angezeigt: 100 · gefunden: 121 · von 10.000 im Verzeichnis

  • caveman-commit juliusbrussee/caveman

    Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

    391.990 Bestanden
  • pr-to-video heygen-com/hyperframes

    Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

    310.083 Bestanden
  • requesting-code-review obra/superpowers

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    242.681 Bestanden
  • using-git-worktrees obra/superpowers

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    202.396 Bestanden
  • git-commit github/awesome-copilot

    Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

    45.879 Bestanden
  • ponytail-review dietrichgebert/ponytail

    Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

    32.309 Bestanden
  • code-review-excellence wshobson/agents

    Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

    29.208 Bestanden
  • resolve-merge-conflicts warpdotdev/common-skills

    Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.

    27.364 Bestanden
  • create-pr warpdotdev/common-skills

    Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.

    27.311 Bestanden
  • check-impl-against-spec warpdotdev/common-skills

    Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.

    25.806 Bestanden
  • github-actions-templates wshobson/agents

    Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.

    16.466 Bestanden
  • code-review-expert sanyuan0704/sanyuan-skills

    Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.

    13.237 Bestanden
  • changelog-automation wshobson/agents

    Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

    13.176 Bestanden
  • commit-context rohitg00/agentmemory

    Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.

    12.859 Bestanden
  • commit-history rohitg00/agentmemory

    List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.

    12.814 Bestanden
  • cpp-coding-standards affaan-m/ecc

    C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.

    10.845 Bestanden
  • convert-documents-to-markdown firecrawl/anydoc

    Convert Word (.doc, .docx), PowerPoint (.ppt, .pptx), Excel (.xls, .xlsx), OpenDocument (.odt, .ods, .odp), RTF, EPUB, CSV, and PDF files to GitHub-Flavored Markdown. Use when a task needs the contents of an office document, spreadsheet, presentation, ebook, or PDF you cannot read directly.

    10.693 Bestanden
  • workflow-patterns wshobson/agents

    Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

    10.495 Bestanden
  • genshijin-commit interfacex-co-jp/genshijin

    超圧縮コミットメッセージ生成。Conventional Commits形式で件名≤50文字、 「何を」より「なぜ」を重視。日本語・英語両対応。 「コミットメッセージ作って」「/commit」「/genshijin-commit」で起動。 ステージング変更時に自動起動候補。

    9.564 Bestanden
  • swiftui-performance-audit dimillian/skills

    Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.

    9.416 Bestanden
  • flutter-dart-code-review affaan-m/ecc

    Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture. Use when reviewing Flutter or Dart code, whatever state management library the project uses.

    9.057 Bestanden
  • github-copilot-starter github/awesome-copilot

    Set up complete GitHub Copilot configuration for a new project based on technology stack

    8.945 Bestanden
  • git-workflow affaan-m/ecc

    Git workflow patterns including branching strategies, commit conventions, keeping history clean and readable, tidying local commits before merging, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, cleaning up history before a pull request, deciding merge versus rebase, or resolving conflicts.

    8.809 Bestanden
  • tldr-prompt github/awesome-copilot

    Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.

    8.762 Bestanden
  • cargo-context getcargohq/cargo-skills

    Read and write the workspace GTM knowledge base — the git-backed repository of markdown describing ICPs, personas, plays, proof points, objections, competitors, and signals — plus its runtime sandbox and typed knowledge graph. Triggers: "document our ICP", "write up this persona", "what is our positioning", "add a battlecard", "capture this objection", "what do we know about <segment>", "update our context", "what is in the context repo", "who do we sell to". Skip when: discovering who actually buys from you by analyzing won/lost data — that is cargo-gtm (this skill writes the conclusion down, it does not derive it); storing structured records rather than prose — use cargo-storage; attaching documents to an agent for RAG — use cargo-content.

    8.099 Bestanden
  • safety-guard affaan-m/ecc

    Guard against destructive operations with three modes: Careful intercepts dangerous commands (rm -rf, git push --force, DROP TABLE) for confirmation, Freeze locks writes to one directory, and Guard combines both via PreToolUse hooks. Use when working on production systems, running agents autonomously, restricting edits to a directory, or during migrations, deploys, and data changes.

    8.041 Bestanden
  • unified-notifications-ops affaan-m/ecc

    Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.

    7.503 Bestanden
  • changelog-generator composiohq/awesome-claude-skills

    Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

    6.969 Bestanden
  • open-code-review alibaba/open-code-review

    Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply fixes when requested. With appropriate review rules, can detect various types of issues including bugs, security vulnerabilities, performance problems, and code quality concerns.

    6.035 Bestanden
  • block-no-verify-hook wshobson/agents

    Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.

    6.032 Bestanden
  • asc-whats-new-writer rorkai/app-store-connect-cli-skills

    Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.

    5.435 Bestanden
  • react-performance affaan-m/ecc

    React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.

    5.314 Bestanden
  • dbs-skill-maker dontbesilent2025/dbskill

    通过需求分析把反复出现的问题制作成可安装、可分级验证的单个 Skill。用户要求做 Skill、把问题沉淀成 Skill、检查或测试候选 Skill 时使用;只有用户明确要求分享或发布时,才准备 GitHub 仓库并验证 `npx skills add`。

    5.177 Bestanden
  • git-guardrails-claude-code vinvcn/mattpocock-skills-zh-cn

    设置 Claude Code hooks,在危险 git commands(push、reset --hard、clean、branch -D 等)执行前阻止它们。适用于用户想防止破坏性 git 操作、添加 git safety hooks,或在 Claude Code 中阻止 git push/reset 时。

    5.058 Bestanden
  • setup-pre-commit vinvcn/mattpocock-skills-zh-cn

    在当前仓库设置 Husky pre-commit hooks,集成 lint-staged (Prettier)、类型检查和测试。适用于用户想添加 pre-commit hooks、设置 Husky、配置 lint-staged,或在提交时运行格式化、类型检查和测试时。

    5.042 Bestanden
  • write-pr-description warpdotdev/common-skills

    Writes the body of a pull request - the summary, the repository template sections, and reviewer guidance such as a recommended reading order and focus areas. Use whenever drafting or revising a PR description, filling in a repository's PR template, refreshing a description that no longer matches the branch, or preparing a branch for review. Use it even when the user only says "open a PR", "put this up for review", or "write this up" without naming the description.

    4.908 Bestanden
  • premium-frontend-ui github/awesome-copilot

    A comprehensive guide for GitHub Copilot to craft immersive, high-performance web experiences with advanced motion, typography, and architectural craftsmanship.

    4.702 Bestanden
  • ljg-push lijigang/ljg-skills

    把 ~/.agents/skills/ljg-* 里所有更新过的 skills 同步到 github repo (ljg-skills),先推 master 分支(org-mode 输出风格),再切 md 分支(markdown 输出风格)做基础 markdown 化后推。Use when user says '/ljg-push', 'push skills', '推送 skills', '同步 skills', 'sync ljg', or whenever ljg-* skills get updated and need shipping. NOT FOR pushing non-ljg skills or arbitrary git repos.

    4.597 Bestanden
  • commit getsentry/skills

    Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.

    4.562 Bestanden
  • commerce-b2b-open-code-components-integrate forcedotcom/sf-skills

    Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention "integrate open code components", "open source B2B commerce", "add open code components", "forcedotcom/b2b-commerce-open-source-components", or want to add open source commerce components to their store. Copies all components and labels so they become available in Experience Builder.

    4.561 Bestanden
  • secret-scanning github/awesome-copilot

    Guide for configuring and managing GitHub secret scanning, push protection, custom patterns, and secret alert remediation. For pre-commit secret scanning in AI coding agents via the GitHub MCP Server, this skill references the Advanced Security plugin (`advanced-security@copilot-plugins`). Use this skill when enabling secret scanning, setting up push protection, defining custom patterns, triaging alerts, resolving blocked pushes, or when an agent needs to scan code for secrets before committing.

    4.484 Bestanden
  • dependabot github/awesome-copilot

    Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update configuration, auto-triage rules, or any GitHub Advanced Security (GHAS) supply chain security topic related to Dependabot. For pre-commit dependency vulnerability scanning in AI coding agents via the GitHub MCP Server, this skill references the Advanced Security plugin (`advanced-security@copilot-plugins`). Use this skill when an agent needs to scan dependencies for known vulnerabilities before committing.

    4.382 Bestanden
  • swiftui-performance dpearson2699/swift-ios-skills

    Profile, diagnose, and remediate SwiftUI runtime performance using code review, Instruments, and repeatable measurements. Use when a SwiftUI screen renders slowly, scrolling or animations hitch, view bodies update excessively, list identity churns, layout work spikes, or broad Observation dependencies raise CPU cost. Covers evidence-based triage, SwiftUI Instruments lanes, lazy-container guardrails, state lifetime, and before/after verification.

    4.328 Bestanden
  • writing-clearly-and-concisely softaworks/agent-toolkit

    Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

    4.243 Bestanden
  • create-branch getsentry/skills

    Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

    4.124 Bestanden
  • changelog generator claude-office-skills/skills

    Generate release notes from git commits, updates, or feature lists

    4.116 Bestanden
  • commit-work softaworks/agent-toolkit

    Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

    4.105 Bestanden
  • react-code-review giuseppe-trisciuoglio/developer-kit

    Provides comprehensive code review capability for React applications, validates component architecture, hooks usage, React 19 patterns, state management, performance optimization, accessibility compliance, and TypeScript integration. Use when reviewing React code changes, before merging pull requests, after implementing new features, or for component architecture validation. Triggers on "review React code", "React code review", "check my React components".

    4.016 Bestanden
  • orch-build-mvp affaan-m/ecc

    Orchestrate bootstrapping a working MVP from a design or spec document — ingest the SDD/PRD, plan thin vertical slices, scaffold the first end-to-end slice, then drive a generator-evaluator build loop with review and gated feat commits. Use when a design or spec document must become a running MVP through planned vertical slices.

    3.912 Bestanden
  • orch-add-feature affaan-m/ecc

    Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.

    3.902 Bestanden
  • orch-fix-defect affaan-m/ecc

    Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.

    3.898 Bestanden
  • orch-refine-code affaan-m/ecc

    Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.

    3.897 Bestanden
  • orch-change-feature affaan-m/ecc

    Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.

    3.886 Bestanden
  • admin grafana/skills

    Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO/SAML/OAuth/GitHub auth, service accounts for CI/CD, user invites, team membership, and API-driven provisioning. Creates stacks via the Cloud API, mints service-account tokens, applies role assignments, configures SSO providers, and provisions teams/folders/dashboards via Terraform. Use when managing Grafana Cloud access, configuring SSO/SAML/OAuth, setting up service accounts for Terraform/CI/CD, assigning RBAC roles, inviting users, managing multiple stacks or organizations, provisioning cloud resources via API or Terraform, or auditing admin actions — even when the user says "set up SSO", "create a stack", "make a service account", or "onboard a team" without explicitly saying "admin".

    3.620 Bestanden
  • nestjs-code-review giuseppe-trisciuoglio/developer-kit

    Provides comprehensive code review capability for NestJS applications, analyzing controllers, services, modules, guards, interceptors, pipes, dependency injection, and database integration patterns. Use when reviewing NestJS code changes, before merging pull requests, after implementing new features, or for architecture validation. Triggers on "review NestJS code", "NestJS code review", "check my NestJS controller/service".

    3.608 Bestanden
  • nextjs-code-review giuseppe-trisciuoglio/developer-kit

    Provides comprehensive code review capability for Next.js applications, validates Server Components, Client Components, Server Actions, caching strategies, metadata, API routes, middleware, and performance patterns. Use when reviewing Next.js App Router code changes, before merging pull requests, after implementing new features, or for architecture validation. Triggers on "review Next.js code", "Next.js code review", "check my Next.js app".

    3.605 Bestanden
  • graph-evolution trailofbits/skills

    Compares Trailmark code graphs at two source code snapshots (git commits, tags, or directories) to surface security-relevant structural changes. Detects new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications that text diffs miss. Use when comparing code between commits or tags, analyzing structural evolution, detecting attack surface growth, reviewing what changed between audit snapshots, or finding security-relevant changes that text diffs miss.

    3.534 Bestanden
  • ce-code-review everyinc/compound-engineering-plugin

    Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.

    3.498 Bestanden
  • no-mistakes kunchenguid/no-mistakes

    Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach the configured push target. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.

    3.378 Bestanden
  • docs-updater giuseppe-trisciuoglio/developer-kit

    Provides automated documentation updates by analyzing git changes between the current branch and the last release tag. Performs git diff analysis to identify modifications, then updates README.md, CHANGELOG.md following Keep a Changelog standard, and discovers documentation folders for contextual updates. Use when preparing a release, maintaining documentation sync, or before creating a pull request. Triggers on "update docs", "update changelog", "sync documentation", "update readme", "prepare release documentation".

    3.371 Bestanden
  • git-create-repo zc277584121/mygitplugin

    Create a new GitHub repository and clone it locally

    3.279 Bestanden
  • copilot-cli giuseppe-trisciuoglio/developer-kit

    Provides GitHub Copilot CLI task delegation in non-interactive mode with multi-model support (Claude, GPT, Gemini), permission controls, output sharing, and session resume. Use when users ask to hand work to Copilot, compare models, or run Copilot programmatically from Claude Code.

    3.275 Bestanden
  • git-commit-pr zc277584121/mygitplugin

    Commit changes and create a pull request to the official upstream repo

    3.221 Bestanden
  • ce-commit everyinc/compound-engineering-plugin

    Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.

    3.217 Bestanden
  • git-sync-main zc277584121/mygitplugin

    Sync local main branch with the latest code from official upstream or origin remote

    3.201 Bestanden
  • code-review-skill awesome-skills/code-review-skill

    Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C#/.NET, Kotlin, Swift, Dart, Flutter, NestJS, C/C++, Zig, CSS/Less/Sass, Qt, and more. Covers architecture review, performance review, security audit, code quality anti-patterns, and common bugs across all ecosystems. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, performance reviews, checking code quality, finding bugs, giving feedback on code.

    3.166 Bestanden
  • understand-diff egonex-ai/understand-anything

    Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks

    3.133 Bestanden
  • review-all gjkim42/kanon-repo

    Run a two-agent code review: spawn two fresh, clean-context agents that examine the SAME committed branch diff in parallel. One agent runs Codex's native `codex review --base` command, while the other independently reviews the code against Google's "What to look for in a code review" guidance. Merge both outputs into one agreement-ranked report. Use this whenever the user asks for "review-all", a second-opinion review, a dual review, a cross-check before a PR, or a maximum-confidence review of committed branch changes. Do not use it to APPLY fixes; it is review-only.

    3.106 Bestanden
  • standup thedotmack/claude-mem

    Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

    3.064 Bestanden
  • principle-sequence-verifiable-units cursor/plugins

    Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.

    3.002 Bestanden
  • oauth vercel-labs/portless

    Configure OAuth providers (Google, Apple, Microsoft, Facebook, GitHub, etc.) to work with portless local dev URLs. Use when setting up OAuth redirect URIs, fixing "redirect_uri_mismatch" or "invalid redirect" errors, configuring sign-in providers for local development, or when a provider rejects .localhost subdomains. Triggers include "OAuth not working with portless", "redirect URI mismatch", "Google/Apple/Microsoft sign-in fails locally", "configure OAuth for local dev", or any task involving OAuth callback URLs with portless domains.

    2.984 Bestanden
  • project-references dboeckli/ai-agent-skills

    Look up conventions, patterns, and concrete implementations from your own GitHub repositories checked out locally under ~/projects/referenzen/. Use this skill whenever there is uncertainty about how something is done in your codebase family — e.g. Helm chart structure, Kubernetes manifests, framework configuration patterns, Docker Compose conventions, CI/CD pipeline setup, or any other recurring architectural decision. Invoke it proactively before guessing at a convention; always cite the source project and path when a pattern is adopted. Also use when the user asks to check out, update, or search reference repositories, or to generate an overview/report of GitHub Actions triggers (push, pull_request, schedule/cron) across repositories.

    2.963 Bestanden
  • ce-worktree everyinc/compound-engineering-plugin

    Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch, PR, or commit. Use when starting isolated work or isolating an existing ref.

    2.950 Bestanden
  • unsafe-checker actionbook/rust-skills

    CRITICAL: Use for unsafe Rust code review and FFI. Triggers on: unsafe, raw pointer, FFI, extern, transmute, *mut, *const, union, #[repr(C)], libc, std::ffi, MaybeUninit, NonNull, SAFETY comment, soundness, undefined behavior, UB, safe wrapper, memory layout, bindgen, cbindgen, CString, CStr, 安全抽象, 裸指针, 外部函数接口, 内存布局, 不安全代码, FFI 绑定, 未定义行为

    2.948 Bestanden
  • netlify-deploy netlify/context-and-tools

    Create, configure, and manage Netlify deploys from code — reach for this when setting up Git continuous deployment, running netlify deploy or netlify deploy --prod from the CLI, writing netlify.toml deploy contexts, adding a Deploy to Netlify button, wiring build hooks, configuring Deploy Previews or branch deploys, locking or skipping deploys, fixing a failed or secrets-scanning deploy, or when someone asks to "deploy my site", "set up preview deploys", "add per-branch build config", or "add a deploy button to my README".

    2.911 Bestanden
  • forecast anthropics/knowledge-work-plugins

    Generate the commit / best-case / pipeline narrative for a forecast call or a 1:1 with your manager - what's closing, what's at risk, what changed since last time. Use when the user asks "write my forecast", "forecast narrative", "prep for forecast call", "prep for my quarterly forecast call", "which deals should I commit vs. call upside", "forecast from this pipeline export", or "prep for my 1:1 with my manager".

    2.859 Bestanden
  • open-code-review-delegate alibaba/open-code-review

    Delegation mode for open-code-review (OCR). Instead of OCR calling an LLM endpoint, this skill instructs the host agent to perform the code review itself, using OCR only for deterministic engineering: file selection and rule resolution. Use when the host agent should drive the review with its own LLM capabilities.

    2.837 Bestanden
  • bun-development sickn33/agentic-awesome-skills

    Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by [oven-sh/bun](https://github.com/oven-sh/bun).

    2.791 Bestanden
  • netlify-identity netlify/context-and-tools

    Add user authentication to a Netlify site with @netlify/identity — signup/login/logout, Google/GitHub/GitLab/Bitbucket OAuth, server-side getUser() checks, role-based access control, and Identity event functions. Use it when a task involves adding a login or signup form, gating content to members or roles, "auth middleware" or verifying users in Netlify Functions or Edge Functions, handling OAuth or email-confirmation callbacks, assigning roles at signup, or customizing Identity emails. For locking a whole site to your company or employees-only access, use netlify-access-control instead.

    2.641 Bestanden
  • animated-readme-logo stark-ai-de/agent-skills

    Create, transform, animate, or audit GitHub README logos and their verified SVG/PNG/GIF delivery. Use when a repository needs branding assets, not ordinary README prose or app/site motion.

    2.625 Bestanden
  • code-review-pro onewave-ai/claude-skills

    Performs a deep code review of files, modules, a diff, or a branch - finding security vulnerabilities (mapped to OWASP Top 10:2025), correctness bugs, performance problems, and maintainability issues - and returns severity-ranked findings with evidence and concrete fixes. Use when the user asks to review, audit, or sanity-check code, asks "is this safe", "what's wrong with this", "find bugs", or wants a security or performance pass before shipping. For posting line comments on a GitHub pull request, use git-pr-reviewer.

    2.535 Bestanden
  • conventional-git samber/cc-skills

    Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.

    2.514 Bestanden
  • copilot-delegate amelnagdy/delegate-skills

    Delegate a coding task to the GitHub Copilot CLI (`copilot`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of coding tasks through Copilot while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

    2.483 Bestanden
  • review-team cline/skills

    Use when the user asks for a code review by a fleet of specialized reviewer agents, wants multiple independent reviewer perspectives, or asks to run reviewers in single-pass or iterative fix-until-clean mode. Launches focused subagents for correctness, security, architecture, conventions, simplicity, UX, reliability, telemetry, testing, compatibility, and documentation review.

    2.476 Bestanden
  • open-standards-strategy samber/developer-relations-skills

    Decides how a company engages a named open standard or protocol - ignore it, consume it, certify conformance, extend it, contribute upstream, co-found a spec with peers, or drive its own as a de facto standard - plus the venue (Git-based spec, foundation, consortium, IETF/W3C/OASIS, ISO transposition), the patent-licensing mode, the conformance plan and the kill rule. Use whenever someone raises open standards participation, protocol strategy, standards body engagement, standards wars, joining versus competing with an emerging protocol, donating a specification to a neutral foundation, whether to standardize an interface at all, or a competitor's rival spec - even if they never say "standard". Not project governance - use samber/developer-relations-skills@oss-governance.

    2.452 Bestanden
  • open-source-company-strategy samber/developer-relations-skills

    Decides what a company open-sources and what stays proprietary, names the strategic motive for each side of the line, says who owns the decision, and states what the company commits never to close. Use whenever someone asks "should we open source this?", "what should we open source", "where do we draw the open-core line", "which features stay paid", "who signs off on open sourcing this", or wants a company-level open source strategy rather than a plan for one project - even if they frame it as a licensing question. Produces an asset-by-asset open/closed verdict, a value-capture and irreversibility check, a public non-reversal commitment and a re-evaluation trigger. Not license selection - use samber/developer-relations-skills@oss-license-strategy.

    2.441 Bestanden
  • code-review-analysis aj-geddes/useful-ai-prompts

    Perform comprehensive code reviews with best practices, security checks, and constructive feedback. Use when reviewing pull requests, analyzing code quality, checking for security vulnerabilities, or providing code improvement suggestions.

    2.408 Bestanden
  • pr-creator google-gemini/gemini-cli

    Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.

    2.347 Bestanden
  • review-and-ship cursor/plugins

    Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.

    2.333 Bestanden
  • what-did-i-get-done cursor/plugins

    Summarize authored commits over a user-specified time period into a concise update

    2.307 Bestanden
  • nushell-pro hustcer/nushell-pro

    Comprehensive Nushell scripting best practices, idioms, security, and evidence-driven code review. Use when writing, reviewing, auditing, debugging, or refactoring Nushell (.nu) scripts, modules, custom commands, pipelines, config, and tests. Also use for Bash/POSIX-to-Nushell conversion and Nu migration issues including custom completions, record-spread flags, YAML, SemVer, cleanup, and subprocess diagnostics.

    2.286 Bestanden
  • pr-review-comments giuseppe-trisciuoglio/developer-kit

    Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failure_scenario) and want them published on a PR as inline review comments. Triggers include "post these review comments on the PR", "associate comments to files in the PR", "publish review findings to PR #N", or having a JSON array of {file, line, summary} to turn into PR comments.

    2.276 Bestanden
  • merge-ready every-app/open-seo

    Take a branch from "code exists (or is about to)" to "ready for the maintainer's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR. Use whenever the user says a feature/fix/branch should be "merge ready", asks to get changes ready for review, or appends this to a build request ("build X and make it merge-ready").

    2.269 Bestanden
  • authoring-github-workflows dotnet/skills

    Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run. USE FOR: editing, adding, or reviewing any file under .github/workflows/, writing run-name/name/if/env/run values that contain ${{ }} expressions, diagnosing a run that fails with 'This run likely failed because of a workflow file issue' and no jobs starting, deciding when a workflow scalar must be quoted, validating workflows with actionlint. DO NOT USE FOR: authoring application YAML unrelated to GitHub Actions, Azure Pipelines, GitLab CI, or non-workflow YAML. SCOPE: this skill covers *syntactic/structural* correctness of workflow YAML (quoting, parsing, actionlint); for *semantic and functional* workflow design (what a workflow should do, agentic-workflow behavior), see .github/agents/agentic-workflows.agent.md — the two are complementary. INVOKES: actionlint (downloaded pinned binary) plus git/grep for inspection.

    2.166 Bestanden
  • dx-devops-pipeline-manage forcedotcom/sf-skills

    Use this skill to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to a Git repository, add or remove stages, rename a stage, add or remove Salesforce environments on stages, attach or detach projects, and activate or deactivate the pipeline. Invoke when the user wants to set up a release pipeline, wire promotion stages across integration, UAT, staging, and production orgs, connect environments to stages, attach a project, or activate a continuous delivery pipeline. Uses sf devops pipeline and sf devops stage commands with --json output. DO NOT TRIGGER for work-item lifecycle, promotion or deployment execution, conflict detection, or standalone project creation (separate skills).

    2.134 Bestanden
  • new-branch-and-pr cursor/plugins

    Create a fresh branch, complete work, and open a pull request

    2.100 Bestanden
  • checkpoint codewithmukesh/dotnet-claude-kit

    Mid-session save point: create a descriptive git commit and a brief handoff note, then keep working. Use before a risky change or refactor, when switching tasks, or to bank progress without ending the session. Triggers on: /checkpoint, "checkpoint", "save progress", "commit and handoff", "save state", "pause here", "before a risky change". For the full end-of-session ritual with learning extraction, use /wrap-up instead.

    1.986 Bestanden
  • code-quality cognitedata/builder-skills

    MUST be used whenever reviewing a Flows app for code quality, maintainability, or clean code issues — before a PR review, after a feature is complete, or when the user asks for a code review. Do NOT skip linting steps. Triggers: code quality, code review, clean code, refactor, maintainability, technical debt, any type, naming, dead code, duplication, DRY, single responsibility, component size, lint, linting, TypeScript strict, dependency injection, file structure.

    1.963 Bestanden
  • codeql github/awesome-copilot

    Comprehensive guide for setting up and configuring CodeQL code scanning via GitHub Actions workflows and the CodeQL CLI. This skill should be used when users need help with code scanning configuration, CodeQL workflow files, CodeQL CLI commands, SARIF output, security analysis setup, or troubleshooting CodeQL analysis.

    1.956 Bestanden
  • prisma-next-feedback prisma/prisma-next

    Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.

    1.915 Bestanden

Die Beschreibungen stammen von den Autoren selbst, auf Englisch. Lesen Sie den Code eines Skills in seinem Repository, bevor Sie ihn installieren.

Was Skills für Agenten sind

Ein Skill ist ein Ordner mit einer Datei SKILL.md – Anweisungen, die für einen KI-Agenten geschrieben sind – und manchmal Skripten oder Vorlagen. Passt eine Aufgabe zur Beschreibung des Skills, lädt ein Agent wie Claude Code, Codex oder Cursor ihn und folgt ihm: wie ein Formular auszufüllen ist, wie Code in einem bestimmten Stil geprüft wird, wie man mit einem bestimmten Dateiformat umgeht. Diese Seite ist ein Verzeichnis solcher Skills auf Basis von skills.sh.

Was das Verzeichnis zeigt

  • die 10.000 Skills mit den meisten Installationen, täglich synchronisiert;
  • zu jedem Skill Name, Autor und Repository, Installationen, Status der Sicherheitsprüfung und den Befehl zum Hinzufügen mit Kopier-Schaltfläche;
  • „Im Trend“: Skills, deren Installationen in den letzten 7 Tagen am stärksten zugelegt haben;
  • Filter nach Themen und Agenten sowie eine Suche; jede Ansicht zeigt bis zu 100 Skills.

Den Prüfstatus verstehen

skills.sh veröffentlicht Sicherheitsprüfungen von Skills. Wir zeigen das Ergebnis als „Bestanden“, „Warnungen“, „Nicht bestanden“ oder „Nicht geprüft“. Eine bestandene Prüfung senkt das Risiko, garantiert aber nichts: Ein Skill kann Skripte enthalten, die Ihr Agent auf Ihrem Rechner ausführt. Lesen Sie den Code im Repository, bevor Sie einen Skill installieren – besonders bei wenigen Installationen oder fehlender Prüfung.

Einen Skill installieren

  1. Den Skill über Themen, Agentenfilter oder Suche finden.
  2. Das Repository öffnen und SKILL.md sowie etwaige Skripte ansehen.
  3. Den Befehl aus der Zeile kopieren und im eigenen Projekt ausführen.
  4. Dem Agenten eine Aufgabe geben, die zum Skill passt.

Zu den Beschreibungen

Die kurzen Beschreibungen stammen von den Autoren, auf Englisch, so wie sie in der jeweiligen SKILL.md stehen. Wir übersetzen oder überarbeiten sie nicht, und die Installationszahlen stammen von skills.sh. Die Namen der Themen sind dagegen übersetzt, filtern lässt sich also auf Deutsch.