Installierbare AI Agent Skills für automation Developer Workflows in Claude Code, Cursor und Windsurf.
Diese Seite konzentriert sich auf praxistaugliche Workflow-Automatisierung für echte Engineering-Teams. Die Tools helfen KI-Agenten und Entwicklern, wiederkehrende Schritte zu automatisieren, Services zu verbinden und vom Prototyp bis zur Produktion konsistent auszuführen. MCP kann als Integrationsschicht dienen, im Mittelpunkt stehen jedoch verlässliche Entwickler-Workflows.
A collection page should not just add more cards to the screen. It should explain why these skills belong together, how the next step moves into installation and validation, and which path should continue the decision afterwards.
This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.
Move from automation-tool comparison into the install flow, validation checklist, and first command path before expanding further.
Open the Install PathOnce the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.
A use-case page for users searching for repeatable automation patterns instead of one-off tools.
Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.
A solution page for teams turning SOPs, handoffs, and operations into repeatable AI-assisted execution paths.
Operational intent deserves a stronger bridge than generic tooling lists can provide.
Reviewed on 2026-04-17 against workflow automation fit, install clarity, operator handoff, and production usefulness. This page now acts as an installation-first gateway instead of a generic automation list.
We prioritize this page because automation-intent users should move quickly from comparison into installation and validation. That path is stronger for recovery than trapping them in broad tooling research.
Use this page when you need one automation toolchain that can move from prototype into repeatable team execution.
Use the collection as an editorial filter when you need automation tools that can be rolled out without excessive operator ambiguity.
Confirm what the CLI writes and how sync behaves after the install path is clear.
Use the workflow solution page after installation to decide how the automation tool should fit into the delivery system.
Guide for implementing oRPC contract-first API patterns in Dify frontend. Trigger when creating or updating contracts in web/contract, wiring router composition, integrating TanStack Query with typed contracts, migrating legacy service calls to oRPC, or deciding whether to call queryOptions directly vs extracting a helper or use-* hook in web/service.
Die spezifikationsgetriebene Entwicklung ermöglicht eine effizientere Integration von APIs und Datenflüssen
Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.
Sync scripts to SuperOps - commits changes and pushes to SuperOps platform
Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.
A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.
Trusted-brand collections are the fastest way to rebuild authority after pruning.
A workflow-first collection that explains why related skills belong together and what job they solve.
Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.
A platform-specific collection for one of the clearest demand clusters in the product ecosystem.
Platform collections let the site recover with narrower, more trustworthy topical intent.
A clean surface for editor-specific demand with explicit workflow intent.
Editor-specific demand should land on curated surfaces, not random repo coverage.
This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.
Diese Sammlungen sind rund um Workflow-Automatisierung, Prozessautomatisierung, Dokumentenoperationen, Datenworkflows und wiederverwendbare Skill-Stacks aufgebaut.
Das Verzeichnis eignet sich besser für direkte Suche, während Sammlungen komplementäre Skills um einen vollständigen Workflow bündeln.
Ja. Die Skills in diesen Sammlungen funktionieren in der Regel in Claude Code, Cursor, Windsurf und anderen unterstützten Umgebungen über einen einheitlichen Installationsablauf.
These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.
A workflow-first collection that explains why related skills belong together and what job they solve.
Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.
A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.
Trusted-brand collections are the fastest way to rebuild authority after pruning.