コレクション gemini-cli

Gemini CLI向けワークフローツール＆ターミナル自動化スキル | AI Agent Skills

Claude Code・Cursor・Windsurf 向けの gemini cli terminal automation AI Agent Skills 集合。開発者ワークフロー自動化を重視します。

ターミナル中心で開発するチーム向けに、このGemini CLIコレクションは実務的なワークフロー部品を提供します。再利用可能なCLIスキル、連携パターン、自動化ヘルパーに焦点を当て、コーディング作業、リリース確認、チームスクリプト運用を支援。必要に応じてMCP対応も含みますが、主目的はCLI開発の生産性と信頼性向上です。

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

開発者

wrap

mag123c

Ultra-fast token & cost tracker for LLM Token Usage (e.g. Claude Code)

★ 60

⑂ 0

開発者

ai-development-guide

shinpr

Detects code smells, anti-patterns, and debugging issues. Use when: fixing bugs, reviewing code quality, or refactoring.

★ 34

⑂ 0

生産性

documentation-criteria

shinpr

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

★ 35

⑂ 0

生産性

testing

shinpr

Applies TDD process, test quality criteria, and mock guidelines. Use when: writing unit tests, using mocks, or reviewing test quality.

★ 0

⑂ 0

開発者

review-design

janekbaraniewski

Review a design doc against the codebase

★ 8

⑂ 0

Related Authority Collections

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.

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.

これらのコレクションはどのワークフロー向けですか？

ワークフロー自動化、プロセス自動化、ドキュメント操作、データワークフロー、再利用可能なスキルスタックを中心に構成されています。

コレクションとメインスキルディレクトリの違いは？

スキルディレクトリは直接検索やフィルタリングに適し、コレクションは完全なワークフロー向けの補完的スキルをまとめて見つけるのに適しています。

これらのコレクションをClaude CodeやCursorにインストールできますか？

はい。コレクション内のスキルは通常、Claude Code、Cursor、Windsurf、その他の対応環境で統一インストールフローにより動作します。

Additional Recovery 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.