Proofread

proofread

Correct the mechanical language errors in one supplied Text Artifact, and change nothing else about it.

$HERE is the directory that contains this SKILL.md, and $MANAGER is the Manager directory: $HERE/../kntnt/ if it exists, else kntnt/ under a Global harness skills directory (~/.claude/skills, ~/.config/opencode/skills, or wherever another Harness keeps them). Neither found: tell the user to install the Manager (npx skills add Kntnt/skills) and stop. $LIBRARY is $MANAGER/library/ — absent, tell the user to run /kntnt update, then stop.

Run uv run --no-cache --no-project "$MANAGER/scripts/kntnt.py" invoke --here="$HERE" with the invocation payload — everything the user typed after /proofread, verbatim, however many lines — on stdin. On exit 0, answer the capabilities in its dependencies first: for each one, say whether its confirm sentence is true of you, and where it is not, give its how, change nothing, and stop. Then continue from the JSON. On any other exit print its stdout verbatim and stop: it has already printed what the user is to see, and none of that text is yours to write.

In the JSON, path is the command path as a list, flags holds each flag the user wrote — true where it stood bare, its value where it carried one, a list of values where it was repeated — operands is what followed the flags, in order, and instruction is the Contextual Instruction, or null, applied as $LIBRARY/references/invocation-envelope.md says.

Run every UV command in this Skill with a fresh private directory as TMPDIR, and remove that directory after the command, including when it fails. The private directory belongs to that one command and no other run, so cleanup removes only files this run created.

A model-invoked run changes only how the Skill starts. Once started, it takes the specific Text Artifact the current turn identifies as the omitted operand and enters the same numbered steps as invocation by name. The paths join before loading any language or editorial resource; the trigger wording is not a second source of rules or an alternate execution path.

Where no Formal Invocation carries an Output Target, settle it from the current turn before correcting or writing. An unnamed destination resolves to the response, and a file mentioned only as the location of the errors names no destination: the verbs fix and correct apply to the named errors, not to the file containing them. Thus Fix the spelling and grammar mistakes in case.md delivers to the response. A turn that explicitly names the response or a path other than the source as the destination selects that Output Target; for example, Write the corrected text to corrected.md selects corrected.md as a separate Output Target. A turn that asks for the file itself to be changed selects In-place Editing only when it explicitly names that file as the object of the change or as the destination of the corrected text; for example, Update case.md with the grammar corrections selects In-place Editing. It remains subject to every refusal that editing mode already carries, including inline text, a URL, an uploaded or read-only source, more than one text, and a simultaneous separate Output Target. A request to save, apply, or persist the corrections without naming where they go is materially ambiguous about the destination: Fix the grammar errors in case.md and save the corrections asks which destination the caller intends and writes nothing. For that case and any other material ambiguity about the destination, ask which destination the caller intends and write nothing.

Arguments

The operand is the Text Artifact: inline text, one local path, or one URL, and exactly one of them — several paths, a glob reaching more than one file, or a directory of texts is more than one. Where the invocation carries no operand, it is the single text the current turn identifies.

--language=<selector> names the language or locale whose mechanics apply. Any spelling the Collection's resolver reaches is accepted — a canonical code (sv, en_GB), a case or separator variant of one (en-GB, EN_GB), a curated alias (BrE, brittisk engelska), or an ordinary description of a language in any language.

--output=<response|path> names the Output Target. response is the default and the value response states it explicitly; anything else is one filesystem path. It and In-place Editing name two destinations for one text, which is why no form carries both.

--in-place[=<value>] selects In-place Editing. It accepts yes, on, and true against no, off, and false; bare --in-place means on, --in-place=off has the same effect as omitting the option, and the default is off.

Steps

1. Settle the single Text Artifact and the options from the JSON. A value outside what ## Arguments admits — --in-place outside its vocabulary, or more than one Text Artifact — is refused as $LIBRARY/references/invocation-envelope.md says: correct nothing, write nothing, and stop. Done when one Text Artifact and a valid set of options are in hand, or you have stopped.
2. Settle the destination before anything is corrected, following $LIBRARY/references/delivery.md. Make every refusal that contract names by reading alone — In-place Editing together with a separate Output Target, an output path equal to the input path, In-place Editing against inline text or a URL or a source that is not a writable local file, and a destination whose parent directory does not exist — so that a refusal has nothing written behind it. Done when the destination is settled, or you have stopped.
3. Read the Text Artifact's leading YAML frontmatter where it has any, and look in it for one top-level kntnt map. That map is the only Kntnt configuration a document carries; language, lang, genre, technique, and every other key outside it are the document's own fields, whatever they are named and whatever they hold. Read language out of the map and nothing else out of it. The map is never required: a Text Artifact carrying none is proofread exactly like one that carries a complete one, its absence refusing nothing and leaving the language to the levels below it in step 4. Done when the artifact's recognized language value is known to be present, absent, or unreachable.
4. Resolve the language, taking the first of these that answers: the --language value; the recognized kntnt map's language value from step 3; the current Contextual Instruction; applicable Conversation Context; then the language of the Text Artifact itself, which is what inference reads and what the default already is. Suppression is that precedence working rather than an error: a Contextual Instruction every higher level has already settled leaves nothing for it to settle, and the run continues rather than refusing it as unaddressable guidance. Where saying so is useful, the delivery names the suppressed instruction beside the resolved configuration. Where that language is materially ambiguous or mixed — no dominant language, or alternation inside paragraphs — ask which language to proofread in rather than choosing one. Nothing has been written yet, so asking costs nothing to undo. Done when exactly one selector is in hand, or you have asked.
5. If step 3 found a recognized kntnt map whose language value no installed resource answers to, and --language supplied no value, report it as unusable artifact metadata: name the value, say that it is neither a canonical code nor an installed alias, and stop. Do not read it as the code it resembles. A --language value settles the parameter and suppresses this, the unusable map then being none of the run's business. Done when the run has stopped, or the metadata is not in the way.
6. Run uv run --no-cache --no-project "$LIBRARY/scripts/languages.py" resolve --scope=mechanics "<selector>". Exit 0: take the reported code as the resolved language and the mechanics scope as this run's language-specific rules. A non-zero exit means the selector reached no single installed resource — interpret the human description semantically, propose one candidate from uv run --no-cache --no-project "$LIBRARY/scripts/languages.py" list, and verify it through the same resolve command; ask only where no unique installed candidate can be established. Then load $LIBRARY/references/editorial/mechanics.md, the shared mechanics contract, which holds the rules of objective correctness that do not depend on the language; it and the resolved scope together are this run's rules, and the scope is the more specific of the two wherever they meet. That one document is the whole of what is admitted from the Collection's editorial resources: load no base contract, no genre, no technique, and no anti-slop catalogue, load no other scope, and read no composition, review, or anti-slop guidance from anywhere. Done when the contract and the mechanics scope are both in hand, or you have stopped.
7. Correct every objective mechanical error in the resolved language, reading the text yourself: misspellings, grammatical errors, punctuation errors, agreement between subject and verb or noun and modifier, wrong inflection, a duplicated word, a word plainly missing, and the locale's own conventions for dates, numbers, currency, and quotation as the mechanics scope states them, together with everything the shared mechanics contract holds. Correct all of them — a mechanical pass that leaves mechanical errors behind is a pass the user has to make again. Before this step is done, make an agreement-only re-read of every ordinary-prose sentence after the other corrections. Check agreement in both directions between subject and verb and between noun and modifier; in Swedish, olika bild must become olika bilder. Make that same re-read whether --language named the language or another level of the precedence settled it. A resolved locale establishes its date conventions but not what ambiguous source fields meant: 3/4 stays exactly 3/4 under both en_GB and en_US unless the Text Artifact itself establishes one reading; never expand or reorder it solely from locale. A grammatically valid word-as-word phrase such as the word probably remains unmarked: add no quotation marks or other emphasis unless the loaded rules identify an objective error. A code sample — a fenced block, an indented block, or an inline code span — is quoted material rather than the text's own prose: its contents are read past rather than read against the rules, so nothing inside one is a finding and nothing inside one is changed, the docstrings, comments, and string literals among them. Prose about code is ordinary prose and is read like every other sentence. Introduce no spellchecker, grammar service, or scanner of your own; the resolver above is the only script this Skill runs. Done when the mechanical errors you can identify are corrected.
8. Change nothing else. Wording, meaning, tone, register, argument, structure, factual content, formatting and markup, code and its contents, links, and metadata all come through untouched, and the frontmatter comes through byte for byte — a language value you were entitled to read is read and left exactly where it is, no kntnt map is added or removed, and nothing is reordered. A preference is not an error, and the rules step 6 put in hand are what says which is which: what neither of them names as an error comes through untouched, however tempting it is, and what either of them does name is corrected however deliberate it looks. A sentence improved here is the failure this Skill exists to prevent: mechanical correction was requested, and mechanical correction is the whole of what is delivered. Done when the diff you are about to deliver is mechanical throughout.
9. Deliver by $LIBRARY/references/delivery.md: the complete Text Artifact to the settled Output Target, the source file replaced where In-place Editing was requested, and a derived filename with its collisions resolved where the target is a directory. On a response target, remove every artifact or scratch file this run created and base the delivery account on the filesystem state that remains after cleanup. Where nothing was corrected and the destination is the response or the source file itself, write nothing at all and return only the short no-change status, in the language of the Text Artifact. Done when the Text Artifact has been delivered, or the no-change status has been reported.