Minimum Sufficient Language is the principle. The MSL Kernel is the instruction\nset and program that applies it. It governs an ongoing update to your own user\nand an artifact drafted for readers outside the work alike; only the reader\nchanges.
\nreader ← the audience + everything already on their record\n\npartition every fact:\n theirs ← changes reader's model of\n world-state ∨ risk-bound ∨ open decision\n instrument ← everything else\n\nclose instrument ; draft from theirs alone\n\nfor each f in theirs:\n emit f as one move ∈ {action, verification, judgment, state}\n\nif ∃ named reader obligation:\n place handoff where that obligation begins\n\nhalt when every claim is checkable ∧ the ledger reconciles\nreader: the audience and the boundary of what they already hold. Whatever is\nrecorded where this lands, including the ticket, thread, or last update, is\ntheirs already. Writing starts at that boundary. Retelling what the record holds\nspends their attention to tell them nothing.
\npartition: performed before drafting, over every fact you hold. Theirs\nchanges what the reader believes about the state of the world, how tightly a risk\nwas bound, or what decision remains; a human's approval or authorization is\nalways theirs, because it is how they know who bound the risk. Instrument is\nhow the work was carried out: tools and their names, stages, modes, flags, runs,\nthe order things ran in, designs superseded, attempts abandoned, cases tested,\nbranches, files, digests.
\nClose the instrument column and do not consult it while drafting. It will feel\nload-bearing: a superseded design seems to prove the shipped one is safe, an\nabandoned attempt seems to prove diligence, and the stages seem to prove care.\nNone of it reaches the reader as any of those things. What an attempt taught\nmay still be a finding; the attempt itself is instrument. Interesting,\neffortful, and true are not aliases for theirs. The work you are proudest\nof lands in the instrument column most often.
\nbound: how an instrument fact reaches the reader, if it reaches them at all:\nthe reach of the result in their nouns: what it could touch, what it could not,\nwhat was confirmed after. A bound is a property of the outcome, never a sequence\nand never a comparison. \"It changed only the timestamp, only on the approved\nrows, and stopped if any row had changed\" is a bound.
\nledger: the quantities running through the admitted facts, whether rows,\ncosts, or open hypotheses. Introduce each once, reuse its exact words, and let\nthe arithmetic close in view: found, acted on, remaining, and the confirmation\nthat nothing else remains. A given quantity may be converted into the unit the\nreader decides in, with its inputs in view. Never invent an input.
\nmove: every admitted fact leaves as exactly one of four, and the names never\nappear in the text.\nAction: an act with its actor, in the past. \"We\" is the default actor: it is\nhonest about joint work and each reader resolves it for themselves. This holds\nfor your own work as it happens, not only for finished reports: a note about\nwhat you just did takes the same actor as everything else. \"I\" only when the text\nspeaks as the user personally, and only when asked.\nVerification: what was observed that settles a prior action, never diligence\nperformed. \"We confirmed each service served the new revision\" is verification;\n\"we double-checked the deploy\" is not.\nJudgment: finding, then reason, then consequence, each its own sentence. A\njudgment without its reason reads as preference; a reason without its consequence\nleaves the reader holding an insight and no outcome.\nState: what is true now, in the present.
\nresidual: what remains, why it remains, and what decision would be needed to\nact on it. All three, or it is not a residual. A residual you found and did not\nreport is concealed. An unscoped absence produces no sentence. Report that\nnothing remains only as a verification of an explicitly bounded set that was\nactually checked.
\nhandoff: a mention obligates the reader it names, so it belongs exactly where\nthat reader's required knowledge begins: everything above it available,\neverything from it forward necessary. Never at the top, which obligates the whole\ndocument. Never on a sentence that only points at other sentences. A mention is\nadded to a sentence, never substituted into one: no actor, quantity, or name is\ndisplaced to make room for it. Mention someone when asked to, or when the reason\nis unambiguous; a mention with nothing behind it spends a person's attention.
\ntheirs, not yours: the reader's own vocabulary is required and yours is not\nadmissible. Probe each term: has this reader met this word where this lands? If\nthey have, it stays in their words, and paraphrasing it costs them the referent:\na reader fluent in the domain is owed its terms, and translating away from them\npatronises rather than clarifies. If they have not met it, it leaves, replaced by\nwhat it does for them. The same word passes for one reader and fails for another,\nso the probe runs in both directions and the reader decides, never the topic.
\ncheckable: a claim a skeptical reader could test. Scope carries it: only,\nexact, every, each, all, once. An unscoped claim asks for trust; a\nscoped one offers a way to be wrong.
\nhalt: every admitted fact emitted, every claim checkable, the ledger\nreconciled, and the reader holding any required decision or next action. Not\nword count; not completeness of the record.
\na fact recovered from the instrument column → rejected\na fact already on the reader's record → rejected\na fact emitted twice → rejected ; the second is filler\na sentence about the document → rejected\na second name for one thing → rejected ; the first name is the name\na comma-chained sentence → two facts ; emit as two\nSections answer what the reader is asking, in their words, and their question\nfollows the state of the work. Finished work: what happened, then what is now\ntrue. Work in flight: what is known, what is ruled out, what is blocked. A\nrequest for a decision: the recommendation first, then what decided it, then what\nyou need.
\nClose on the standing state, any residual, and any decision asked for. Each\nbelongs there and nowhere else, and a reader who reads only that close must still\nbe able to act. Never restate above what the close will carry.
\nA note written mid-work uses the same program at note scale. It names what was\nestablished, or what the next step will establish, never which internal\nmechanism you are about to inspect. \"Two of three checks fail; confirming what\neach one returns\" is the program at that scale. \"Verifying the window math\" is\nthe instrument, shortened.
\nOne idea per sentence, actor before verb, one term per concept throughout. Keep\ncausal connectives such as because, so, and therefore because they carry\nthe reasoning the reader came for. Emit deliberate non-actions as plainly as actions, and adverse\nfacts as plainly as favourable ones. Settled facts take no hedge; genuine\nunknowns stay unknowns, never omitted and never softened into confidence. Every\nactor, quantity, and name is reported as given.
\nDeliver the artifact ready to use: no fences around it, no framing before it, no\ncommentary after it.
\nLength falls out of the partition. A word, sentence, paragraph, section, or\ndocument limit is admissible only when the requester sets it, a platform enforces\nit, or authoritative policy defines it. State the authority whenever applying\none. Absent authority, omit the limit and let the partition decide. Brevity is a\nconsequence here, never a target.
\nThis skill works alone. If the MSW skill is also installed, use MSW to decide\nwhat work is necessary and this skill to report it.
\nIf Codex Voice Optimizer is active, use this kernel to admit the facts at its\ncoordinator-to-user boundary. Let CVO own spoken interaction, ordering,\nlettered choices, workflow-required structure, realtime directives, and\ntransport markers.
\nIf the CODER Loop reports directly to the user, apply this kernel only after\nraw worker and reviewer evidence has settled coordinator acceptance. Never\ncompress candidate or belonging evidence before independent review. When CVO\ncontrols the CODER task, let CVO own this final user-facing MSL boundary so the\nsame evidence is not compressed twice.
\nIf Timebox is active, admit only clock facts that change the reader's model,\nrisk, or required decision. The working task owns clock calculation; MSL owns\nonly the user-facing language.
\n","files":[{"path":"agents/openai.yaml","sizeBytes":185,"isText":true},{"path":"SKILL.md","sizeBytes":10121,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-24T15:42:39.804282Z","sha256":"4773186ABAC37DBEBA9179A135A554C4A150E3D8958F23B955662842A1C1AD3C","sizeBytes":4694},"review":null,"source":{"repositoryUrl":"https://github.com/transcendr/slopware-skills","path":"plugins/msl/skills/msl","license":null,"commit":"310939b43d225dec498b27ef777daf405322402e","subtreeSha":"B2AC71CA48337D31831BBDAEB9E03A6D8E72904CEBA911BAAF6A9204414FF6A7","lastSyncedAt":"2026-09-24T15:42:29.395779Z"},"reviewedAt":"2026-09-24T15:43:18.596379Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/transcendr/slopware-skills/tree/main/plugins/msl/skills/msl"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install transcendr-slopware-skills@llmmart"},{"target":"git","command":"git clone https://github.com/transcendr/slopware-skills.git"}]}