pipeline-optimizersolid

Structured 6-step procedure for improving, renovating, or rebuilding existing pipelines, individual project folders, documentation structures, or software stacks. Addressable as "pipeline optimizer" (for whole topic pipelines, e.g. a software, research, or game-dev pipeline) or "project-folder optimizer" (for individual project folders within a pipeline, e.g. a single software tool or paper project). Triggers on tasks like "improve pipeline X", "optimize the stack", "rebuild Y", "renovation", "pipeline refactoring", "clean up project folder", "improve folder structure", "unify conventions", "documentation consolidation", "integrate into existing system", or any substantial intervention in established structures. Delivers building-stock analysis, purpose clarification, ideal sketch, gap plan, empirical pain-point identification, and retests with fresh subagents. Prevents parallel standards, duplication, and pipeline breaks.
ellmos-ai/skills · ★ 6 · AI & Automation · score 84

Install: claude install-skill ellmos-ai/skills

> **Deutsch** — Offizielle Deutsch-Version / Documento Oficial en Deutsch. # Pipeline Optimizer / Project-Folder Optimizer (Deutsch) **6-step renovation without incompatibilities** — applicable at two scales: | Trigger name | Scope | Example | |---|---|---| | **Pipeline optimizer** | Whole pipelines, stacks, documentation structures | Your topic pipelines, e.g. `software/`, `research/`, `games/`, an agent system | | **Project-folder optimizer** | Individual project folders within a pipeline | A software tool, a paper project, a game project | A **pipeline** here means a topic-oriented top-level structure in which multiple projects live under shared conventions (e.g. a software pipeline with release rules, a research pipeline with a publication procedure). Both use the same 6-step workflow — the only difference is the **scope** (pipeline-wide vs. single project) and, accordingly, the depth of the building-stock survey in step A. ## When this skill applies The skill applies as soon as you are asked to improve, rebuild, or extend an **existing** structure — not for greenfield construction. Concrete triggers: **Pipeline level** (scope: whole pipeline): - "Make pipeline X better" - "Optimize the stack" - "Renovate the software pipeline" - "Documentation consolidation in the research pipeline" - Substantial intervention in a topic pipeline, central `_tools/`, or system components **Project-folder level** (scope: single project folder): - "Clean up / optimize project folde