orc-explain

Re-explains the last ORC output in plain language with background context and term definitions.

6|1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/azure-id/orc --skill orc-explain-azure-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orc-explain
Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-explain
Command: npx skills add https://github.com/azure-id/orc --skill orc-explain-azure-id

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an ORC pipeline message — a preflight block, a scoring line, a gate result — does not land, users often ask for a shorter version, which just repeats the same confusing message. This Skill re-pitches the exact message the user did not understand by adding the background it assumed and defining every ORC-specific term, without re-running any work. ## Core Features & Use Cases - Plain-language restatement: States the point of the last ORC output in one ordinary sentence, then supplies the missing background context. - Terminology definitions: Defines ORC-only terms (band, facet, disposition, P0–P3, freshness tier, wave, slice, gate, packet, lane) using the project's own wiki vocabulary when available. - Read-only and side-effect free: Never dispatches agents, edits files, changes gate outcomes, or writes traces — it explains only what was just said and returns to the exact run state. - Use Case: After ORC prints a gate result you do not follow, invoke /orc-explain to get the same decision restated with the assumed context filled in and each jargon term defined. ## Quick Start Ask the assistant to explain the last ORC message again in plain words, for example by typing /orc-explain or saying "wait, what does that gate result mean?"

Frequently Asked Questions about orc-explain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get ORC to explain a message I did not understand?▼

Invoke /orc-explain or say something like "wait, what?" after the confusing output. The skill restates the last ORC message in plain words, adds the background it assumed, and defines every ORC-specific term it used.

What ORC terms does orc-explain define?▼

It defines ORC-only vocabulary such as band, facet, disposition, P0–P3, freshness tier, wave, slice, gate, packet, and lane. When a project wiki exists, it uses wiki/orc-orientation.md so definitions match the rest of the repository's documentation.

Does orc-explain change or re-run any part of the pipeline?▼

No. It is strictly read-only: it never dispatches agents, edits files, changes gate outcomes, or alters phases. After explaining, the run resumes exactly where it was with no re-plan, re-score, or undo.

Why is orc-explain usage invisible in orc stats?▼

The skill writes no trace and owns no run, so it can fire many times per session without flooding the log directory. The accepted trade-off is that /orc-explain invocations do not appear in orc stats, which its help text states.

When should I not use orc-explain?▼

Do not use it when you actually want the work redone rather than restated. The skill only re-pitches the existing message; if you want different results, it will point you to the lane that re-does the work instead of silently becoming that lane.