Home / mikeheid / overture · GitHub

refine 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.

refine 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/refine@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/refine/SKILL.md
Versions recorded: 2
Latest version: git:20261008.a084eb1, committed Oct 8, 2026
First version recorded: Oct 2, 2026
Size: 4,061 bytes
Repository stars: 5
License: MIT

Revise one existing spec or planning document so it says what was decided - read it and the decisions and findings that bear on it, propose the changes as a change list before touching it, and name the other documents the change ripples into. Use when the user types /overture:refine, or for an owner-console "Refine" fork (the overture:refine next_step).

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

# Refine: revise one document to match what was decided

A targeted revision of something that already exists. (To go one level down
into something that has no spec yet, use drill instead.)

## Where the project keeps its documents

1. `.overture.json`'s `specs_dir`, if set, is where its specs live.
2. The project's `CLAUDE.md` or README, which usually names its spec folder,
   decision log and findings register.
3. Otherwise the **App Architect convention**, if the project uses it: an
   `architect/` folder holding `digest.md` (a running summary with a segment
   map and a `## Decisions` section), `10-stack.md`, `30-segments.md`,
   `40-specs/<segment>.md`, `50-master/` (generated copies) and
   `60-review/findings.md`. Use whichever of these exist.

## Find the target

Resolve the argument to **one** file: a spec under the specs folder, or a
planning document (stack, segment map, an orchestrator or master copy).
Inside an owner-console round the target is what the locked answer, or the
round's answers, cite: their `source`, `evidence` and `valid_if` paths, and
the item's spec. If it resolves to nothing, or to several files, say so and
stop rather than guess.

## Steps
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add mikeheid/overture/refine@sha256:8c58a02f12930adb

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_am2vdf5mwpb4beia.svg)](https://markdownregistry.com/a/art_am2vdf5mwpb4beia)

3 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	4,061 B	A	view · diff
git:20261002.ae38807	2026-10-02	ae38807	4,070 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 (4061 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_am2vdf5mwpb4beia
GET https://markdownregistry.com/api/v1/resolve?ref=mikeheid/overture/refine
GET https://markdownregistry.com/api/v1/blob/8c58a02f12930adb2008238f9589d9b3ae05da46e451fb98842a16ff7389b74a

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.