vault-clarification SKILL.md skillA
vault-clarification from jbaruch/speaker-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jbaruch/speaker-toolkit/vault-clarification@git:20261020.9721075Pins git:20261020.9721075 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jbaruch/speaker-toolkit
- Path
skills/vault-clarification/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261020.75cc466, committed Oct 20, 2026
- First version recorded
- Oct 20, 2026
- Size
- 17,974 bytes
- Repository stars
- 22
- License
- none declared
Runs interactive clarification sessions with the speaker after talk processing. Resolves ambiguities in rhetoric observations, validates findings, captures speaker intent, conducts humor post-mortems, and probes for blind-spot moments invisible to transcripts. Stores confirmed intents and infrastructure config in the tracking database. Opens with the topics vault-ingress recorded when the speaker accepted the session, and closes that session in the run obligations ledger. Triggers…
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 Clarification — Interactive Session
Process steps in order. Do not skip ahead.
Each step's output informs the next. The first-session infrastructure capture in
Step 6 gates profile generation downstream.
Resolve the absolute path of this loaded `SKILL.md`, then set
`speaker_toolkit_root` to the plugin root two directories above the directory
containing this file. Never derive it from the consumer working directory.
Treat `{speaker_toolkit_root}` as absolute in every toolkit-owned command;
vault paths remain consumer-owned.
Run after vault-ingress has processed talks. Purpose: resolve ambiguities, validate
findings, capture intent, and fill in speaker infrastructure config.
vault-ingress Step 9 invokes this skill for an accepted session, and that call
carries `run_id`: the run in `{vault_root}/ingress-obligations.json` whose
session is pending. A call without `run_id` is standalone; Step 2 still checks
the ledger for a session left pending by a host that could not make the call.
The vault lives at `~/.claude/rhetoric-knowledge-vault/` (may be a symlink).
Set `host_python` to the current host's explicit absolute interpreter path (not
…Read the whole file at its exact version.
How to install
mdr add jbaruch/speaker-toolkit/vault-clarification@sha256:880ef8a3a217582eThe line at the top of this page pins the label git:20261020.9721075, 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_cgjk5jqkqk73m4jg)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 20, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.75cc466 latest | 2026-10-20 | 75cc466 | 17,974 B | A | view · diff |
| git:20261020.8b44b36 | 2026-10-20 | 8b44b36 | 18,110 B | A | view · diff |
| git:20261020.95dc15b | 2026-10-20 | 95dc15b | 17,974 B | A | view · diff |
| git:20261020.9721075 | 2026-10-20 | 9721075 | 18,641 B | A | view · diff |
| git:20261020.a6fa0e7 | 2026-10-20 | a6fa0e7 | 18,955 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 (17974 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
jbaruch/speaker-toolkit · 22 stars · license none declared · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cgjk5jqkqk73m4jg GET https://markdownregistry.com/api/v1/resolve?ref=jbaruch/speaker-toolkit/vault-clarification GET https://markdownregistry.com/api/v1/blob/880ef8a3a217582e7dbe05605964634c003d4c38cc85637d6892af33e46fff94
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.