Colección gemini-cli

Herramientas de workflow y automatización terminal para Gemini CLI | AI Agent Skills

Colección de AI Agent Skills instalables para workflows de desarrollo de gemini cli terminal automation en Claude Code, Cursor y Windsurf.

Para equipos que trabajan de forma nativa en terminal, esta colección de Gemini CLI aporta bloques prácticos de workflow. Reúne skills reutilizables de línea de comandos, patrones de integración y helpers de automatización para tareas de código, checks de release y scripts de equipo. MCP puede aparecer cuando sea útil, pero el objetivo central es mejorar productividad y confiabilidad en workflows basados en CLI.

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, operator clarity, workflow fit, 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 Gemini CLI 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

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.

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.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against terminal workflow fit, installation clarity, operator handoff, and day-to-day CLI usefulness. This page is now positioned as an install-first 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: Killer-Skills editorial review within the recovery-focused authority queue.
Verification: Validate installability, operator 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. Open the installation docs before opening more Gemini CLI-related repositories.
2. Choose one tool that best supports scripting, release checks, automation, or terminal execution.
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 team workflow.

Standardize CLI release checks

Treat the collection as an editorial filter when you need Gemini CLI-adjacent tools that improve terminal reliability without overcomplicating the 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 path before scaling it to more projects or more teammates.
4. Document the chosen Gemini CLI workflow 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 tool choices before you standardize a team stack.

mag123c

Session start - check progress, suggest next task

★ 55

⑂ 0

Desarrollador

documentation-criteria

shinpr

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

★ 35

⑂ 0

Productividad

review-design

janekbaraniewski

Review a design doc against the codebase

★ 8

⑂ 0

Inteligencia Artificial

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.

¿Para qué flujos de trabajo están diseñadas estas colecciones?

Estas colecciones están diseñadas para automatización de flujos, procesos, documentos, datos y pilas de habilidades reutilizables.

¿Cómo se diferencia una colección del directorio principal?

El directorio es mejor para búsqueda directa, mientras las colecciones ayudan a encontrar habilidades complementarias agrupadas por flujo completo.

¿Puedo instalar estas colecciones para Claude Code o Cursor?

Sí. Las habilidades de estas colecciones generalmente funcionan en Claude Code, Cursor, Windsurf y otros entornos mediante instalación unificada.

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.

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.

P2 comparison

Claude Code vs Cursor vs Windsurf

Comparison pages are one of the best ways to prove independent judgment and avoid the mirror-site posture.

Comparisons make Killer-Skills look editorial-first instead of repo-wrapper-first.