writing
Skill8 starsChanged 3 months agoMITView on GitHub
Jeremy's longform writing process, preferences, and human-in-the-loop Google Doc collaboration protocol. Use when helping draft, structure, outline, scaffold, edit, fact-check, or reorganize any essay, article, blog post, Substack piece, tweet thread, or long-form argument Jeremy will publish under his own name — or when collaborating in a Google Doc on such a piece. Also fires on oblique openers like "let's get back to the essay / the AI piece." Jeremy writes the actual prose himself; this skill is scaffolding + evidence + editing his words, NOT ghostwriting. Do NOT use for code comments, commit messages, PR descriptions, docs-as-code / READMEs, or short throwaway/parody tweets (that's kauffj-voice).
51 other projects use a version of this.
Adopted by
Most recently taken up by
- LarsLrn/orcaitheir own version, first seen Nov 8, 2026
- ryanportfolio/winuse-mcptheir own version, first seen Nov 8, 2026
- NilsHellwig/acl-paper-skillstheir own version, first seen Nov 8, 2026
- fracazo/design-systemtheir own version, first seen Nov 8, 2026
- zakirkun/slayerclawtheir own version, first seen Nov 8, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 7, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
- ryanportfolioSkill
apply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions51 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 51
- wu-yc/LabClaw★ 1.1ksame name
- agentic-community/mcp-gateway-registry★ 1ksame name
- solana-foundation/explorer★ 856same name
- notque/claude-code-toolkit★ 448same name
- notque/vexjoy-agent★ 448same name
- zeuikli/claude-code-workspace★ 155same name
- joshuadavidthomas/agent-skills★ 49same name
- iliaal/ai-skills★ 45same name
- aws-samples/sample-agentic-coding-harness-benchmarks★ 20same name
- alxyrgin/secondbrain_ai★ 17same name
41 more not listed
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.
- AGENTS.mdAGENTS.md
- instructions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- exploreSkill
- featureSkill
- find-sessionSkill
- fix-ciSkill
- humanizerSkill
- kauffj-voiceSkill
- proposeSkill
- review-prSkill
- review-securitySkill
- review-simplicitySkill
- review-uiSkill
- workspaceSkill
The file
Files
Writing with Jeremy — longform co-pilot
Jeremy is writing something he will publish under his own name. Your job is to make his writing better without ever becoming its author. Read the two source-of-truth files once per session before producing anything:
$HOME/.claude/skills/writing/PREFERENCES.md— his standing rules (what he wants, what he refuses). Authoritative; if it conflicts with your instinct, it wins.$HOME/.claude/skills/writing/PLAYBOOK.md— the process and the reusable moves (the pipeline, evidence tiering, hot-zone handling, the Google Doc protocol, fact-check discipline).
Append to $HOME/.claude/skills/writing/lessons.md whenever he corrects you.
The three rules you may never break
- He writes the words. For anything signed, deliver a scaffold — section moves, bullets to expand, which evidence goes where, his own seed lines, transitions — never finished prose in his voice. A full draft is something he'd have to tear down, not build on. When genuinely unsure whether he wants scaffold or prose, ask.
- Typo bright line. In his Doc you may directly fix only unambiguous misspellings and typos. Word choice, grammar-as-style, hyphenation, tense, phrasing → anchored comment, never a silent edit. Report every direct fix in chat at the end of a pass.
- This is not
kauffj-voice.kauffj-voice(incl. its--seriousregister) is for tweets, throwaway, and parody. Do not invoke it to draft signed longform — that's the ghostwriting rule 1 forbids. For questions about his voice, point atkauffj-voice; don't restate it here.
Fast orientation
- Where things live and why (authorship split, drift avoidance): see PLAYBOOK.md → "Architecture."
- Editing his Doc (block tags, comment types, index-staleness safety): PLAYBOOK.md → "Doc protocol."
- Starting a new piece from raw material (memo/notes → scaffold): PLAYBOOK.md → "Pipeline."
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.