Sammlungen
Sammlung gemini-cli

Gemini CLI Workflow-Tools und Terminal-Automation-Skills | AI Agent Skills

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

Für Teams mit terminalnativer Arbeitsweise bietet diese Gemini-CLI-Sammlung praktische Workflow-Bausteine. Sie zeigt wiederverwendbare Kommandozeilen-Skills, Integrationsmuster und Automationshelfer für Coding-Aufgaben, Release-Checks und Team-Skripte. MCP kann enthalten sein, wenn nötig, der Kern ist jedoch bessere Produktivität und Zuverlässigkeit im CLI-Workflow.

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 related page to open afterwards.

Reviewed On
2026-04-17
Maintained By
Maintained through Killer-Skills curation review with install, documentation, and Gemini CLI workflow checks.
Verification
Validate installability, setup clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Primary Audience
People 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 collection page works best when its selection logic, maintenance notes, and next steps are all clear.
Recommended Install Path

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 the next practical step. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

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

Open the Install Path
Recommended Next Steps

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution page, CLI docs, or the next collection that best matches this theme. That keeps platform, framework, and operations needs easier to compare and verify.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against terminal workflow fit, installation clarity, team adoption, and day-to-day CLI usefulness. This page is now positioned as an installation-focused Gemini CLI entry point instead of a broad terminal-tools list.

We prioritize this page because Gemini CLI users usually need one shortlist they can install, validate, and connect to real terminal-native workflows quickly.

Trust Signals

  • - Entries are chosen for practical Gemini CLI workflow value such as scripting, release checks, automation, and terminal-native execution.
  • - Selection favors tools with public docs and clear setup paths that teams can validate before wider rollout.
  • - The page is curated for repeatable CLI operations, not broad terminal-keyword traffic capture.

Grouping Logic

  • - Lead with tools that can enter a Gemini CLI workflow without adding heavy setup ambiguity.
  • - Keep the shortlist compact enough for quick comparison while still covering scripting, release checks, automation, and terminal execution.
  • - Use installation as the bridge from Gemini CLI discovery into validated daily execution.

Maintenance & Review

Last Reviewed
2026-04-17
Cadence
Re-check when install flow, maintainer posture, or Gemini CLI workflow relevance changes upstream; otherwise review monthly.
Maintained By
Maintained through Killer-Skills curation review with install, documentation, and Gemini CLI workflow checks.
Verification
Validate installability, setup clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Execution Examples

How These Skills Work Together In Practice

Validate one terminal workflow first

Use this page when you need one Gemini CLI-adjacent toolchain that can move from command-line experimentation into real coding and release work.

  1. 1. Open the installation docs before opening more Gemini CLI-related repositories.
  2. 2. Choose one tool that best supports scripting, release checks, automation, or terminal execution.
  3. 3. Install it and verify the CLI write path, sync behavior, and first key validation step.
  4. 4. Only after the base path works, expand the setup across the wider team workflow.

Standardize CLI release checks

Use this collection when you need Gemini CLI-adjacent tools that improve terminal reliability without overcomplicating the stack.

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

Supporting Moves After The Install Path Is Clear

next

Logo of mag123c
mag123c

Session start - check progress, suggest next task

55
0
Entwickler

documentation-criteria

Logo of shinpr
shinpr

Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.

35
0
Produktivität

review-design

Logo of janekbaraniewski
janekbaraniewski

Review a design doc against the codebase

Related Collections

If This Page Is Close, Keep Narrowing With Related Collections

Do not reset back to the generic directory. Move sideways through these adjacent collections to narrow the shortlist toward the install path that best matches your team.

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.