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: 320 · von 10.000 im Verzeichnis

  • tdd mattpocock/skills

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    1.028.752 Bestanden
  • safe-debug lllllllama/rigorpilot-skills

    Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

    310.731 Bestanden
  • systematic-debugging obra/superpowers

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    280.800 Bestanden
  • test-driven-development obra/superpowers

    Use when implementing any feature or bugfix, before writing implementation code

    242.482 Bestanden
  • finishing-a-development-branch obra/superpowers

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    200.326 Bestanden
  • 198.658 Bestanden
  • durable-objects cloudflare/skills

    Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.

    92.549 Bestanden
  • playwright-stealth-verify liarjsdev/liarjs-skills

    Check whether a Playwright, Puppeteer, Selenium or CDP-driven browser presents a coherent fingerprint, using liarjs as a library against a Page you already have - navigator.webdriver, HeadlessChrome tokens, worker versus main-thread identity, patched-API integrity, WebGL versus WebGPU GPU identity. Use when asked whether an automated browser looks like a normal one, when a headless setup or a stealth plugin's effect needs measuring rather than assuming, or when an assertion on fingerprint quality belongs in a test suite.

    79.640 Bestanden
  • ab-testing coreyhaines31/marketingskills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

    67.952 Bestanden
  • momentic-test momentic-ai/skills

    Create, run, and maintain Momentic browser E2E tests and modules stored as *.test.yaml and *.module.yaml files.

    58.835 Bestanden
  • 52.125 Bestanden
  • momentic-mobile-test momentic-ai/skills

    Create, run, and maintain Momentic mobile E2E tests and modules for Android and iOS. Use Momentic MCP tools for live device validation, and use direct v2 YAML edits only for high-confidence local mobile v2 changes.

    44.629 Bestanden
  • golang-testing samber/cc-skills-golang

    Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.

    39.360 Bestanden
  • vitest antfu/skills

    Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

    39.343 Bestanden
  • golang-naming samber/cc-skills-golang

    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.

    37.134 Bestanden
  • golang-documentation samber/cc-skills-golang

    Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.

    36.837 Bestanden
  • golang-popular-libraries samber/cc-skills-golang

    Golang library and framework selection — vetted production-ready options by category (web, database, testing, logging, messaging), new and experimental stdlib packages, standard-library-first tradeoffs, and maturity signals (maintenance, license, importer counts). Apply when the user asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project. Not for a specific library's API once chosen (→ See that library's dedicated skill, e.g. `samber/cc-skills-golang@golang-samber-lo`), nor for go.mod mechanics, upgrades, or vulnerability audits (→ See `samber/cc-skills-golang@golang-dependency-management` skill).

    36.005 Bestanden
  • golang-stretchr-testify samber/cc-skills-golang

    Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification, suite lifecycle, and advanced patterns like Eventually, JSONEq, and custom matchers. Apply when the codebase imports github.com/stretchr/testify.

    35.883 Bestanden
  • flutter-add-widget-test flutter/agent-plugins

    Implement a component-level test using `WidgetTester` to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.

    35.705 Bestanden
  • flutter-add-integration-test flutter/agent-plugins

    Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integration_test package.

    34.875 Bestanden
  • python-testing-patterns wshobson/agents

    Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

    34.542 Bestanden
  • convex-test get-convex/agent-skills

    Generate convex-test tests for the app's Convex functions.

    29.244 Bestanden
  • convex-verify get-convex/agent-skills

    Prove a Convex feature works — seed, drive as multiple mocked users via convex-test, assert behavior including the negative authz cases (wrong user refused, data-scope enforced).

    29.186 Bestanden
  • fix-errors warpdotdev/common-skills

    Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.

    27.465 Bestanden
  • e2e-testing-patterns wshobson/agents

    Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

    23.466 Bestanden
  • prompt-engineering-patterns wshobson/agents

    This skill should be used when the user asks to "optimize a prompt", "improve prompt performance", "design a prompt template", "write better prompts", "debug prompt issues", "use chain-of-thought", "structured prompting", "few-shot prompting", or wants to apply advanced prompt engineering patterns for production LLM applications.

    22.439 Bestanden
  • argent-react-native-app-workflow software-mansion/argent

    Step-by-step workflows for developing or debugging React Native apps on iOS simulator or Android emulator. Use when starting the app, debugging Metro, fixing builds, diagnosing runtime errors, or running tests.

    22.097 Bestanden
  • argent-metro-debugger software-mansion/argent

    Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP) through the same surface. Use when connecting to the runtime, inspecting React components, reading console logs, or evaluating JavaScript.

    21.972 Bestanden
  • javascript-testing-patterns wshobson/agents

    Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

    19.718 Bestanden
  • neon-postgres-branches neondatabase/agent-skills

    Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, resetting a branch from its parent, branch expiration and CI/CD branch lifecycles, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch", "branch per PR" and "sensitive data testing".

    19.480 Bestanden
  • momentic-maintain momentic-ai/skills

    Diagnose, classify, triage, and repair failing Momentic tests with MCP run tools, the Momentic CLI, and manual run artifacts. Use when a developer asks what happened on a branch, DevX or on-call asks why main is red, or the user wants to inspect classifications, de-flake quarantined or recovered tests, reduce retries, re-classify runs, run AI triage, or repair failures.

    17.641 Bestanden
  • dart-add-unit-test dart-lang/skills

    Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.

    17.488 Bestanden
  • vue-testing-best-practices antfu/skills

    17.183 Bestanden
  • dart-generate-test-mocks dart-lang/skills

    Define and generate mock objects for external dependencies using `package:mockito` and `build_runner`. Use when unit testing classes that depend on complex external services like APIs or databases.

    16.731 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.513 Bestanden
  • flutter-animations madteacher/mad-agents-skills

    Add, fix, refactor, debug, test, or explain Flutter animations and motion effects. Use when working with implicit animations such as AnimatedContainer, AnimatedOpacity, AnimatedSwitcher, and TweenAnimationBuilder; explicit animations using AnimationController, Tween, CurvedAnimation, AnimatedWidget, AnimatedBuilder, and built-in transitions; Hero/shared-element route transitions; staggered or sequenced animations; physics-based motion, gestures, springs, flings, scroll physics, curves, performance, accessibility, reduced motion, and animation lifecycle bugs.

    15.208 Bestanden
  • mo-qa momentic-ai/skills

    Run and control Mo QA sessions with Momentic's `qa` CLI. Use for bug bashes, status checks, report export, replies to Mo, file transfer, or repairs based on Mo findings.

    13.524 Bestanden
  • golang-testing affaan-m/ecc

    Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices. Use when writing Go tests — table-driven cases, subtests, benchmarks, fuzzing, or coverage.

    13.035 Bestanden
  • debugging-strategies wshobson/agents

    Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

    12.849 Bestanden
  • webapp-testing github/awesome-copilot

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    12.379 Bestanden
  • vue-testing-best-practices vuejs-ai/skills

    Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.

    12.347 Bestanden
  • wcag-audit-patterns wshobson/agents

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

    11.928 Bestanden
  • writing-unit-tests riekelt/principal-engineer

    Use when writing or refactoring unit tests - a new test file, added cases, a flaky test, an unreadable one. Encodes behavior-first testing: one behavior per test, names that state the claim, deterministic setup, mocks only at boundaries you do not own. Use whenever a test is being written, even a quick one, and whenever a test needs a sleep, a mock of your own code, or a copy of the implementation's math.

    11.906 Bestanden
  • principal-engineering riekelt/principal-engineer

    Use when doing any non-trivial engineering work - implementing, debugging, refactoring, configuring, operating, or investigating why a system misbehaves - or any change where being wrong has a cost. Encodes the evidence-over-theory discipline, the hard safety rules, and the pre-change checkpoint. Use whenever code, data, or infrastructure is about to change or must be understood before it can, even if the task looks routine or is only "find out why". Foundation for the sibling skills.

    11.905 Bestanden
  • testing-changes riekelt/principal-engineer

    Use when deciding what tests a change needs - a feature, a bug fix, a refactor, any behavior change - or when reviewing whether a diff's tests are sufficient. Encodes tests-change-with-behavior, the bug-regression pattern, and assertion discrimination. Use whenever behavior changes and the test diff is empty, especially when the change is "too small to test".

    11.857 Bestanden
  • dart-add-unit-test flutter/agent-plugins

    Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.

    11.589 Bestanden
  • tdd-workflow affaan-m/ecc

    Test-driven development workflow: write a failing test first, watch it fail, implement the smallest change to green, then refactor with 80%+ coverage across unit, integration, and E2E tests. Use when writing a new feature, fixing a bug, refactoring, or when told to write failing tests first.

    11.472 Bestanden
  • dart-generate-test-mocks flutter/agent-plugins

    Define and generate mock objects for external dependencies using `package:mockito` and `build_runner`. Use when unit testing classes that depend on complex external services like APIs or databases.

    11.309 Bestanden
  • python-testing affaan-m/ecc

    Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements. Use when writing pytest tests — fixtures, mocks, parametrization, or coverage.

    11.072 Bestanden
  • argent-qa-flows software-mansion/argent

    Create repeatable QA regression E2E tests as Argent flows from test cases, tickets, or acceptance criteria. Use when the user asks to generate or preserve an automated regression scenario, with deterministic setup, stable targets, executable structural or visual evidence, and two consecutive full passes. For one-off UI checks or replayable paths without acceptance criteria, use argent-test-ui-flow or argent-create-flow. Supports iOS, Android, Chromium, and Vega (Fire TV), where recorded tv-remote steps replace touch directives. Apple TV and Android TV are unsupported; use argent-tv-interact there and report the limitation.

    10.819 Bestanden
  • dependency-upgrade wshobson/agents

    Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.

    10.611 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.526 Bestanden
  • airflow-dag-patterns wshobson/agents

    Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.

    10.485 Bestanden
  • e2e-testing affaan-m/ecc

    Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.

    10.470 Bestanden
  • bats-testing-patterns wshobson/agents

    Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.

    10.425 Bestanden
  • web3-testing wshobson/agents

    Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.

    10.300 Bestanden
  • sast-configuration wshobson/agents

    Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

    10.252 Bestanden
  • springboot-tdd affaan-m/ecc

    Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

    10.241 Bestanden
  • screen-reader-testing wshobson/agents

    Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

    10.185 Bestanden
  • rust-testing affaan-m/ecc

    Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

    10.171 Bestanden
  • limrun-detox-testing limrun-inc/skills

    Configure, run, or debug Detox on Limrun iOS simulators. Use when attaching the Limrun Detox runtime to an app, wiring Detox mediator connectivity, or validating app/tester connections over destination tunnels.

    10.100 Bestanden
  • limrun-xcode limrun-inc/skills

    Build an iOS / Apple app on remote Xcode with `lim xcode build` instead of local xcodebuild, run project commands with `lim xcode run`, or run its XCTest suites with `lim xcode test`, from any environment (Linux, Windows, macOS, VM, container). Use for non-Bazel projects (an `.xcodeproj` / `.xcworkspace`, an XcodeGen `project.yml` with a gitignored project, React Native / Expo native build) when the user wants to build, compile, run code generation or Make targets, test, inspect build logs, reload, produce a preview build, or ship a signed device IPA. To run, tap, screenshot, or otherwise interact with the result on a simulator, use limrun-ios-simulator. For Bazel workspaces, use limrun-xcode-bazel.

    10.096 Bestanden
  • nature-statistics yuan1z0825/nature-skills

    Audit or improve manuscript statistical reporting, including experimental units, replication, uncertainty, tests, and figure statistics. Use for 统计审查、统计方法小节、图注统计 and reviewer concerns; compute new analyses only when requested with data.

    10.032 Bestanden
  • verification-loop affaan-m/ecc

    Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.

    9.967 Bestanden
  • cpp-testing affaan-m/ecc

    Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

    9.890 Bestanden
  • break jakubkrehel/skills

    Renders a component you choose in every state and scenario on a temporary page and stress tests it.

    9.874 Bestanden
  • dogfood callstack/agent-device

    Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

    9.841 Bestanden
  • kotlin-coroutines-flows affaan-m/ecc

    Kotlin Coroutines and Flow patterns for Android and KMP — structured concurrency, Flow operators, StateFlow, error handling, and testing. Use when writing coroutines or Flow code on Android or KMP, or debugging cancellation and concurrency.

    9.651 Bestanden
  • mcp-builder mcp-use/mcp-use

    Build, modify, debug, migrate, review, or verify TypeScript MCP servers and MCP Apps with mcp-use. Use for tools, resources, prompts, middleware, Views, authentication, Skills over MCP, scaffolding, and advanced features.

    9.618 Bestanden
  • django-verification affaan-m/ecc

    Run the full Django verification loop — environment check, mypy/ruff/black linting, migration safety, pytest with coverage targets, pip-audit and bandit security scans, settings and logging review, and diff review — producing a phased pass/fail report before release or PR. Use when preparing a Django pull request, validating migrations or coverage, or running pre-deploy readiness checks.

    9.581 Bestanden
  • laravel-tdd affaan-m/ecc

    Laravel testing strategies with PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage. Use when writing Laravel tests with PHPUnit or Pest, or driving a Laravel feature test-first.

    9.576 Bestanden
  • parallel-debugging wshobson/agents

    Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.

    9.524 Bestanden
  • springboot-verification affaan-m/ecc

    Run the full Spring Boot verification loop — Maven or Gradle build, SpotBugs, PMD, and Checkstyle static analysis, unit and Testcontainers integration tests with JaCoCo coverage, OWASP dependency and secret scans, and diff review — producing a pass/fail readiness report. Use when preparing a Spring Boot pull request, validating coverage thresholds, or running pre-deploy verification.

    9.496 Bestanden
  • chatgpt-app-builder mcp-use/mcp-use

    Build, modify, debug, migrate, review, or verify TypeScript MCP servers and MCP Apps with mcp-use. Use for tools, resources, prompts, middleware, Views, authentication, Skills over MCP, scaffolding, and advanced features.

    9.357 Bestanden
  • swift-testing-pro twostraws/swift-testing-agent-skill

    Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.

    9.304 Bestanden
  • orca-per-workspace-env stablyai/orca

    Set up, review, debug, or validate an Orca per-workspace environment recipe: the on-demand, disposable runtime (cloud sandbox, VM, SSH host, or local container) Orca creates fresh for each workspace. Use to stand up a new recipe end to end, fix an `environmentRecipes` entry in `orca.yaml`, scaffold provider lifecycle scripts, or resolve an `orca vm recipe doctor` failure. Use `orca-cli` for ordinary worktree and workspace creation with no recipe involved.

    9.200 Bestanden
  • bun-runtime affaan-m/ecc

    Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

    9.191 Bestanden
  • ai-regression-testing affaan-m/ecc

    Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.

    9.072 Bestanden
  • swift-protocol-di-testing affaan-m/ecc

    Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing. Use when Swift code needs testing and file system, network, or external APIs must be mocked.

    9.049 Bestanden
  • kotlin-testing affaan-m/ecc

    Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices. Use when writing Kotlin tests with Kotest or MockK, or testing coroutines and checking coverage.

    9.030 Bestanden
  • flutter-testing-apps flutter/agent-plugins

    8.943 Bestanden
  • ralphinho-rfc-pipeline affaan-m/ecc

    Split an RFC into a multi-agent execution DAG — decompose into work units with dependencies and acceptance tests, run research, plan, implement, test, and review per unit, then merge through a queue with re-based branches and final system verification. Use when a feature is too large for a single agent pass, orchestrating RFC-driven multi-agent execution, or managing merge queues across agent-built units.

    8.734 Bestanden
  • msw-scripting msw-git/msw-ai-coding-plugins-official

    Authoring MSW scripts (.mlua) plus integrated playtest and debugging. Covers mlua syntax, annotations (@Component/@Logic/@ExecSpace/@Sync), lifecycle, exec spaces, property sync, event system, file workflow, build-log inspection, error classification, and the test/debug loop. Keywords: script, mlua, lua, Component, Logic, annotation, ExecSpace, Sync, event, play, test, debug, lifecycle.

    8.568 Bestanden
  • perl-testing affaan-m/ecc

    Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology. Use when writing Perl tests with Test2::V0 or Test::More, or measuring coverage.

    8.513 Bestanden
  • laravel-verification affaan-m/ecc

    Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness. Use when verifying a Laravel project before merge or deploy — lint, static analysis, tests, coverage, security.

    8.358 Bestanden
  • terraform-test hashicorp/agent-skills

    Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution.

    8.268 Bestanden
  • ui-demo affaan-m/ecc

    Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.

    8.110 Bestanden
  • managed-deep-agents langchain-ai/langchain-skills

    INVOKE THIS SKILL when building, testing, or deploying Managed Deep Agents in LangSmith with the mda CLI. Walks a user through their first agent end to end — interviewing them about what they want to build, mapping it onto what MDA can actually do, then scaffolding and deploying it. Covers the file-based project layout; define_deep_agent / defineDeepAgent; instructions, skills, memory, identity, tools, middleware, sandboxes, schedules, channels, and evals; mda init/build/dev/deploy/logs/delete; and Context Hub.

    8.044 Bestanden
  • agent-introspection-debugging affaan-m/ecc

    Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

    7.927 Bestanden
  • meticulous-test alwaysmeticulous/skills

    Run a Meticulous test run after implementing a frontend change, then hand off to the `meticulous-review` skill to classify each visual change as intended or unintended. Uploads the build once — the same build can be re-triggered against different bases without rebuilding — and it works with uncommitted changes. Use when implementing a feature autonomously end-to-end before creating a PR.

    7.817 Bestanden
  • meticulous-use-session-data alwaysmeticulous/skills

    Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Use when you need to understand what user interactions and API calls a test covers, or when you want network mocks for writing tests.

    7.798 Bestanden
  • csharp-testing affaan-m/ecc

    C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices. Use when writing or reviewing xUnit tests, mocks, or integration tests in a C# / .NET project.

    7.689 Bestanden
  • cypress-docs cypress-io/ai-toolkit

    Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.

    7.233 Bestanden
  • cypress-explain cypress-io/ai-toolkit

    Explains Cypress tests (E2E and component tests), and answers questions about Cypress use and behavior. Use when the user asks to explain how a test works, explain how Cypress works, review or critique a test without writing code. Apply even when the user does not say 'Cypress' (e.g. 'explain this test'). Prefer the cypress-author skill when the user wants to create, fix, or update tests.

    7.030 Bestanden
  • asc-testflight-orchestration rorkai/app-store-connect-cli-skills

    Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.

    6.934 Bestanden
  • cold-email-subject-line-tester mbfinotti/sales-skills

    Generates, scores, and split-tests email subject lines, producing angle-distinct variants, a numeric scorecard, and a test plan with sample size and decision metric. Covers B2B cold outbound and B2C lifecycle/promotional email, and flags spam-trigger words inside the subject line only. Use whenever the user mentions a subject line, open rates, email A/B test, preview text, or "nobody opens my emails", even if they don't say "subject line" explicitly. Do NOT use for body copy or inbox-placement audits (mbfinotti/sales-skills@cold-email-deliverability), personalization angles (mbfinotti/sales-skills@sales-outreach-personalization), or cadence design (mbfinotti/sales-skills@sales-outbound-sequence).

    6.810 Bestanden
  • platform-apex-test-generate forcedotcom/sf-skills

    Use to generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking, assertions, and disciplined test-fix loops. Use when creating Apex test classes (for triggers, services, controllers, batch jobs, queueables, and callouts), improving coverage, debugging or fixing failing Apex tests, or running test/coverage analysis. Triggers on *Test.cls files, sf apex run test, coverage reports. Do NOT trigger for production Apex (use platform-apex-generate) or Jest/LWC tests.

    6.611 Bestanden
  • platform-apex-test-run forcedotcom/sf-skills

    Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate).

    6.508 Bestanden
  • platform-apex-logs-debug forcedotcom/sf-skills

    Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use platform-apex-test-run), generating or fixing Apex code (use platform-apex-generate), or Agentforce session tracing (use agentforce-observe).

    6.390 Bestanden
  • fastapi-patterns affaan-m/ecc

    FastAPI best practices covering project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest. Use when building or reviewing FastAPI apps — Pydantic schemas, dependencies, async handlers, auth, or tests.

    6.253 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.