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.
The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory
Once 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.
Reviewed on 2026-04-17 against workflow fit, installation clarity, operator handoff, and repeatable execution value. This page is now positioned as an install-first workflow gateway instead of a generic tooling roundup.
We prioritize this page because workflow-intent users should move from comparison into installation, validation, and team rollout quickly. That recovery path is stronger than keeping them inside another broad repo crawl.
Trust Signals
- Entries are selected because they solve a concrete workflow role such as routing, approvals, handoff, or execution scaffolding.
- Included tools still connect cleanly to operator-facing setup docs, installation paths, or trusted workflow guidance.
- Selection favors repeatable delivery value over generic repository popularity or trend-driven tool lists.
Grouping Logic
- Lead with workflow tools that can turn routing, approvals, handoff, and execution scaffolding into one installable path.
- Keep the shortlist compact enough for fast comparison while still covering orchestration, reusable scaffolds, and operator checkpoints.
- Use installation as the bridge from workflow discovery into validated multi-step execution.
Maintenance & Review
Last Reviewed
2026-04-17
Cadence
Review monthly and whenever a workflow entry changes setup complexity, maintenance ownership, or production positioning.
Maintained By
Killer-Skills editorial review with authority-surface recovery priorities.
Verification
Each entry must still represent a concrete workflow role, remain installable, and connect cleanly to operator-facing docs or setup guidance.
Execution Examples
How These Skills Work Together In Practice
Install one workflow lane before standardizing it
Use this page when you need to shortlist one workflow stack, validate it quickly, and only then roll it out to more contributors or agents.
1. Open the installation docs before evaluating more workflow repositories.
2. Pick one scaffold or orchestration tool that matches the execution path you need now.
3. Install it and verify the CLI write path, handoff behavior, and first checkpoint.
4. Only after the base lane works, standardize it across the team.
Approval-gated automation loop
Pair automation builders with approval-aware tooling when a workflow can trigger external actions, publishing, or destructive changes.
1. Use an automation builder to connect triggers, data, and downstream actions.
2. Insert a review or approval gate before irreversible changes happen.
3. Document the validation path so operators know what to confirm after each run.
Context-rich handoff between tools
A workflow stack is most useful when handoffs preserve project state, not just payload text.
1. Define which tool owns planning, which tool executes, and which step verifies outputs.
2. Keep shared context in docs, prompts, or memory artifacts that survive handoff.
3. Send users into installation or CLI docs when the next step requires concrete environment setup.
The component-refactoring skill simplifies high-complexity React components, improving code quality and reducing maintenance efforts for developers. It utilizes patterns and workflows to refactor components, making them more efficient and easier to understand.
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
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.
The create-skill AI agent skill automates workflows and integrates APIs for Claude Code, enhancing developer productivity. It teaches the agent focused workflows, leveraging markdown and optional scripts.
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
Write or update documentation for the Inkeep docs site (agents-docs package). Use when: creating new docs, modifying existing docs, introducing features that need documentation, touching MDX files in agents-docs/content/. Triggers on: docs, documentation, MDX, agents-docs, write docs, update docs, add page, new tutorial, API reference, integration guide.
If This Page Is Close, Keep Narrowing With Adjacent Authority Pages
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.
Use These Additional Paths If You Need One More Step To Narrow The Decision
These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.
