outofrange-consulting · outofrange-consulting · Jun 19, 2026
diff --git a/plugins/copilot-preset/skills/copilot-preset/SKILL.md b/plugins/copilot-preset/skills/copilot-preset/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: copilot-preset
-description: >-
-  How this OMP workspace is wired to GitHub Copilot models. Use when the user
-  asks which model is running, how to switch Copilot models, about AI-credit /
-  token billing, which model is cheapest, MAI-Code-1-Flash ("MIA Coding"), or
-  how to run the dev-team cheaply on their Copilot license.
+description: "How this OMP workspace is wired to GitHub Copilot models. Use when the user asks which model is running, how to switch Copilot models, about AI-credit/token billing, which model is cheapest, MAI-Code-1-Flash (\"MIA Coding\"), or how to run the dev-team cheaply on their Copilot license."
 ---
 
 # GitHub Copilot model preset

diff --git a/plugins/dev-team/skills/add-plugin/SKILL.md b/plugins/dev-team/skills/add-plugin/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: add-plugin
-description: >-
-  Install a Oh-My-Pi (OMP) plugin and register it in settings.json so the
-  full team can replicate the install. Use this whenever adding a new
-  plugin to the project — it keeps settings.json in sync with what is
-  actually installed.
+description: "Install an Oh-My-Pi (OMP) plugin and register it in settings.json so the team can replicate the install. Use whenever adding a new plugin to the project — it keeps settings.json in sync with what is installed."
 argument-hint: >-
   <name@marketplace> [--repo <owner/repo>]
 user-invocable: true

diff --git a/plugins/dev-team/skills/adr-tools/SKILL.md b/plugins/dev-team/skills/adr-tools/SKILL.md
@@ -1,13 +1,6 @@
 ---
 name: adr-tools
-description: >-
-  Create and manage Architecture Decision Records using the adr-tools CLI
-  (https://github.com/npryce/adr-tools). Use when the user asks to "add an ADR",
-  "record this decision", "create an ADR", "supersede ADR N", "link ADRs",
-  "generate the ADR table of contents", or any request involving the `adr`
-  command. Pairs with the adr-author agent — this skill is the mechanics
-  (commands, files, links); adr-author is the decision framework (when an ADR is
-  warranted) and the prose authoring.
+description: "Create and manage Architecture Decision Records via the adr-tools CLI (https://github.com/npryce/adr-tools). Use when the user asks to \"add an ADR\", \"record this decision\", \"create an ADR\", \"supersede ADR N\", \"link ADRs\", \"generate the ADR table of contents\", or any request involving the `adr` command. Pairs with the adr-author agent: this skill is the mechanics (commands, files, links); adr-author is the decision framework and prose."
 role: worker
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/agent-add/SKILL.md b/plugins/dev-team/skills/agent-add/SKILL.md
@@ -1,12 +1,6 @@
 ---
 name: agent-add
-description: >-
-  Create a new Oh-My-Pi (OMP) agent file (review or team type) following the
-  official sub-agent schema and token-efficiency budgets. Use when the user
-  wants to add a new review agent, detect a new category of code issue, create
-  a team agent persona, or says things like "add an agent for X", "create a
-  reviewer for Y", "new team agent for Z". Also use when given a URL to a
-  coding standard that should become a review agent.
+description: "Create a new Oh-My-Pi (OMP) agent file (review or team type) following the official sub-agent schema and token-efficiency budgets. Use when the user wants to add a review agent, detect a new category of code issue, or create a team-agent persona: \"add an agent for X\", \"create a reviewer for Y\", \"new team agent for Z\". Also use when given a URL to a coding standard that should become a review agent."
 argument-hint: >-
   <description-or-url> [--name <name>] [--type review|team]
   [--tier small|mid|frontier] [--context diff-only|full-file|project-structure]

diff --git a/plugins/dev-team/skills/agent-audit/SKILL.md b/plugins/dev-team/skills/agent-audit/SKILL.md
@@ -1,11 +1,6 @@
 ---
 name: agent-audit
-description: >-
-  Audit code-review agents, skills, and hooks for structural compliance.
-  Use this when adding or modifying any agent, skill, or hook file, or for
-  a periodic health check of the toolkit. Trigger phrases: "audit the
-  agents", "check compliance", "validate the skills", "are the agents
-  correct", or any time agent/skill files change.
+description: "Audit code-review agents, skills, and hooks for structural compliance. Use when adding or modifying any agent, skill, or hook file, or for a periodic health check: \"audit the agents\", \"check compliance\", \"validate the skills\", \"are the agents correct\", or any time agent/skill files change."
 argument-hint: "[file-path | --all] [--fix]"
 user-invocable: true
 allowed-tools: read, edit, search, find

diff --git a/plugins/dev-team/skills/agent-create/SKILL.md b/plugins/dev-team/skills/agent-create/SKILL.md
@@ -1,13 +1,6 @@
 ---
 name: agent-create
-description: >-
-  Create new Oh-My-Pi (OMP) sub-agent files following the official schema and
-  token-efficiency budgets. Handles both review agents (JSON output, read-only
-  tools, ≤ 40-line body) and team agents (prose output, action tools, ≤ 75-line
-  body). Use when the user says "add an agent", "create a reviewer for X",
-  "new team agent for Y", or when /agent-add is invoked. Validates against
-  /agent-audit before writing. Updates the agent registry and CLAUDE.md after
-  success.
+description: "Create new Oh-My-Pi (OMP) sub-agent files following the official schema and token-efficiency budgets — review agents (JSON output, read-only tools, ≤ 40-line body) and team agents (prose output, action tools, ≤ 75-line body). Use when the user says \"add an agent\", \"create a reviewer for X\", \"new team agent for Y\", or when /agent-add is invoked. Validates against /agent-audit before writing, then updates the agent registry and CLAUDE.md."
 role: worker
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/agent-eval/SKILL.md b/plugins/dev-team/skills/agent-eval/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: agent-eval
-description: >-
-  Run eval fixtures against review agents and grade results. Use this after
-  adding or modifying a review agent, to validate detection accuracy, or
-  when the user says "run the evals", "test the agents", "check for
-  regressions", or "how accurate is the agent".
+description: "Run eval fixtures against review agents and grade results. Use after adding or modifying a review agent, to validate detection accuracy, or when the user says \"run the evals\", \"test the agents\", \"check for regressions\", or \"how accurate is the agent\"."
 argument-hint: "[--agent <name>] [--skill <name>] [--fixture <name>] [--trials <n>] [--verbose]"
 user-invocable: true
 allowed-tools: >-

diff --git a/plugins/dev-team/skills/agent-readiness/SKILL.md b/plugins/dev-team/skills/agent-readiness/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: agent-readiness
-description: >-
-  Score how ready the current repository is for AI-assisted development against
-  the Agent-Readiness Scorecard. Use when the user asks "how agent-ready is this
-  repo", "score this repo for agents", "agent readiness", or wants a tiered
-  readiness report.
+description: "Score how ready the current repository is for AI-assisted development against the Agent-Readiness Scorecard. Use when the user asks \"how agent-ready is this repo\", \"score this repo for agents\", \"agent readiness\", or wants a tiered readiness report."
 argument-hint: "[repo-path] [--json <file>] [--markdown <file>]"
 user-invocable: true
 allowed-tools: >-

diff --git a/plugins/dev-team/skills/agent-remove/SKILL.md b/plugins/dev-team/skills/agent-remove/SKILL.md
@@ -1,11 +1,6 @@
 ---
 name: agent-remove
-description: >-
-  Remove an agent from the system — deletes the agent file, cleans up all
-  registry entries, removes cross-references, and updates documentation.
-  Use when the user says "remove the X agent", "delete X-review", "retire
-  the X role", or "we no longer need X". Handles both team agents and review
-  agents. Always confirms before deleting.
+description: "Remove an agent — deletes the agent file, cleans up registry entries and cross-references, and updates docs. Use when the user says \"remove the X agent\", \"delete X-review\", \"retire the X role\", or \"we no longer need X\". Handles team and review agents; always confirms before deleting."
 argument-hint: "<agent-name> [--dry]"
 user-invocable: true
 allowed-tools: read, edit, bash(rm *), bash(ls *), bash(git rm *), bash(grep -r *), find, search

diff --git a/plugins/dev-team/skills/agent-skill-authoring/SKILL.md b/plugins/dev-team/skills/agent-skill-authoring/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: agent-skill-authoring
-description: Conventions, anti-patterns, and meta-patterns for writing skills (and the shared agent/skill philosophy). Use when creating or editing a SKILL.md file, or when reviewing the agent-vs-skill separation. For the procedural workflow that generates a new agent file, use the agent-create skill (invoked by /agent-add).
+description: "Conventions, anti-patterns, and meta-patterns for writing skills (and the shared agent/skill philosophy). Use when creating or editing a SKILL.md file, or reviewing the agent-vs-skill separation. For the procedural workflow that generates a new agent file, use the agent-create skill (invoked by /agent-add)."
 role: worker
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/apply-fixes/SKILL.md b/plugins/dev-team/skills/apply-fixes/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: apply-fixes
-description: >-
-  Apply correction prompts generated by /code-review. Use this whenever the
-  user wants to apply, fix, or action the results of a code review — phrases
-  like "apply the fixes", "fix the issues", "apply corrections", or after
-  /code-review has run and produced a corrections/ directory.
+description: "Apply correction prompts generated by /code-review. Use when the user wants to apply or action review results: \"apply the fixes\", \"fix the issues\", \"apply corrections\", or after /code-review has produced a corrections/ directory."
 argument-hint: "<corrections-dir> [--dry] [--skip-tests] [--skip-build] [--skip-lint]"
 user-invocable: true
 allowed-tools: read, edit, search, find, bash(git diff *, npm run *, npx *, yarn *, pnpm *)

diff --git a/plugins/dev-team/skills/benchmark/SKILL.md b/plugins/dev-team/skills/benchmark/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: benchmark
-description: >-
-  Capture runtime performance metrics (Core Web Vitals, resource sizes, load
-  times) for web pages. Compare against baselines and performance budgets.
-  Use when the user says "benchmark", "check performance", "page speed",
-  "web vitals", "performance regression", or "how fast is this page".
+description: "Capture runtime performance metrics (Core Web Vitals, resource sizes, load times) for web pages and compare against baselines and budgets. Use when the user says \"benchmark\", \"check performance\", \"page speed\", \"web vitals\", \"performance regression\", or \"how fast is this page\"."
 argument-hint: "<url> [--baseline] [--budget] [--trend] [--mobile] [--3g] [--runs <n>]"
 user-invocable: true
 allowed-tools: read, write, find, search, bash(npx playwright *), bash(node *), bash(mkdir *), bash(date *), bash(cat *)

diff --git a/plugins/dev-team/skills/branch-workflow/SKILL.md b/plugins/dev-team/skills/branch-workflow/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: branch-workflow
-description: Clean branch completion workflow — PR creation, merge strategy, and cleanup. Use this skill when implementation is complete and it's time to ship — after Phase 3 human gate passes. Also use when the user says "create a PR", "merge this", "ship it", "finish this branch", or asks about merge strategy.
+description: "Clean branch-completion workflow — PR creation, merge strategy, and cleanup. Use when implementation is complete and it's time to ship (after the Phase 3 human gate), or when the user says \"create a PR\", \"merge this\", \"ship it\", \"finish this branch\", or asks about merge strategy."
 role: worker
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/build/SKILL.md b/plugins/dev-team/skills/build/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: build
-description: >-
-  Execute an approved implementation plan using TDD. Reads the plan, implements
-  each step with RED-GREEN-REFACTOR, runs inline review checkpoints, and
-  produces verification evidence. Use when the user says "build this", "implement
-  the plan", "start building", or after /plan has been approved.
+description: "Execute an approved implementation plan using TDD — read the plan, implement each step with RED-GREEN-REFACTOR, run inline review checkpoints, and produce verification evidence. Use when the user says \"build this\", \"implement the plan\", \"start building\", or after /plan is approved."
 argument-hint: "[--plan <path>]"
 user-invocable: true
 allowed-tools: read, write, edit, find, search, bash, task, ask

diff --git a/plugins/dev-team/skills/cd-test-architecture/SKILL.md b/plugins/dev-team/skills/cd-test-architecture/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: cd-test-architecture
-description: Evaluate an existing application's tests and recommend a CD-pipeline-aligned test architecture — fast, deterministic tests with minimal tooling that fully validate behavior (including cross-service interaction) and run in CI without configuring the rest of the system. Use when the user says "evaluate how this app is tested", "design a test architecture", "align our tests for CD", "make our CI tests deterministic", "our tests need the whole system configured", "our tests live in another repo / Postman / manual scripts", or asks for UI/service/batch test patterns.
+description: "Evaluate an existing app's tests and recommend a CD-pipeline-aligned test architecture — fast, deterministic, minimal-tooling tests that fully validate behavior (including cross-service) and run in CI without standing up the rest of the system. Use when the user says \"evaluate how this app is tested\", \"design a test architecture\", \"align our tests for CD\", \"make our CI tests deterministic\", \"our tests need the whole system configured\", \"our tests live in another repo / Postman / manual scripts\", or asks for UI/service/batch test patterns."
 role: worker
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/ci-debugging/SKILL.md b/plugins/dev-team/skills/ci-debugging/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: ci-debugging
-description: Systematic CI/CD failure diagnosis with hypothesis-first approach, environment delta analysis, and anti-patterns. Use when CI fails, pipelines break, or the user says "CI is failing", "build broke", "pipeline error", or "tests pass locally but fail in CI".
+description: "Systematic CI/CD failure diagnosis — hypothesis-first, environment-delta analysis, and anti-patterns. Use when CI fails or the user says \"CI is failing\", \"build broke\", \"pipeline error\", or \"tests pass locally but fail in CI\"."
 role: worker
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/code-review/SKILL.md b/plugins/dev-team/skills/code-review/SKILL.md
@@ -1,11 +1,6 @@
 ---
 name: code-review
-description: >-
-  Run all enabled review agents against target files. Use this whenever the
-  user asks for a code review, wants feedback on their code, says "review my
-  code", "check this before I PR", "what's wrong with this", "run the
-  agents", or has just finished implementing a feature. Use proactively
-  before commits and pull requests.
+description: "Run all enabled review agents against target files. Use whenever the user asks for a code review or feedback: \"review my code\", \"check this before I PR\", \"what's wrong with this\", \"run the agents\", or has just finished implementing a feature. Use proactively before commits and pull requests."
 argument-hint: >-
   [--agent <name>] [--since <ref>] [--path <dir>] [--all] [--json]
   [--force --reason "<text>"] [--static-analysis|--no-static-analysis]

diff --git a/plugins/dev-team/skills/competitive-analysis/SKILL.md b/plugins/dev-team/skills/competitive-analysis/SKILL.md
@@ -1,19 +1,6 @@
 ---
 name: competitive-analysis
-description: >-
-  Compare this plugin against external plugins, tools, feature sets, or ideas to
-  find gaps and weaknesses. Produces a structured gap analysis report with rough
-  specs for closing each gap. Use this skill whenever the user references
-  capabilities from OUTSIDE the plugin — another plugin they found, a competitor's
-  tool, a feature list from a different project, a repo URL, or a hypothetical
-  concept for capabilities we lack. Trigger phrases include "how do we compare
-  to X", "what does Y have that we don't", "what are we missing", "gap analysis",
-  "competitive analysis", "weaknesses compared to", "stack up against",
-  "where do we fall short", and "should we add X — I saw it in another tool".
-  Also trigger when the user pastes a feature list or describes capabilities
-  they saw elsewhere and asks whether we should have them. Do NOT trigger for
-  internal operations like running reviews, auditing our own agents, adding
-  skills, threat modeling, domain analysis, or debugging — those use other skills.
+description: "Compare this plugin against external plugins, tools, or feature sets to find gaps and weaknesses; produces a structured gap-analysis report with rough specs to close each gap. Use when the user references capabilities from OUTSIDE the plugin (a competitor tool, a pasted feature list, a repo URL, or \"should we add X — I saw it in another tool\"): \"how do we compare to X\", \"what does Y have that we don't\", \"what are we missing\", \"gap analysis\", \"competitive analysis\", \"weaknesses compared to\", \"stack up against\", \"where do we fall short\". Do NOT trigger for internal ops (reviews, agent audits, adding skills, threat modeling, domain analysis, debugging)."
 role: orchestrator
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/continue/SKILL.md b/plugins/dev-team/skills/continue/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: continue
-description: >-
-  Resume work from a prior session by reading phase progress files in memory/
-  and active plans. Use this when starting a new session on in-progress work,
-  or when the user says "continue", "pick up where I left off", "resume",
-  or "what was I working on".
+description: "Resume work from a prior session by reading phase-progress files in memory/ and active plans. Use when starting a new session on in-progress work, or when the user says \"continue\", \"pick up where I left off\", \"resume\", or \"what was I working on\"."
 argument-hint: ""
 user-invocable: true
 allowed-tools: read, find, search, bash(git log *), bash(git branch *), bash(git status *), bash(git diff *), bash(ls *)

diff --git a/plugins/dev-team/skills/cost-report/SKILL.md b/plugins/dev-team/skills/cost-report/SKILL.md
@@ -1,10 +1,6 @@
 ---
 name: cost-report
-description: >-
-  Report actual token spend and dollar cost of dispatched work — per agent and
-  total — and flag cost regressions. Use when the user asks "how much did that
-  cost", "token spend", "cost of this run", "cost report", or wants to check for
-  a cost regression after /code-review or an orchestration run.
+description: "Report actual token spend and dollar cost of dispatched work — per agent and total — and flag cost regressions. Use when the user asks \"how much did that cost\", \"token spend\", \"cost of this run\", \"cost report\", or wants to check for a cost regression after /code-review or an orchestration run."
 argument-hint: "[--transcript <path>] [--tolerance <n>]"
 user-invocable: true
 allowed-tools: >-

diff --git a/plugins/dev-team/skills/design-doc/SKILL.md b/plugins/dev-team/skills/design-doc/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: design-doc
-description: Produce a written design document in docs/specs/ with user approval before planning begins. Use this skill during the Research phase when a feature request, architectural change, or non-trivial task enters the pipeline. Ensures misunderstandings are caught before any planning or implementation work starts. Also use when the user says "brainstorm", "design", "spec", or "let's think through this".
+description: "Produce a written design document in docs/specs/ with user approval before planning begins. Use during the Research phase when a feature request, architectural change, or non-trivial task enters the pipeline, so misunderstandings are caught before planning or implementation. Also use when the user says \"brainstorm\", \"design\", \"spec\", or \"let's think through this\"."
 role: worker
 user-invocable: true
 ---

diff --git a/plugins/dev-team/skills/design-interrogation/SKILL.md b/plugins/dev-team/skills/design-interrogation/SKILL.md
@@ -1,13 +1,6 @@
 ---
 name: design-interrogation
-description: >-
-  Relentlessly interview the user about a plan, design, or feature spec to
-  surface unresolved decisions, hidden assumptions, and edge cases. Use when
-  the user says "grill me", "stress-test this plan", "poke holes in my design",
-  "what am I missing", or before committing to a plan that feels under-examined.
-  Unlike /specs (which produces artifacts) this skill produces clarity — it's a
-  thinking tool. Also use proactively in the Research phase when a design doc
-  has implicit decisions that need to be made explicit.
+description: "Relentlessly interview the user about a plan, design, or feature spec to surface unresolved decisions, hidden assumptions, and edge cases. Use when the user says \"grill me\", \"stress-test this plan\", \"poke holes in my design\", \"what am I missing\", or before committing to an under-examined plan. Unlike /specs (which produces artifacts) this produces clarity — a thinking tool. Also use proactively in the Research phase when a design doc has implicit decisions to make explicit."
 role: worker
 user-invocable: true
 ---