Sammlung codex

Codex-Workflow-Skills und Entwickler-Integrationen | AI Agent Skills

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

Für Codex/OpenAI-Nutzer konzipiert, priorisiert diese Sammlung verlässliche Engineering-Workflows statt generischer Listen. Sie bietet wiederverwendbare Skills, integrierbare Komponenten und Automationshelfer für Review-Zyklen, Quality-Gates und Delivery-Prozesse. MCP-Optionen sind möglich, im Mittelpunkt stehen jedoch praktische Coding-Abläufe.

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 trial is concrete instead of another round of browsing.

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, repo review coverage, and handoff readiness. We kept the tools that help Codex operators move from first install to steady daily use.

Most people landing here already know they want to work in Codex. What they need next is a smaller list tied to review, handoff, and terminal execution instead of another broad integrations directory.

Trust Signals

- Each entry solves a concrete Codex job such as repo review, shell safety, handoff, or CLI workflow support.
- We keep tools with public setup docs, visible maintenance, and a clear first-use path.
- Preference goes to tools a team can trial in one repository before adopting more widely.

Grouping Logic

- Start with tools that remove the first bottleneck in a Codex CLI loop instead of the noisiest repository.
- Keep the list small enough to compare quickly while still covering review, handoff, automation, and baseline workflow structure.
- Route the next step toward 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 Codex 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 Codex tool for repo review or handoff

Start here when your team already codes in Codex and needs one extra layer for review, shell safety, or cleaner handoffs.

1. Choose the single gap you need to close first: repo review, shell safety, handoff, or workflow scaffolding.
2. Open the install docs for the tool that best matches that gap.
3. Verify what the CLI writes, how sync behaves, and what an operator must check after the first run.
4. If the tool works cleanly in one repo, document the baseline before rolling it out more widely.

Stabilize a Codex CLI baseline

Use this collection when different operators are starting to drift and you need one documented way to review, sync, and hand off work in Codex.

1. Check maintainer activity and public setup guidance before adding any new tool.
2. Prefer the tool that reduces operator ambiguity rather than the one with the longest feature list.
3. Pilot the workflow in one active repo, then capture the handoff rules for the rest of the team.
4. Revisit the shortlist only after the first baseline is working.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Check what the CLI writes, what it syncs, and which checkpoints an operator should verify after setup.

Step 3

Step 3: Cross-check with trusted tools

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

documentation-criteria

shinpr

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

★ 35

⑂ 0

Produktivität

sync-readme

lbb00

Sync README ist eine Fähigkeit von KI-Agents, die README-Dokumente synchronisiert und übersetzt.

★ 17

⑂ 0

Künstliche Intelligenz

agent-gossip-coordinator

ruvnet

Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator

★ 16.7k

⑂ 0

Künstliche Intelligenz

review-design

janekbaraniewski

Review a design doc against the codebase

★ 8

⑂ 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.

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.