← Search

Adopt a typed spec for your hand-written CLAUDE.md
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 1d562c6
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : installs packages
⚙ Needs: Node.js and npm…

Adopt a typed spec for your hand-written CLAUDE.md

Start a typed CLAUDE.md.spec.ts from your existing hand-written instructions — faithful, non-destructive, reversible, and never an upgrade in disguise

At a glance
What
Start a typed CLAUDE.md.spec.ts from your existing hand-written instructions — faithful, non-destructive, reversible, and never an upgrade in disguise
Cost
Free
Needs
Node.js and npm, and a hand-written CLAUDE.md (or AGENTS.md) you want to keep as the starting point. The skill itself is guidance your agent follows, not software; the vigiles CLI it works with is installed separately, inside the project where you use it (npm install -D vigiles). No accounts, no API keys, no cost. Never paste secrets here.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Adopt Spec is a free Muse skill that starts a typed CLAUDE.md.spec.ts from your existing hand-written instructions, faithfully, non-destructively and reversibly. Its adoption rules are non-negotiable: preserve every rule, command and prose section, so the spec compiles back to roughly your existing file, with Key Files entries carried over and placed where each fits.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 1d562c6

Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: Node.js and npm, and a hand-written CLAUDE.md (or AGENTS.md) you want to keep as the starting point. The skill itself is guidance your agent follows, not software; the vigiles CLI it works with is installed separately, inside the project where you use it (npm install -D vigiles). No accounts, no API keys, no cost. Never paste secrets here. Install "Adopt a typed spec for your hand-written CLAUDE.md" for me. It is @zernie's adopt-spec skill for the vigiles tooling: when I ask it to, it reads my existing CLAUDE.md (or AGENTS.md), works out its structure — commands, rules (and how each is enforced), prose sections, and any "Key Files" list — classifies each rule (enforce, guidance, or TODO), and drafts a typed CLAUDE.md.spec.ts that compiles back to about the file I already have, without ever editing the original. It shows me the draft and a summary first and writes only if I say yes; switching my file to spec-managed is a separate step I run myself, and vigiles eject hands it back as plain markdown anytime. MIT-licensed. Source: https://raw.githubusercontent.com/zernie/vigiles/1d562c69566f6ca611bc84b1be5cbe2f4157043e/skills/adopt-spec/SKILL.md (a single file — no helper files) Pinned version: install the code at commit 1d562c69566f6ca611bc84b1be5cbe2f4157043e exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 12, 2026: Skill Harbor regenerated this install prompt from the current upstream file, because the generated spec no longer carries your key-files list as a map. The old keyFiles field is deprecated and the skill must never emit it: each entry of a "Key Files" list is now placed where it fits — a note in that file's own header comment, a rule in that folder's own CLAUDE.md, or a one-line file() pointer in the section that needs it — and which place is your call, entry by entry. Until you decide, the list is carried over as a plain prose section, so nothing is lost, but it does not land in the spec as a structured map the way the previous prompt described. 1. Download SKILL.md into a temporary folder. 2. Compare it with the fingerprint from Skill Harbor's review of 2026-10-12: - SKILL.md: SHA-256 966652ae80d70ccd2bd4a1c8a7aef3ec01250fac90813c552cfabdc275d9286c If the file does not match, it changed since the review: do not install it yet — tell me what you found and let me decide. 3. Read the file and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. 4. When I say yes, copy SKILL.md into my skills folder, in a folder named "adopt-spec". 5. Check the copy opens correctly (valid frontmatter, file in place) and tell me what was installed, where, and what is left for me to do (for example: install vigiles in the project where I want to use it — npm install -D vigiles — then ask you to adopt my CLAUDE.md; the skill only runs when I invoke it directly, and it presents the spec before writing anything). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It can download and install software packages.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 1d562c6 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : installs packages
What the scan found — excerpts from the install prompt
  • installs packages — Prerequisites: Node.js and npm, and a hand-written CLAUDE.md (or AGENTS.md) you want to keep as the starting p · 5. Check the copy opens correctly (valid frontmatter, file in place) and tell me what was installed, where, an · Prérequis : Node.js et npm, et un CLAUDE.md (ou AGENTS.md) manuscrit que tu veux garder comme point de départ.
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
1d562c6 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : installs packages

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.