@mmerterden/multi-agent-pipeline 12.6.0 → 12.8.0

package/pipeline/skills/shared/external/backlog/SKILL.md

@@ -7,11 +7,11 @@ argument-hint: [list | add | pick <id> | done <id>]
 allowed-tools: Read, Grep, Glob, Edit, Write
 ---
 
-# backlog — deferred work, kept whole
+# backlog - deferred work, kept whole
 
-> **Layer:** workflow — the deterministic registry routine for deferred jobs.
-> **Bundled:** [BACKLOG.md](BACKLOG.md) — the registry. The heart of this skill.
-> **Iron rule:** moving a job onto this list is a MOVE, never a rewrite — the FULL spec
+> **Layer:** workflow - the deterministic registry routine for deferred jobs.
+> **Bundled:** [BACKLOG.md](BACKLOG.md) - the registry. The heart of this skill.
+> **Iron rule:** moving a job onto this list is a MOVE, never a rewrite - the FULL spec
 > travels verbatim. A compressed one-liner is a loss; the point of the backlog is that
 > deferring costs nothing later.
 
@@ -26,14 +26,14 @@ allowed-tools: Read, Grep, Glob, Edit, Write
 
 Every entry in `BACKLOG.md` carries, verbatim:
 
-- **id** — short stable slug (`kebab-case`), assigned on add.
-- **title** — one line.
-- **state** — `deferred` -> `ready` -> `in-progress` -> `done`. Entries only move forward; nothing is deleted.
-- **origin** — where it came from (the task/PR/finding/conversation that spawned it).
-- **spec** — the FULL description, verbatim from when it was deferred. Not a summary.
-- **unblock** — the condition that makes it actionable (a dependency, a decision, a date). `deferred` items without an unblock condition are just `ready`.
+- **id** - short stable slug (`kebab-case`), assigned on add.
+- **title** - one line.
+- **state** - `deferred` -> `ready` -> `in-progress` -> `done`. Entries only move forward; nothing is deleted.
+- **origin** - where it came from (the task/PR/finding/conversation that spawned it).
+- **spec** - the FULL description, verbatim from when it was deferred. Not a summary.
+- **unblock** - the condition that makes it actionable (a dependency, a decision, a date). `deferred` items without an unblock condition are just `ready`.
 
-Prefer an append-only markdown table or section list in `BACKLOG.md`; never overwrite an entry's spec on a state change — only its `state` line moves.
+Prefer an append-only markdown table or section list in `BACKLOG.md`; never overwrite an entry's spec on a state change - only its `state` line moves.
 
 ## Operations
 
@@ -46,4 +46,4 @@ Prefer an append-only markdown table or section list in `BACKLOG.md`; never over
 
 ## Why keep it whole
 
-The failure mode this skill prevents: an agent defers a job with a one-line note, the surrounding context evaporates, and picking it up later means re-deriving the spec (or silently dropping it). Storing the full spec at defer-time makes deferral safe — the cost of "later" is paid once, up front, not lost.
+The failure mode this skill prevents: an agent defers a job with a one-line note, the surrounding context evaporates, and picking it up later means re-deriving the spec (or silently dropping it). Storing the full spec at defer-time makes deferral safe - the cost of "later" is paid once, up front, not lost.

package/pipeline/skills/shared/external/ci-cd-pipelines/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ci-cd-pipelines
-description: "CI/CD pipelines: GitHub Actions workflows, Docker multi-stage builds, environment management, secret management, deployment strategies"
+description: "CI/CD pipelines: GitHub Actions workflows, Docker multi-stage builds, environment management, secret management, deployment strategies. Use when setting up or fixing a build, test or deploy pipeline."
 tags: [ci-cd, github-actions, docker, deployment, devops, backend]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/context-compression/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: context-compression
-description: "When agent sessions generate millions of tokens of conversation history, compression becomes mandatory. The naive approach is aggressive compression to minimize tokens per request."
+description: "When agent sessions generate millions of tokens of conversation history, compression becomes mandatory. The naive approach is aggressive compression to minimize tokens per request. Use when an agent session has grown too long to keep in full and history has to be compressed."
 risk: unknown
 source: community
 ---

package/pipeline/skills/shared/external/council/SKILL.md

@@ -45,11 +45,11 @@ Run each as a distinct perspective (in-context, or as parallel sub-agents when
 the decision is high-stakes). Give each the same framing and ask for its
 strongest honest position, not a hedge.
 
-- **Skeptic** — attacks the leading option. What breaks it, what is being
+- **Skeptic** - attacks the leading option. What breaks it, what is being
   assumed, what is the failure mode nobody is naming?
-- **Pragmatist** — optimizes for shipping and reversibility. What is the
+- **Pragmatist** - optimizes for shipping and reversibility. What is the
   cheapest path that keeps options open? What is good-enough now?
-- **Critic** — optimizes for long-term cost and coherence. What does this choice
+- **Critic** - optimizes for long-term cost and coherence. What does this choice
   lock in? What is the second-order effect in six months?
 
 Add a fourth domain voice (security, cost, UX) only when the decision hinges on

package/pipeline/skills/shared/external/css-modern/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: css-modern
-description: "Modern CSS: container queries, nesting, @layer, Grid/Flexbox patterns, custom properties, animations, and transitions"
+description: "Modern CSS: container queries, nesting, @layer, Grid/Flexbox patterns, custom properties, animations, and transitions. Use when writing or reviewing modern CSS: layout, container queries, custom properties, animation."
 tags: [css, grid, flexbox, container-queries, nesting, animations, frontend]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/database-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database-patterns
-description: "Database patterns: SQL best practices (PostgreSQL), indexing, query optimization, migrations, schema design, ORMs (SQLAlchemy, Prisma, Drizzle)"
+description: "Database patterns: SQL best practices (PostgreSQL), indexing, query optimization, migrations, schema design, ORMs (SQLAlchemy, Prisma, Drizzle). Use when designing a schema, writing migrations, or a query needs optimising."
 tags: [database, sql, postgresql, prisma, drizzle, sqlalchemy, backend]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/debugging-strategies/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debugging-strategies
-description: "Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches."
+description: "Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches. Use when a bug resists guesswork and needs a systematic approach."
 risk: safe
 source: community
 date_added: "2026-02-27"

package/pipeline/skills/shared/external/docker-expert/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: docker-expert
-description: "You are an advanced Docker containerization expert with comprehensive, practical knowledge of container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies based on current industry best practices."
+description: "You are an advanced Docker containerization expert with comprehensive, practical knowledge of container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies based on current industry best practices. Use when writing or reviewing a Dockerfile, compose setup, or container build."
 category: devops
 risk: unknown
 source: community

package/pipeline/skills/shared/external/fastapi-pro/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fastapi-pro
-description: Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns.
+description: "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use when building or reviewing an async Python API with FastAPI, SQLAlchemy or Pydantic."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/firebase/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: firebase
-description: "You're a developer who has shipped dozens of Firebase projects. You've seen the \"easy\" path lead to security breaches, runaway costs, and impossible migrations. You know Firebase is powerful, but you also know its sharp edges."
+description: "You're a developer who has shipped dozens of Firebase projects. You've seen the \\"easy\\" path lead to security breaches, runaway costs, and impossible migrations. You know Firebase is powerful, but you also know its sharp edges. Use when integrating or reviewing Firebase: auth, Firestore, functions, or its cost and scaling traps."
 risk: unknown
 source: "vibeship-spawner-skills (Apache 2.0)"
 date_added: "2026-02-27"

package/pipeline/skills/shared/external/github-actions-templates/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: github-actions-templates
-description: "Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications."
+description: "Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications. Use when a GitHub Actions workflow has to be written or hardened."
 risk: critical
 source: community
 date_added: "2026-02-27"

package/pipeline/skills/shared/external/help-skills/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: help-skills
-description: Mevcut tum iOS/Swift skill'lerini listeler ve ne ise yaradiklarini aciklar.
+description: "Mevcut tum iOS/Swift skill'lerini listeler ve ne ise yaradiklarini aciklar. Use when asked which iOS or Swift skills are available and what each one covers."
 risk: safe
 ---
 

package/pipeline/skills/shared/external/hig-components-content/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-components-content
-description: Apple Human Interface Guidelines for content display components.
+description: "Apple Human Interface Guidelines for content display components. Use when designing or reviewing how content is displayed on an Apple platform."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-components-layout/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-components-layout
-description: Apple Human Interface Guidelines for layout and navigation components.
+description: "Apple Human Interface Guidelines for layout and navigation components. Use when designing or reviewing layout and navigation on an Apple platform."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-components-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-components-status
-description: Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.
+description: "Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use when designing or reviewing progress, status or feedback UI on an Apple platform."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-components-system/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-components-system
-description: 'Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts.'
+description: 'Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when designing or reviewing widgets, Live Activities or notifications on an Apple platform.'
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-foundations/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-foundations
-description: Apple Human Interface Guidelines design foundations.
+description: "Apple Human Interface Guidelines design foundations. Use when a design decision turns on Apple's foundations: layout, typography, colour, motion, accessibility."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-inputs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-inputs
-description: "Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered."
+description: "Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered. Use when designing or reviewing input controls, forms or text entry on an Apple platform."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-patterns
-description: Apple Human Interface Guidelines interaction and UX patterns.
+description: "Apple Human Interface Guidelines interaction and UX patterns. Use when an interaction or UX pattern on an Apple platform needs designing or reviewing."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-platforms/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-platforms
-description: Apple Human Interface Guidelines for platform-specific design.
+description: "Apple Human Interface Guidelines for platform-specific design. Use when a design has to fit a specific Apple platform's conventions."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/hig-technologies/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-technologies
-description: "Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered."
+description: "Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered. Use when designing or reviewing a feature built on an Apple technology such as Sign in with Apple, Wallet or Maps."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/html-semantic/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: html-semantic
-description: "Semantic HTML5: elements, forms with validation and accessibility, SEO best practices, structured data, Open Graph, Twitter Cards"
+description: "Semantic HTML5: elements, forms with validation and accessibility, SEO best practices, structured data, Open Graph, Twitter Cards. Use when writing or reviewing markup, forms or document structure for semantics, accessibility and SEO."
 tags: [html, semantic, seo, forms, open-graph, structured-data, frontend]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/humanizer/SKILL.md

@@ -41,7 +41,7 @@ AI sprinkles friendly/emotive emoji into prose. Strip them.
 | Emotive / smiley emoji | "Done 🎉", "Hi there 🙂", "😊", "👍 looks good" | Remove the emoji, keep the words |
 | Emoji as decoration/bullet | "✨ Feature:", "🚀 Shipped", "🔥 Fast" | Plain text |
 
-Keep ONLY functional status/severity marks that a fixed template explicitly defines (e.g. a `✅/⏳` phase-tick strip, `🔴/🟡` severity labels). Everywhere else in prose — issue/Jira comments, Confluence/Wiki pages, PR bodies, commit messages — carry **no** emoji.
+Keep ONLY functional status/severity marks that a fixed template explicitly defines (e.g. a `✅/⏳` phase-tick strip, `🔴/🟡` severity labels). Everywhere else in prose - issue/Jira comments, Confluence/Wiki pages, PR bodies, commit messages - carry **no** emoji.
 
 ### AI Vocabulary
 

package/pipeline/skills/shared/external/ios-debugger-agent/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ios-debugger-agent
-description: Debug the current iOS project on a booted simulator with XcodeBuildMCP.
+description: "Debug the current iOS project on a booted simulator with XcodeBuildMCP. Use when an iOS bug has to be reproduced and diagnosed on a booted simulator."
 risk: safe
 source: "Dimillian/Skills (MIT)"
 date_added: "2026-03-25"

package/pipeline/skills/shared/external/ios-developer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ios-developer
-description: Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization.
+description: "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization. Use when building or reviewing a native iOS feature in Swift or SwiftUI."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/kotlin-coroutines-expert/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: kotlin-coroutines-expert
-description: "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing."
+description: "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing. Use when writing or reviewing coroutines and Flow, or a concurrency bug needs diagnosing."
 risk: safe
 source: community
 date_added: "2026-02-27"

package/pipeline/skills/shared/external/macos-menubar-tuist-app/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: macos-menubar-tuist-app
-description: Build, refactor, or review SwiftUI macOS menubar apps that use Tuist.
+description: "Build, refactor, or review SwiftUI macOS menubar apps that use Tuist. Use when building, refactoring or reviewing a SwiftUI macOS menubar app that uses Tuist."
 risk: safe
 source: "Dimillian/Skills (MIT)"
 date_added: "2026-03-25"

package/pipeline/skills/shared/external/macos-spm-app-packaging/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: macos-spm-app-packaging
-description: Scaffold, build, sign, and package SwiftPM macOS apps without Xcode projects.
+description: "Scaffold, build, sign, and package SwiftPM macOS apps without Xcode projects. Use when a SwiftPM macOS app has to be built, signed or packaged without an Xcode project."
 risk: safe
 source: "Dimillian/Skills (MIT)"
 date_added: "2026-03-25"

package/pipeline/skills/shared/external/monorepo-architect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: monorepo-architect
-description: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,"
+description: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,. Use when a monorepo's build system, task graph or dependency layout needs designing or fixing."
 risk: safe
 source: community
 date_added: "2026-02-27"

package/pipeline/skills/shared/external/nextjs-app-router/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: nextjs-app-router
-description: "Next.js 15+ App Router: Server/Client Components, Server Actions, data fetching, layouts, middleware, ISR/SSG/SSR, and routing patterns"
+description: "Next.js 15+ App Router: Server/Client Components, Server Actions, data fetching, layouts, middleware, ISR/SSG/SSR, and routing patterns. Use when building or reviewing App Router work: Server Components, Server Actions, data fetching, layouts."
 tags: [nextjs, react, frontend, ssr, app-router, full-stack]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/nodejs-backend-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: nodejs-backend-patterns
-description: "Comprehensive guidance for building scalable, maintainable, and production-ready Node.js backend applications with modern frameworks, architectural patterns, and best practices."
+description: "Comprehensive guidance for building scalable, maintainable, and production-ready Node.js backend applications with modern frameworks, architectural patterns, and best practices. Use when building or reviewing a Node.js service: structure, error handling, configuration, scaling."
 risk: safe
 source: community
 date_added: "2026-02-27"

package/pipeline/skills/shared/external/observability-engineer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: observability-engineer
-description: Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows.
+description: "Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use when metrics, logging, tracing or alerting have to be designed or fixed."
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/pipeline/skills/shared/external/python-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: python-patterns
-description: "Modern Python 3.12+: type hints, dataclasses, Pydantic v2, async/await, context managers, generators, pattern matching"
+description: "Modern Python 3.12+: type hints, dataclasses, Pydantic v2, async/await, context managers, generators, pattern matching. Use when writing or reviewing modern Python: typing, dataclasses, Pydantic, async, generators."
 tags: [python, type-hints, pydantic, asyncio, dataclasses, backend]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/react-best-practices/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: react-best-practices
-description: "React 19+ best practices: Server Components, use() hook, Actions, hooks patterns, state management, and performance optimization"
+description: "React 19+ best practices: Server Components, use() hook, Actions, hooks patterns, state management, and performance optimization. Use when building or reviewing React work: components, hooks, state, Server Components, Actions."
 tags: [react, frontend, javascript, typescript, hooks, state-management]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/rest-api-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: rest-api-design
-description: "REST API design: HTTP methods, status codes, pagination, versioning, rate limiting, caching headers, OpenAPI documentation"
+description: "REST API design: HTTP methods, status codes, pagination, versioning, rate limiting, caching headers, OpenAPI documentation. Use when a REST surface needs designing or reviewing: methods, status codes, pagination, versioning, caching."
 tags: [rest, api, http, openapi, pagination, backend]
 version: "2025.1"
 ---

package/pipeline/skills/shared/external/search-first/SKILL.md

@@ -71,6 +71,6 @@ person does not redo the search.
 ## Anti-patterns
 
 - **Jumping to code** before step 0-4.
-- **Silent skipping** — reporting no prior art when a channel was down or
+- **Silent skipping** - reporting no prior art when a channel was down or
   unchecked.
-- **Dependency reflex** — adding a package for a one-liner the repo already has.
+- **Dependency reflex** - adding a package for a one-liner the repo already has.

package/pipeline/skills/shared/external/skill-creator/SKILL.md

@@ -1,31 +1,31 @@
 ---
 name: skill-creator
 version: 1.0.0
-description: "Author and refine skills for a plugin/toolkit efficiently. Use when creating a new skill, trimming or splitting an existing one, writing a skill's description, or choosing skill vs command vs agent vs CLAUDE.md. Encodes the house rules — lean SKILL.md as an index, progressive disclosure into bundled files, the reference (descriptive) vs workflow (imperative) split, no-prefix naming, and growing a skill from observed failures. Bundles a template, a pre-ship checklist, and good/bad description examples."
+description: "Author and refine skills for a plugin/toolkit efficiently. Use when creating a new skill, trimming or splitting an existing one, writing a skill's description, or choosing skill vs command vs agent vs CLAUDE.md. Encodes the house rules - lean SKILL.md as an index, progressive disclosure into bundled files, the reference (descriptive) vs workflow (imperative) split, no-prefix naming, and growing a skill from observed failures. Bundles a template, a pre-ship checklist, and good/bad description examples."
 user-invocable: true
 argument-hint: [new | trim | description]
 allowed-tools: Read, Write, Edit, Glob
 ---
 
-# skill-creator — how to write skills here
+# skill-creator - how to write skills here
 
 > **Layer:** reference (knowledge)
 > **Use when:** creating/trimming a skill, writing a description, or choosing skill vs command/agent/CLAUDE.md.
 > **Bundled (read on demand):** [template.md](template.md) · [checklist.md](checklist.md) · [examples.md](examples.md) · [label-check.md](label-check.md) · [audit.md](audit.md)
 
 ## 1. Is a skill the right tool?
-- **CLAUDE.md** — broad facts/rules true *every* session.
-- **Skill** — on-demand procedure or knowledge for a recurring task.
-- **Subagent/agent** — needs independent reasoning + its own context/tools.
-- **MCP server** — structured integration with an external system's API.
+- **CLAUDE.md** - broad facts/rules true *every* session.
+- **Skill** - on-demand procedure or knowledge for a recurring task.
+- **Subagent/agent** - needs independent reasoning + its own context/tools.
+- **MCP server** - structured integration with an external system's API.
 
 ## 2. The description is discovery (the 90% lever)
 It's the *only* thing the model sees when deciding to load the skill. **Write it first.** Include **what + when + trigger words + one example trigger**, in third person. (Anthropic's data: vague→specific lifts activation ~20%→50%; adding examples ~72%→90%.) Good/bad pairs in [examples.md](examples.md).
 
 ## 3. Keep it lean (it stays in context every turn once loaded)
-- `SKILL.md` is an **index** — aim for ~1 page, hard cap ~500 lines.
-- Push detail into bundled files **one level deep** (reference, examples, scripts). They cost zero tokens until read; nested-deeper files get partially read — don't nest.
-- A **script executes without its source entering context** — prefer a script over asking the model to regenerate code.
+- `SKILL.md` is an **index** - aim for ~1 page, hard cap ~500 lines.
+- Push detail into bundled files **one level deep** (reference, examples, scripts). They cost zero tokens until read; nested-deeper files get partially read - don't nest.
+- A **script executes without its source entering context** - prefer a script over asking the model to regenerate code.
 - Challenge every line: *"would Claude err without this?"* If no, cut it.
 
 ## 4. Pick the right degree of freedom (= our layers)
@@ -34,9 +34,9 @@ It's the *only* thing the model sees when deciding to load the skill. **Write it
 - **tool skill → thin index over a script/CLI:** lean SKILL.md (when + the run command + sub-commands at a glance), heavy detail in a bundled `reference.md`; the script is the engine (e.g. `tools/figma-utility`).
 
 ## 5. Naming
-No platform prefix — the toolkit name + description already carry it. Reference = aspect noun (`navigation`); workflow = verb-phrase (`branch-and-pr`). Avoid vague/reserved (`helper`, `utils`, `claude-*`). For a name/title/strict-rule label that must carry its **whole intent**, validate it with the fresh-subagent inference test in [label-check.md](label-check.md) before committing.
+No platform prefix - the toolkit name + description already carry it. Reference = aspect noun (`navigation`); workflow = verb-phrase (`branch-and-pr`). Avoid vague/reserved (`helper`, `utils`, `claude-*`). For a name/title/strict-rule label that must carry its **whole intent**, validate it with the fresh-subagent inference test in [label-check.md](label-check.md) before committing.
 
-## 6. Grow it from real usage — don't pre-write
+## 6. Grow it from real usage - don't pre-write
 1. Do the task **without** a skill; note where Claude actually fails.
 2. Write the **minimum** that fixes those gaps.
 3. Watch Claude use it: move reused detail up into SKILL.md, cut detail it ignores, sharpen the description if it didn't trigger.
@@ -44,5 +44,5 @@ No platform prefix — the toolkit name + description already carry it. Referenc
 ## Before shipping
 Start from [template.md](template.md); run [checklist.md](checklist.md). For a new or
 substantially-changed skill that must be trusted, run the **multi-architect audit**
-([audit.md](audit.md)) — a panel of distinct-lens reviewers + synthesis, looped
+([audit.md](audit.md)) - a panel of distinct-lens reviewers + synthesis, looped
 fix → re-audit until no blockers/majors remain.

package/pipeline/skills/shared/external/skill-creator/audit.md

@@ -1,4 +1,4 @@
-# Multi-architect audit — adversarial quality gate for a skill
+# Multi-architect audit - adversarial quality gate for a skill
 
 The [checklist](checklist.md) is the self-review floor. This is the **high-confidence
 gate**: a panel of N independent reviewers, each a *distinct lens*, reads the skill
@@ -6,22 +6,22 @@ against the rubric + ground truth, then a synthesizer dedups and rules. You **lo
 fix → re-audit until it passes** (no blockers/majors). Run it before shipping a new
 or substantially-changed skill, or whenever a skill must be trusted.
 
-Use the [Workflow tool](scripts/audit-panel.js) to fan the panel out — it returns
+Use the [Workflow tool](scripts/audit-panel.js) to fan the panel out - it returns
 `{remaining, clearsBar, verdict}`.
 
 ## The loop (run to convergence)
-1. **Panel** — N agents, one lens each, read-only. Each returns specific findings
+1. **Panel** - N agents, one lens each, read-only. Each returns specific findings
    (severity · file:location · problem · concrete fix). Empty if its lens is clean.
-2. **Synthesize** — dedup overlaps; **drop false positives** (verify each against the
+2. **Synthesize** - dedup overlaps; **drop false positives** (verify each against the
    real files/repo before keeping); classify blocker / major / minor / nit;
    `clearsBar = no blockers and no majors remain`.
-3. **If not clean** — apply the do-now set (blockers + majors + cheap high-value
+3. **If not clean** - apply the do-now set (blockers + majors + cheap high-value
    minors), then run a **fresh** panel (see "Fresh each round") and repeat.
 4. **Stop** when `clearsBar` is true. The later/nit list is optional polish.
 
 ## Rules that make it trustworthy
 - **Fresh panel each round.** After a fix, re-run the panel anew so agents read the
-  *current* files — do not reuse a prior run's cached results (they reflect the old
+  *current* files - do not reuse a prior run's cached results (they reflect the old
   state and will report fixed issues as open / miss regressions).
 - **Verify before keeping.** Every finding must be confirmed against the actual file
   or repo. The synthesizer drops anything it can't reproduce. Prefer findings that
@@ -29,31 +29,31 @@ Use the [Workflow tool](scripts/audit-panel.js) to fan the panel out — it retu
 - **Ground-truth, not vibes.** Give the panel the rubric ([SKILL.md](SKILL.md) +
   [checklist.md](checklist.md)), an exemplar skill, and the real source the skill
   describes (e.g. the iOS repo). Agents read; they don't assume.
-- **Watch for regressions.** A fix can break something — the red-team lens and the
+- **Watch for regressions.** A fix can break something - the red-team lens and the
   fresh re-audit exist to catch it (e.g. a broadened check that now false-positives).
 - **clearsBar gates the merge.** Don't merge with an open blocker/major.
 
-## Lenses — pick the set for the task
+## Lenses - pick the set for the task
 One distinct lens per agent (+ a synthesizer). Two ready-made sets:
 
-**General skill audit** — discovery · leanness · shape/layer · scripts · accuracy-vs-source · domain-correctness · wiring · boundaries · red-team → synthesis.
+**General skill audit** - discovery · leanness · shape/layer · scripts · accuracy-vs-source · domain-correctness · wiring · boundaries · red-team → synthesis.
 
-**Prompt-engineering audit** (when the concern is *prompt quality* — descriptions,
+**Prompt-engineering audit** (when the concern is *prompt quality* - descriptions,
 instructions, triggering):
-1. **description-as-discovery** — what + when + trigger words + example; would it activate on a real task?
-2. **disambiguation** — distinct from siblings; a reader can tell when to pick this vs a neighbor.
-3. **trigger coverage** — the real user phrasings (and synonyms) are covered.
-4. **instruction clarity** — steps are unambiguous, ordered, single-interpretation; no vague directives.
-5. **degrees of freedom / layer fit** — reference=descriptive (no numbered procedure), workflow=spine, tool=thin-index; freedom matches the task.
-6. **progressive disclosure / leanness** — SKILL.md is an index; detail bundled one level deep; no duplication.
-7. **token efficiency** — every line is load-bearing; nothing restates what the model already knows.
-8. **consistency** — terminology, naming, paths, cross-references, examples all agree.
-9. **anti-patterns / misfire** — would the model over-apply it, skip a gate, hallucinate a path, or follow it into a wrong output?
-10. **red-team** — adversarially try to make it not trigger, trigger wrongly, or produce broken output; hunt overclaims (says X, the script doesn't).
+1. **description-as-discovery** - what + when + trigger words + example; would it activate on a real task?
+2. **disambiguation** - distinct from siblings; a reader can tell when to pick this vs a neighbor.
+3. **trigger coverage** - the real user phrasings (and synonyms) are covered.
+4. **instruction clarity** - steps are unambiguous, ordered, single-interpretation; no vague directives.
+5. **degrees of freedom / layer fit** - reference=descriptive (no numbered procedure), workflow=spine, tool=thin-index; freedom matches the task.
+6. **progressive disclosure / leanness** - SKILL.md is an index; detail bundled one level deep; no duplication.
+7. **token efficiency** - every line is load-bearing; nothing restates what the model already knows.
+8. **consistency** - terminology, naming, paths, cross-references, examples all agree.
+9. **anti-patterns / misfire** - would the model over-apply it, skip a gate, hallucinate a path, or follow it into a wrong output?
+10. **red-team** - adversarially try to make it not trigger, trigger wrongly, or produce broken output; hunt overclaims (says X, the script doesn't).
 
 Scale the panel to risk: a quick check is ~3 lenses; a thorough gate is ~10.
 
 ## Scope of fixes per round
 Fix **blockers + majors** always; fold in **cheap, high-value minors** while you're
 in the file. Defer speculative nits and pre-existing/out-of-scope drift to the
-"later" list (and `log()`/note them — don't silently drop coverage).
+"later" list (and `log()`/note them - don't silently drop coverage).

package/pipeline/skills/shared/external/skill-creator/checklist.md

@@ -9,13 +9,13 @@ Run before considering a skill done.
 
 ## Leanness
 - [ ] `SKILL.md` reads like an index, ~1 page (hard cap ~500 lines).
-- [ ] Detail lives in bundled files **one level deep** — no nested-deeper references.
-- [ ] Every line survives "would Claude err without this?" — no over-explaining, no restating what the model knows.
+- [ ] Detail lives in bundled files **one level deep** - no nested-deeper references.
+- [ ] Every line survives "would Claude err without this?" - no over-explaining, no restating what the model knows.
 - [ ] Deterministic code is a **script**, not prose asking the model to regenerate it.
 
 ## Shape
 - [ ] Layer is explicit (reference or workflow) and matches the content.
-- [ ] **Reference** skill has **no numbered procedures** — heuristics + pointers only.
+- [ ] **Reference** skill has **no numbered procedures** - heuristics + pointers only.
 - [ ] **Workflow** skill's numbered steps are **only** the deterministic/irreversible spine, and it has a **verification gate**.
 - [ ] Conventions **point to canonical files** rather than pasting code that will rot.