Collection gemini

Gemini Workflow Tools for Coding and Review Teams

A practical Gemini shortlist for coding support, review loops, rules sync, and safer rollout decisions.

Gemini teams usually want fewer tools, not more. They need something they can test around coding, review, policy sync, or release control without turning the stack into another compatibility project. This collection keeps the shortlist focused on tools a team can trial quickly and keep if they improve daily execution.

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 with monthly collection checks.

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

Start with the install guide so the first Gemini tool trial has a concrete setup path.

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 for setup clarity, maintainer reliability, review coverage, and rollout readiness. We kept the tools that help Gemini teams move from experiments to dependable delivery habits.

People landing here usually already know they are building around Gemini. What they need next is a smaller list tied to coding, review, policy sync, and rollout control.

Trust Signals

- Each entry strengthens a concrete Gemini workflow such as coding support, review, rules sync, or repeatable rollout.
- We keep tools with public setup docs, visible maintenance, and a clear first-use path.
- Preference goes to tools teams can test in one active project before wider rollout.

Grouping Logic

- Start with the tool that removes the first source of workflow drift around Gemini.
- Keep the list compact while still covering coding, review, rules sync, and automation support.
- Move the next click into install docs, CLI behavior, and a concrete rollout checklist.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or Gemini workflow relevance changes upstream; otherwise review monthly.
Maintained By: Killer-Skills editorial review with monthly collection checks.
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

Pick one Gemini tool for coding or review

Start here when the team already works with Gemini and needs one extra layer for coding support, review loops, or safer operator handoff.

1. Decide whether the first need is coding support, review, rules sync, or rollout control.
2. Open the install docs for the tool that best matches that need.
3. Verify what the CLI writes, how it fits the current workflow, and what the operator must review after setup.
4. Expand only after one active project proves the setup is worth keeping.

Reduce workflow drift around Gemini

Use the collection as a filter when different teammates are starting to use Gemini with inconsistent rules, review habits, or rollout steps.

1. Check maintainer activity and public setup guidance before adding any new tool.
2. Prefer the tool that reduces ambiguity for operators instead of the tool with the largest feature set.
3. Pilot in one active workflow, then document the rules for the rest of the team.
4. Revisit the shortlist only after the first baseline is stable.

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 which operator checks matter after setup.

Step 3

Step 3: Cross-check with trusted tools

After the first workflow trial succeeds, compare it with the trusted starter collection before standardizing.

orpc-contract-first

[ Featured ]

langgenius

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

★ 132.2k

⑂ 0

db-migrations

lobehub

db-migrations is a skill for automating database migrations using AI agents, enabling multi-agent collaboration and effortless workflow design.

★ 74.2k

⑂ 0

sync-readme

lbb00

sync-readme is a skill that synchronizes and translates English and Chinese README files, ensuring consistency across languages.

★ 17

⑂ 0

widget-generator

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k

⑂ 0

Adjacent Curated Collections

If This Page Is Close, Keep Narrowing With Adjacent Curated 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.

P1 collection

OpenCode Workflow Tools to Install First

A focused OpenCode collection that shortens companion-tool selection before installation and rollout.

OpenCode-intent users need a tighter curated bridge than a broad integrations list can provide.

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

Agent Framework Tools to Install First

A framework and SDK collection for teams building agent foundations, not just browsing vendor names.

Framework intent strengthens the site's product judgment and reduces the mirror-site posture.

P1 collection

Next.js Workflow Tools to Install First

A full-stack workflow collection for Next.js teams that need a faster path from evaluation into install and rollout.

Framework-specific collections create stronger topical authority than broad developer-tool roundups.

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.

What should I do after I open a collection?

Use the collection to shortlist tools, then open the installation docs before browsing more repositories. That is the fastest path to install and validate a real setup.

Which collection should I open first if I want lower-risk tools?

Start with the official and trusted tools collection. It concentrates first-party and well-established ecosystem tools before you branch into broader workflow bundles.

Can I install skills from a collection in Claude Code or Cursor?

Yes. Choose a skill from the collection, open the install guide, and run `npx killer-skills add owner/repo`. The CLI handles the native file format for supported IDEs.

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.

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.

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.