A read-only skill that visualizes the backend utilization of this session/project (delegation to Claude=host / Codex / Cursor).
The source of truth for records is .claude/state/orchestration-ledger.jsonl(the companion appends per delegation, Phase 90.1.1) and
.claude/state/orchestration-totals.json(idempotent roll up at session end/completion, Phase 90.1.2).
Display is on-demand only. Do not show during work; show it with this skill when you want to see it. Only once when all tasks are complete, task-completed automatically outputs a terminal summary (a separate path from this skill).
Quick Reference
- 「Show me the orchestration utilization" → generate and open the HTML scorecard
- 「Which backend was used」「Codex/Cursor how much" → Terminal summary
- 「Show me the cumulative totals」「The bragging-worthy one" → HTML scorecard (lifetime totals are the main feature)
Deliverables
| Output | Artifact |
|---|---|
| HTML scorecard | scripts/orchestration-scorecard.sh --format html-data → scripts/render-html.sh --template orchestration as a single HTML with |
| Terminal summary | scripts/orchestration-scorecard.sh --format terminal(3-5 lines) |
tri-state: used（count>0）/ available(configured but unused) / not-configured(binary absent = neutral, not broken).
If there are zero delegations, degrade to "no delegations observed".
Execution
Call the helper script from the plugin bundle root:
HARNESS_PLUGIN_ROOT="${HARNESS_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"
Terminal summary (--terminal）
bash "${HARNESS_PLUGIN_ROOT}/scripts/orchestration-scorecard.sh" --format terminal
Summarize 3-5 lines and present them as-is.
HTML scorecard (default / --out / --no-open）
OUT="${1:-.claude/state/orchestration-scorecard.html}" # --out <path> で上書き
bash "${HARNESS_PLUGIN_ROOT}/scripts/orchestration-scorecard.sh" --format html-data \
| bash "${HARNESS_PLUGIN_ROOT}/scripts/render-html.sh" --template orchestration --data - --out "$OUT"
--no-openIf not specified, present the path after generation and guide the user to open it in a browser (automatic open is environment-dependent, so presenting the path is the default)- Do not use redaction: scorecard data is structurally non-sensitive (counts + backend names + repo basename + timestamps only). The no-secret guarantee is ensured by the upstream ledger contract
Related Skills
harness-progress— progress dashboard (task progress. This skill specializes in backend utilization)harness-work/breezing— implementation (the side that actually uses the backend)