Home / nevenincs / vaultspec-core · GitHub

vaultspec-documentation SKILL.md skillA

vaultspec-documentation from nevenincs/vaultspec-core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add nevenincs/vaultspec-core/vaultspec-documentation@git:20260908.ce86e08

Pins git:20260908.ce86e08 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: nevenincs/vaultspec-core
Path: src/vaultspec_core/builtins/skills/vaultspec-documentation/SKILL.md
Versions recorded: 4
Latest version: git:20260908.ce86e08, committed Sep 8, 2026
First version recorded: May 22, 2026
Size: 11,523 bytes
Repository stars: 2
License: MIT

Create or substantially rewrite one user-facing README, guide, or feature document. Focused maintenance edits use a direct evidence-and-review pass.

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

# Documentation Pipeline

Produce one user-facing document grounded in its sources. For creation or substantial
rewriting, use the pipeline below. For focused maintenance, inspect the affected claims,
edit within the established structure, and verify technical accuracy and readability; do
not restart the full pipeline.

The system's approval contract applies throughout. Reuse supplied scope and audience;
ask only for material missing choices. Explicit prior authorization can cover a
wireframe and final delivery within that scope. These document stages are not plan
Phases and do not create additional framework review gates.

## The Pipeline

```
Phase 1: Wireframe -> Phase 2: Refinement -> Phase 3: User Approval -> Phase 4: Context Gathering -> Phase 5: Drafting -> Phase 6: Technical Review -> Phase 7: Editorial Review -> Phase 8: User Approval
```

For the full pipeline, complete each stage's purpose before the next. If delegation is
unavailable, perform the passes sequentially and state that review was not independent.
Section-level passes feed a cohesive whole-document review.

______________________________________________________________________

## Phase 1: Wireframe
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nevenincs/vaultspec-core/vaultspec-documentation@sha256:e27c14eda85495ff

The line at the top of this page pins the label git:20260908.ce86e08, 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_ek5uk2tesbkkchv7.svg)](https://markdownregistry.com/a/art_ek5uk2tesbkkchv7)

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

Versions

The registry has recorded 4 versions of this file, between May 22, 2026 and Sep 8, 2026, about one every 36 days.

version	committed	commit	size	audit
git:20260908.ce86e08 latest	2026-09-08	ce86e08	11,523 B	A	view · diff
git:20260905.f755314	2026-09-05	f755314	11,375 B	A	view · diff
git:20260613.68b0c19	2026-06-13	68b0c19	11,482 B	A	view · diff
git:20260522.5e7dd03	2026-05-22	5e7dd03	12,015 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 (11523 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

nevenincs/vaultspec-core · 2 stars · license MIT · pushed 2026-10-27 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ek5uk2tesbkkchv7
GET https://markdownregistry.com/api/v1/resolve?ref=nevenincs/vaultspec-core/vaultspec-documentation
GET https://markdownregistry.com/api/v1/blob/e27c14eda85495ffd3e80c4e2e86cf9499092a3d524b9c32a3a76cdc8ea9c633

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 nevenincs/vaultspec-core

vaultspec-adr SKILL.md skill

nevenincs/vaultspec-core · .vaultspec/skills/vaultspec-adr/SKILL.md · Record a costly decision, place it within accepted decision coverage, and reconcile affected ADR wording.