Home / mikeheid / overture · GitHub

roar SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

roar from mikeheid/overture is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add mikeheid/overture/roar@git:20261008.a084eb1

Pins git:20261008.a084eb1 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: mikeheid/overture
Path: plugin/skills/roar/SKILL.md
Versions recorded: 2
Latest version: git:20261008.a084eb1, committed Oct 8, 2026
First version recorded: Oct 2, 2026
Size: 8,870 bytes
Repository stars: 5
License: MIT

Run a three-perspective panel (architect, ux, and an advisor seat) on a question, decision or design - independent reads in parallel, a deliberation round where the panelists challenge each other, then a full implementation plan. Use when the user types /overture:roar followed by a question, decision or design under review. Inside an owner-console round (a fork with roles ["roar"]) the console-fork skill's section 7 governs, and the round ends in lockable questions, not a plan.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Roar: three seats, one deliberation, one plan

`/overture:roar <prompt>` runs a **three-round** panel that ends in a
complete implementation plan. The user sees a short status block before each
round.

1. **Round 1, independent reads.** Three panelists answer in parallel. None
   sees the others.
2. **Round 2, deliberation.** Each panelist sees the other two's Round 1
   claims and concedes, pushes back or refines.
3. **Round 3, synthesis.** A full implementation plan built on where Round 2
   converged.

The plan is the deliverable. Rounds 1 and 2 exist to pressure-test it.

## Which mode you are in

- **Inside an owner-console round.** You reached this from the console-fork
  skill (a fork whose `roles` is `["roar"]`, with a fork id and a bundle from
  `A fork-context FORK_ID`). Follow console-fork **section 7** for the rules
  that are the console's: at most one roar per lock, the `ck-fork:FORK_ID ROLE`
  prefix on every seat's task description, the transcript stored with
  `A transcript`, and **Round 3 ends in one to five lockable questions, not a
  plan**. Nothing is written into the project before the owner locks; a change
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add mikeheid/overture/roar@sha256:a431240967f7f9f1

The line at the top of this page pins the label git:20261008.a084eb1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_th6pqdbu727ap66d.svg)](https://markdownregistry.com/a/art_th6pqdbu727ap66d)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Oct 2, 2026 and Oct 8, 2026, about one every 7 days.

version	committed	commit	size	audit
git:20261008.a084eb1 latest	2026-10-08	a084eb1	8,870 B	A	view · diff
git:20261002.ae38807	2026-10-02	ae38807	8,891 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (8870 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

mikeheid/overture · 5 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_th6pqdbu727ap66d
GET https://markdownregistry.com/api/v1/resolve?ref=mikeheid/overture/roar
GET https://markdownregistry.com/api/v1/blob/a431240967f7f9f1ae01aa943a5ed2508d6d0d0886bae8dd7c530aa7c6676610

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.