Home / nevenincs / vaultspec-core · GitHub

vaultspec-team SKILL.md skillA

vaultspec-team 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-team@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-team/SKILL.md
Versions recorded: 7
Latest version: git:20260927.50639bc, committed Sep 27, 2026
First version recorded: May 22, 2026
Size: 2,021 bytes
Repository stars: 2
License: MIT

Supervise several workers over one approved plan. Use when the plan's Parallelization section names containers that may run concurrently.

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

# Team (vaultspec-team)

A coordination policy for executing an approved plan with parallel workers; the host
environment dispatches, sequences, and monitors them. It adds nothing to the pipeline:
each worker runs `vaultspec-execute` on its assigned container, and the supervisor keeps
the plan and the review gate. For single-persona work, load the persona directly.

## Shape

- Assign the Steps or whole containers the plan declares: Steps at L1, Steps or Phases
  at L2, and suitable containers at higher tiers. The plan's Parallelization section
  says which may run concurrently.
- Each worker follows `vaultspec-execute` as a dispatched worker: one commit and its
  ledger rows per Step, Steps closed through the plan verbs, blockers raised to the
  supervisor, assignment completion reported to the supervisor. Report Phase close only
  when a Phase exists.
- Workers never change plan structure; the supervisor applies changes through the plan
  verbs under the system's scoped approval contract. Routine corrections need no new
  approval. Isolate working trees or serialize shared plan, ledger, and commit writes;
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nevenincs/vaultspec-core/vaultspec-team@sha256:d61baf81a4602f09

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_jpdevyccragush4m.svg)](https://markdownregistry.com/a/art_jpdevyccragush4m)

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

Versions

The registry has recorded 7 versions of this file, between May 22, 2026 and Sep 27, 2026, about one every 21 days.

version	committed	commit	size	audit
git:20260927.50639bc latest	2026-09-27	50639bc	2,021 B	A	view · diff
git:20260908.af390dd	2026-09-08	af390dd	1,647 B	A	view · diff
git:20260905.f755314	2026-09-05	f755314	1,331 B	A	view · diff
git:20260613.68b0c19	2026-06-13	68b0c19	2,376 B	A	view · diff
git:20260612.69d4b58	2026-06-12	69d4b58	2,340 B	A	view · diff
git:20260610.5560595	2026-06-10	5560595	1,542 B	A	view · diff
git:20260522.5e7dd03	2026-05-22	5e7dd03	1,439 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 (2021 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_jpdevyccragush4m
GET https://markdownregistry.com/api/v1/resolve?ref=nevenincs/vaultspec-core/vaultspec-team
GET https://markdownregistry.com/api/v1/blob/d61baf81a4602f099372547ca30b83bb4eb7d7302818c831d1e2be4abb3d3ada

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.