reference-intake SKILL.md skillA
reference-intake from bandersnatch0x/design-playbook is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bandersnatch0x/design-playbook/reference-intake@git:20260828.582f33bPins git:20260828.582f33b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bandersnatch0x/design-playbook
- Path
packages/design-playbook/skills/reference-intake/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260828.582f33b, committed Aug 28, 2026
- First version recorded
- Jul 22, 2026
- Size
- 6,250 bytes
- Repository stars
- 3
- License
- a license file GitHub does not identify
Reference intake contract from screenshot, URL, design file, or product analogy. Use when the user supplies visual/product reference before build, or when Keep/Change/Do not copy boundaries are missing for a design ask.
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
# reference-intake
Turn raw reference material into a **run-local declaration input** the pipeline can consume without re-deriving from chat.
Not a style library. Not a code export. Not a Pass/Fail gate.
Authority boundary (ADR-0011):
| This skill owns | Does not own |
| --- | --- |
| Observed vs inferred evidence about the reference | `spec.md` L1→L6 |
| Keep / Change / Do not copy | decision report / Fill source |
| License and brand risk notes | evaluator verdict |
## When to apply / skip
**Apply** when the ask includes at least one of:
- local screenshot / mock / design export path
- URL of a live product or design
- existing in-repo design artifact the user points at
- explicit product or brand analogy ("like Linear", "reference Feishu settings page" — example (zh): "参考飞书设置页")
**Skip** when the ask is text-only product requirements with no reference material. Narrate once: `-> reference-intake?: no reference materials, skipped`.
## Steps
### 1. Inventory sources
List every reference source. For each source record:
- `kind`: `screenshot` | `url` | `design_file` | `product_analogy` | `other`
- locator (path or URL or product name)
…Read the whole file at its exact version.
How to install
mdr add bandersnatch0x/design-playbook/reference-intake@sha256:9c9ddd847f1397b7The line at the top of this page pins the label git:20260828.582f33b, 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_53fy5qo6j2cven6z)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 22, 2026 and Aug 28, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260828.582f33b latest | 2026-08-28 | 582f33b | 6,250 B | A | view · diff |
| git:20260821.2c1a20f | 2026-08-21 | 2c1a20f | 6,199 B | A | view · diff |
| git:20260821.e8bff11 | 2026-08-21 | e8bff11 | 5,463 B | A | view · diff |
| git:20260815.e7d4014 | 2026-08-15 | e7d4014 | 4,403 B | A | view · diff |
| git:20260722.120b091 | 2026-07-22 | 120b091 | 3,894 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 (6250 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
bandersnatch0x/design-playbook · 3 stars · license a license file GitHub does not identify · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_53fy5qo6j2cven6z GET https://markdownregistry.com/api/v1/resolve?ref=bandersnatch0x/design-playbook/reference-intake GET https://markdownregistry.com/api/v1/blob/9c9ddd847f1397b78ad6f2e99a0ae877b9814530ce6e215b85624b4ad37a9573
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.