drill 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.
drill from mikeheid/overture is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mikeheid/overture/drill@git:20261008.a084eb1Pins 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/drill/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261008.a084eb1, committed Oct 8, 2026
- First version recorded
- Oct 2, 2026
- Size
- 3,917 bytes
- Repository stars
- 5
- License
- MIT
Drill one level down into a segment or concept that has no spec yet - list the functions it must capture, ask the three to five questions that would change its spec (each with lettered options and a star), then write a short standalone spec. Use when the user types /overture:drill, or for an owner-console "Drill" fork (the overture:drill 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
# Drill: one segment, from functions to a spec One segment (or one concept a decision introduced) per run. (To revise a spec that already exists, use refine instead.) ## Where the project keeps its specs 1. `.overture.json`'s `specs_dir`, if set, is where specs live. 2. The project's `CLAUDE.md` or README, which usually names its spec folder and decision log. 3. Otherwise the **App Architect convention**, if the project uses it: an `architect/` folder holding `digest.md` (a running summary with a segment map), `10-stack.md` (the locked stack), `30-segments.md` (each segment with a `status`) and `40-specs/<segment>.md`. Use whichever of these exist. ## Find the target - **Standalone**: resolve the argument against the segment list (`30-segments.md` under the convention). `next` means the first segment not yet at status `spec`. - **Inside an owner-console round** (a fork with `step: "drill"`, run by the console-fork skill's section 8): the target is the thing the locked answer, or the round's answers, introduced that no spec covers yet. The owner's own words are in the bundle (`A fork-context FORK_ID`). ## Steps …
Read the whole file at its exact version.
How to install
mdr add mikeheid/overture/drill@sha256:02a7f13a637bf4d2The 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.
[](https://markdownregistry.com/a/art_46ll5ezaofnkrdwi)
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 | 3,917 B | A | view · diff |
| git:20261002.ae38807 | 2026-10-02 | ae38807 | 3,926 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3917 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
mikeheid/overture · 5 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_46ll5ezaofnkrdwi GET https://markdownregistry.com/api/v1/resolve?ref=mikeheid/overture/drill GET https://markdownregistry.com/api/v1/blob/02a7f13a637bf4d21c27e5fc1e478d25dff296d3791702946a89bce3851ad47b
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.
More from mikeheid/overture
Every file in mikeheid/overture