Home / avestura / whiteboard-defense · GitHub

whiteboard SKILL.md skillA

whiteboard from avestura/whiteboard-defense is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add avestura/whiteboard-defense/whiteboard@git:20261014.3ffd1e6

Pins git:20261014.3ffd1e6 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
avestura/whiteboard-defense
Path
plugins/whiteboard-defense/skills/whiteboard/SKILL.md
Versions recorded
6
Latest version
git:20261014.3ffd1e6, committed Oct 14, 2026
First version recorded
Oct 13, 2026
Size
19,469 bytes
Repository stars
5
License
MIT

Produces a "whiteboard defense" brief after substantial coding, design, or content work, so the user can explain and defend what was shipped. Lists the decisions made, who made each one (user, inferred, or the agent's default), the alternatives not taken, failure modes, and questions the user should be able to answer. Flags where the agent silently relied on a default (the usual logo, slide-deck format, UI style, library choice, architecture). Use at the end of any substantial task that is, or…

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

# Whiteboard defense

The standard this skill serves: **at any moment, the user could be pulled aside and asked to explain any customer-facing system they shipped, and defend the decisions behind it.** They do not need line-level knowledge. They need the high-level model: how it works, why X and not Y, what a malicious actor could do, where it fails.

You (the agent) made many decisions while working. Most the user never saw. Your job is to surface them, honestly, in a form the user can learn from in two minutes.

Two things matter above all:

1. **Provenance.** For every decision, say who made it. The user must be able to tell "I asked for this" from "the agent picked this on its own".
2. **Defaults.** Say where you filled a gap with your habitual choice instead of a deliberate one. Models fall back on a small set of default styles and patterns; the user wants those named, not hidden.

## Modes

Read the first word of the user's arguments, if any.

| Invocation | Mode | Behavior |
|---|---|---|
| automatic (end of substantial task) | `short` | Chat-only digest, at most 15 lines. Cheap by design: no file, no reference files read. |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add avestura/whiteboard-defense/whiteboard@sha256:b8a67d9cff7839d5

The line at the top of this page pins the label git:20261014.3ffd1e6, 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 badge

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

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

Versions

The registry has recorded 6 versions of this file, between Oct 13, 2026 and Oct 14, 2026, more than one a day.

versioncommittedcommitsizeaudit
git:20261014.3ffd1e6 latest2026-10-14 3ffd1e6 19,469 BA view · diff
git:20261013.e47cf402026-10-13 e47cf40 19,184 BA view · diff
git:20261013.66e74f92026-10-13 66e74f9 21,685 BA view · diff
git:20261013.2f474342026-10-13 2f47434 21,329 BA view · diff
git:20261013.978762b2026-10-13 978762b 20,726 BA view · diff
git:20261013.6634dd92026-10-13 6634dd9 13,517 BA 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 (19469 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

avestura/whiteboard-defense · 5 stars · license MIT · pushed 2026-10-14 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_vjjgqjwvr277o5j5
GET https://markdownregistry.com/api/v1/resolve?ref=avestura/whiteboard-defense/whiteboard
GET https://markdownregistry.com/api/v1/blob/b8a67d9cff7839d5f9c9f61ce29880bde0c713481ef3c29530c3ca48dd660e1d

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.

Browse by kind, by grade A, or by owner.