manuscript-profile-setup — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited manuscript-profile-setup (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A manuscript's profile is what makes the rest of the suite genre-aware instead of guessing. It records the book's genre, audience, register, comps, craft standard, where the canon/series bible lives, which passes apply, and any marketing constraints. The passes read it automatically — you set it once.
Determine where .manuscript/ should live. From the current working directory, walk up the parent folders looking for an existing .manuscript/profile.md.
values, and ask what to change. Skip to STEP 3.
the author is working in (where the manuscript files are). Confirm the root in one line ("I'll set up the profile at <path>/.manuscript/ — is that the right project folder?") before writing, unless the author already named the folder.
First, try to infer from anything already available — the manuscript text, a bible document in the folder, the author's message. Then ask only the gaps. Keep it to a short, friendly back-and-forth, not a form dump. The fields:
memoir, nonfiction…).
dark, comedic, grounded…).
few load-bearing facts stated inline? (Fine to have none — say so.)
the book (a secret, a death, a timeline anchor).
listing; add fair-play only if it's a mystery/crime/thriller. (If the add-on manuscript-cinematic-scene-audit is installed, also add cinematic.)
Don't stall on blanks. Any field can be empty; the passes degrade gracefully and say what they couldn't judge. Capturing genre, audience, and the load-bearing facts gives 80% of the value.
greatness_set ← map from genre (mystery→mystery, fantasy→fantasy, romance→romance, thriller→thriller, literary→literary, memoir/nonfiction→memoir-nonfiction, anything else→general).
passes ← continuity + prose-immersion + publisher + listing by default; addfair-play iff genre ∈ {mystery, crime, thriller, suspense}; add cinematic iff the manuscript-cinematic-scene-audit add-on is installed.
ledger_path ← .manuscript/canon-ledger.json.State the derived defaults so the author can override them.
Write <project root>/.manuscript/profile.md using the schema in profile.template.md (the suite ships it at the repo root; mirror its YAML keys exactly so the passes can parse it). Preserve the author's free-text Notes section. For an edit, change only the requested fields and keep the rest.
Then seed an empty canon ledger if none exists: write <project root>/.manuscript/canon-ledger.json with the empty skeleton the manuscript-canon-ledger skill defines (its STEP "seed an empty ledger"). Do not populate canon here — that's the ledger skill's job.
Report, in a few lines: where the profile was written, the key choices (genre, audience, passes enabled, canon source), and what to do next — e.g. "Run manuscript-editorial-router on a chapter, or call any single pass directly." If the author originally asked for a critique and only needed setup to proceed, continue straight into that pass now.
fill load-bearing facts with guesses.
don't create a second one in a subfolder.
Notes. The author will open and hand-edit this file.
.manuscript/profile.md and an empty ledger. It does notread, grade, or rewrite the manuscript.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.