Home / nevenincs / vaultspec-core · GitHub

vaultspec-curate SKILL.md skillA

vaultspec-curate 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-curate@git:20260927.50639bc

Pins git:20260927.50639bc 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-curate/SKILL.md
Versions recorded: 9
Latest version: git:20260927.50639bc, committed Sep 27, 2026
First version recorded: Jul 14, 2026
Size: 4,150 bytes
Repository stars: 2
License: MIT

Audit and reconcile existing ADRs, implementation, and supporting records when the user requests vault curation or retrofit. Report decision conflicts and coverage gaps, and apply authorized repairs without rewriting decision history.

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

# Vault curation

Use this standalone maintenance workflow for a user-requested feature, decision cluster,
or corpus audit. It is not a pipeline stage or a prerequisite for ordinary ADR
authoring. The ADR author owns reconciliation for the decision being written; curation
examines existing records across a wider scope.

Finish a bounded pass with findings, applied repairs, and an honest coverage statement.
A partially reviewed corpus is a valid checkpoint, not a clean bill of health.

## Scope and ownership

Use the requested scope and existing authorization. A review-only request produces
findings without repairing reviewed records. A curation request permits confirmed,
content-preserving repairs within scope; changes to decision authority follow the
system's approval contract. Prior authorization counts.

Work directly, or delegate a bounded assignment to `vaultspec-docs-curator` when useful.
Give a delegate the scope, write authority, relevant evidence, and any continuation or
service budget. One owner persists the audit and coordinates shared writes; do not run
the same reconciliation independently in both sessions.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nevenincs/vaultspec-core/vaultspec-curate@sha256:e770c5f5455e7079

The line at the top of this page pins the label git:20260927.50639bc, 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_h7u3ct3qb7ar67wj.svg)](https://markdownregistry.com/a/art_h7u3ct3qb7ar67wj)

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

Versions

The registry has recorded 9 versions of this file, between Jul 14, 2026 and Sep 27, 2026, about one every 9 days.

version	committed	commit	size	audit
git:20260927.50639bc latest	2026-09-27	50639bc	4,150 B	A	view · diff
git:20260924.afdc9ea	2026-09-24	afdc9ea	9,119 B	A	view · diff
git:20260908.5b40718	2026-09-08	5b40718	7,739 B	A	view · diff
git:20260908.ce86e08	2026-09-08	ce86e08	7,741 B	A	view · diff
git:20260905.f755314	2026-09-05	f755314	7,560 B	A	view · diff
git:20260826.80b272e	2026-08-26	80b272e	8,662 B	A	view · diff
git:20260723.7fc2f3b	2026-07-23	7fc2f3b	8,624 B	A	view · diff
git:20260714.dc27844	2026-07-14	dc27844	8,562 B	A	view · diff
git:20260714.d74188f	2026-07-14	d74188f	8,268 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 (4150 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_h7u3ct3qb7ar67wj
GET https://markdownregistry.com/api/v1/resolve?ref=nevenincs/vaultspec-core/vaultspec-curate
GET https://markdownregistry.com/api/v1/blob/e770c5f5455e70790659409001691e601227139e43e28d58826b35caab151201

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.