Sammlung cli

12 KI-Agent-Tools für CLI und Terminal | AI Agent Skills

Installierbare AI Agent Skills für cli terminal Developer Workflows in Claude Code, Cursor und Windsurf.

Diese Sammlung zeigt KI-Agent-Tools, die sich wirklich für die Arbeit im Terminal eignen. Im Fokus stehen praktische Entwickler-Workflows: wiederkehrende Schritte automatisieren, Agent-Pipelines ausführen, Daten- oder Schema-Aufgaben bearbeiten und die tägliche Entwicklung beschleunigen. Einige Projekte unterstützen MCP oder andere Integrationen, doch der Kernnutzen liegt in Produktivität über die Kommandozeile und verlässlicher Ausführung. Für Teams mit terminalzentriertem Workflow ist das eine solide Ausgangsbasis.

Page-Level Review Standard

This Page Is a Curated Decision Surface, Not Just a Themed List

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.

Reviewed On

2026-04-17

Maintained By

Killer-Skills editorial review within the recovery-focused authority queue.

Verification

Validate installability, shell fit, operator clarity, and maintainer trust before retaining or adding an entry.

Primary Audience

High-intent users who roughly know the direction and need a faster path to an installable shortlist.

Three Minimum Standards For This Collection

- A collection page must narrow users into a better shortlist instead of flattening more repositories onto the screen.
- The next click should continue into installation docs, CLI validation, or a better-fit solution page instead of resetting back to a broad directory.
- This page only becomes a real first-party judgment surface when its selection logic, maintenance posture, and delivery path are all visible.

Primary Install Bridge

Pick One Skill, Then Take the Install Path

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.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from CLI and terminal workflow discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path

Best-Fit Next Paths

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.

P1 solution

Process Automation Solution

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.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against CLI-native workflow fit, installation clarity, operator handoff, and terminal-first execution value. This page is now positioned as an install-first terminal workflow entry point instead of a generic AI tools list.

We prioritize this page because terminal-intent users usually need a shortlist they can install and validate without leaving the shell for another round of vague tooling research.

Trust Signals

- Entries are chosen for terminal-native execution value such as command-line automation, shell workflows, and operator-friendly validation steps.
- Selection favors tools with public documentation and clear setup paths that teams can verify before standardizing a terminal stack.
- The page is curated for repeatable terminal operations, not for broad AI tooling adjacency or repository popularity alone.

Grouping Logic

- Lead with tools that can enter a terminal-first workflow without pulling teams back into heavy GUI setup ambiguity.
- Keep the shortlist compact enough for fast comparison while still covering command execution, automation, and operator handoff.
- Use installation as the bridge from terminal discovery into validated day-to-day execution.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or terminal workflow relevance changes upstream; otherwise review monthly.
Maintained By: Killer-Skills editorial review within the recovery-focused authority queue.
Verification: Validate installability, shell fit, operator clarity, and maintainer trust before retaining or adding an entry.

Execution Examples

How These Skills Work Together In Practice

Install one terminal-first companion before standardizing the shell workflow

Use this page when you want one CLI companion that can enter real terminal work immediately instead of turning evaluation into another tooling spiral.

1. Open the installation docs before opening more CLI-related repositories.
2. Choose one tool that best supports command execution, terminal automation, or operator handoff.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider shell workflow.

Keep the team inside the terminal

Treat the collection as an editorial filter when you need terminal-first tools that speed up delivery without forcing a context switch into another UI stack.

1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated terminal path before scaling it to more repos or more teammates.
4. Document the chosen terminal baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check CLI tooling choices before you standardize a terminal-first stack.

spec-driven-development

n8n-io

Die spezifikationsgetriebene Entwicklung ermöglicht eine effizientere Integration von APIs und Datenflüssen

★ 181.1k

⑂ 0

Künstliche Intelligenz

formax-script-output-placement-workflow

yusifeng

Use when adding or modifying generator scripts that write files; keeps generated artifacts out of docs/ and aligns script defaults with ownership paths plus CI gate updates.

★ 7

⑂ 0

Künstliche Intelligenz

mag123c

Session start - check progress, suggest next task

★ 55

⑂ 0

Entwickler

fix_bug

pgplex

Fix a bug from a GitHub issue using TDD. Analyzes the issue, creates a reproducing test case, implements the fix, verifies it, runs refactor-pass, and creates a PR.

★ 808

⑂ 0

Entwickler

elixir-cyclic-deps

matteing

🔮 A smol coding agent in Elixir

★ 33

⑂ 0

Künstliche Intelligenz

openspec-explore

tatargabor

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

★ 9

⑂ 0

Entwickler

i18n

aicodingstack

Internationalization management tool for syncing and translating language files

★ 28

⑂ 0

Künstliche Intelligenz

Related Authority Collections

If This Page Is Close, Keep Narrowing With Related Authority Collections

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.

P0 collection

Official AI Skills & Trusted Tools

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.

P0 collection

Agent Workflow Building Tools

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.

P1 collection

Top Claude Code Skills

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.

P1 collection

Cursor-Compatible Skills

A clean surface for editor-specific demand with explicit workflow intent.

Editor-specific demand should land on curated surfaces, not random repo coverage.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

Für welche Workflows sind diese Sammlungen gedacht?

Diese Sammlungen sind rund um Workflow-Automatisierung, Prozessautomatisierung, Dokumentenoperationen, Datenworkflows und wiederverwendbare Skill-Stacks aufgebaut.

Was unterscheidet eine Sammlung vom Hauptverzeichnis?

Das Verzeichnis eignet sich besser für direkte Suche, während Sammlungen komplementäre Skills um einen vollständigen Workflow bündeln.

Kann ich diese Sammlungen für Claude Code oder Cursor installieren?

Ja. Die Skills in diesen Sammlungen funktionieren in der Regel in Claude Code, Cursor, Windsurf und anderen unterstützten Umgebungen über einen einheitlichen Installationsablauf.

Additional Next Paths

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.

P1 guide

How to Install AI Agent Skills

A practical onboarding guide that bridges high-intent discovery into CLI and docs without forcing repository-level browsing first.

Installation intent is one of the site's clearest forms of first-party utility.

P1 solution

Workflow Automation Solution

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.