writing-craft
Skill0 starsChanged 2 months agoMITView on GitHub
Invert's house style decisions for any prose — Slack, email, LinkedIn, blog, status updates, investor comms, internal docs. Fires on \"help me write,\" \"draft this,\" \"tighten this,\" \"edit this,\" \"how does this read.\" Owns mechanics and house conventions only; what to claim belongs to content-proportion-check. Not for strategy discussion or concept questions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Ptlimited/writing-crafttheir own version, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Ptlimited/writing-craft★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- blog-cold-readSkill
- content-proportion-checkSkill
- defensibility-checkSkill
- giving-feedbackSkill
- hamming-taste-principlesSkill
- idea-to-briefSkill
- learning-mediumSkill
- linear-write-cleanupSkill
- portable-handoffSkill
- saddles-positioningSkill
- session-stateSkill
- skill-auditSkill
- strategy-decisionsSkill
- transcript-auditSkill
- uncertainty-killerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
If emphasis needs a mark, reorder the sentence instead.
- Distinctive: line 59
All verbatim-backed. All gone.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Writing Craft
Concision, active voice, specifics over abstractions, and cutting throat-clearing are default behavior — they are not listed here. This file carries only the arbitrary choices, which I'd otherwise guess at.
House conventions
- Oxford comma: always. "We invited the strippers, JFK, and Stalin."
- US English, no trailing s: toward, backward, afterward, forward.
- Exclamation points: almost never. One per document maximum, reserved for genuine exclamations. If emphasis needs a mark, reorder the sentence instead.
- Emphatic word last. End position carries the weight: "…but it has hardly advanced in fortitude."
Grammar calls worth getting right
- Comma before because flips the meaning. "Rhonda didn't do it because she loved him" (she did it, not for love) vs. "Rhonda didn't do it, because she loved him" (she didn't; love is the reason). Usually you want the comma.
- "And so" — drop the and. Both are conjunctions; keep so.
- Comma + conjunction only between two independent clauses. "He ate all the food, and went back for more" is wrong — the second clause has no subject. Drop the comma.
- Dependent clause first takes a comma; second doesn't. "As the wave crashed down, the surfer fell." / "The surfer fell as the wave crashed down." (since, while, because, although, as)
Two editing rules that beat instinct
- Zweig's two-thirds. Take the draft's word count, multiply by ⅔ — that's the ceiling. Short-form (Slack, email): cut by half on the first pass.
- Kill your favorite line. Whatever you like most in your own writing is usually what readers like least. The clever phrase is the first cut.
Marketing copy: the shape Nick actually ships
Encoded from his hand-rewrite of a LinkedIn post (2026-07). Each item is my draft → his cut. These are observed preferences from one substantial rewrite, not laws — if a later rewrite contradicts one, update it.
- No antithesis openers. I wrote "The hard part isn't the judgment call. It's assembling the data to make it." He wrote "One of the hardest parts of a deviation investigation is assembling the data to make it." Setup-across-two-sentences reads as a writerly tic. Say it once, in one sentence.
- Hedge the problem, sharpen the benefit. My instinct runs the other way. He softened every claim a practitioner could counterexample ("the hard part" → "one of the hardest parts"; "the evidence lives in" → "the evidence you need is often spread across") and then made a benefit claim larger than any I'd have passed: "Invert gives everyone the power of an SME." Absolute claims about the customer's world are exposure. Absolute claims about what Invert does for them are the product.
- Mine the friction detail for the benefit line. I used "larger queries need an SME with different system access" only as pain. He flipped that same detail into the value proposition. When a problem sentence names a scarce person, role, or access level, the benefit line is usually "everyone gets that."
- Second person. "The evidence you need," not "the evidence needed."
- Copy is a caption for a visual, not a substitute for it. He replaced my prose description of the capability with "Here's an example of…" — the post exists to hand off to a demo clip. Default assumption for marketing copy: something visual is coming. Write the handoff, not the replacement.
- Cut the problem chain if it delays the product. He deleted the most heavily sourced material in the draft — the 48-hour window, open-high-and-park, three records become six, retest timing, patient impact. All verbatim-backed. All gone. This sits in real tension with content-proportion-check's "practitioner is protagonist, Invert in the methods section." His revealed preference is shorter and faster to Invert. Lead with the short version; offer the problem-led long version as the alternate, don't default to it.
- Close on business consequence, flatly. Mine: "The investigation is still theirs. The search for the data doesn't have to be." His: "It matters how long deviation investigations take. Each hour spent costs real money." Blunter, and worse as prose — that's the point. No writerly turn in the final line.
- "Kill your favorite line" already covered this, and I ignored it twice. Both closers I wrote were favorite lines; both were cut. The rule bites hardest on the last sentence. Apply it there first.
One thing to flag rather than silently inherit: he closed on cost, but the sourced practitioner led with patient delay, not money. For a cost-negative site building an NPV case, money is plausibly the better buying trigger — but it was a substitution, so don't assume it generalizes to every audience.
Before returning
Show original and rewrite side by side so the pattern is visible, and flag the top 3–5 problems rather than every instance.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

