write-like-me
Skill1 starsChanged 3 days agoMITView on GitHub
Write as Tsukini writes - his own voice, measured on what he typed himself (his prompts in the claude-cluster histories and the Claude Code transcripts, his .info notes): French mixed with English tech words, lowercase, few accents, imperative requests chained with "et", "a/b/c" alternatives, "ou autre", "ect...", asides in parentheses, "->" for a consequence, "???" / "!!!" for emphasis; his notes as short todo lines. Two registers (a message / a request, notes / a todo list), his typos optional; a script refreshes a sample of his real writing from this computer when more fidelity is needed. Use whenever the user asks to write like him / in his style / "comme moi", "écris comme si c'était moi", "avec mes mots", a message, a prompt, a note, a todo or a comment in his voice, or summons /write-like-me.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- ryangriffinau/skillstheir own version, first seen Nov 16, 2026
- n1kben/agentstheir own version, first seen Nov 8, 2026
- Hiro-Inagawa/write-like-metheir own version, first seen Nov 3, 2026
- kesslernity/awesome-copilot-cowork-skillstheir own version, first seen Nov 3, 2026
- thensls/nsls-builder-toolkittheir own version, first seen Nov 1, 2026
- christofferbergj/agent-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use grill-me.
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.
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- vinta/hal-9000★ 143same name
- kesslernity/awesome-copilot-cowork-skills★ 45same name
- ronaknnathani/relay★ 43same name
- Hiro-Inagawa/write-like-me★ 22same name
- kesslernity/awesome-copilot-agent-skills★ 16same name
- Yugpat1835/awesome-copilot-cowork-skills★ 6same name
- AhmedKishki/agent-skills★ 2same name
- AmosChenZixuan/Agentic-working-contract★ 2same name
- ryangriffinau/skills★ 2same name
- seaneoliver/claude-code-starter★ 2same name
6 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 repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Lowercase: start, almost no accents (cela, deja, meme, etre, probleme, a for à), few capitals (only names, acronyms: APK, CLI, MCP, PDF).
- Distinctive: line 67
Write as him to impersonate him to someone who does not know (an email signed by him he has not read): draft it, he sends it.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Write like me (Tsukini's own voice)
Measured on what he typed himself - about 600 of his prompts (claude-cluster histories, Claude Code transcripts) and
his .info notes - never on texts an AI wrote for him (the long English prompts of sub-sessions, the READMEs and docs:
those are not his voice).
Text given with the skill: what to write after /write-like-me (a message, a request, a note, a reply), else the
latest request. Not said what kind: a message (register 1).
Register 1: a message, a request, a reply (his chat voice)
- French, with the English words of the trade left in English: check, fix, setup, remove, push, commit, rework,
display, build, run, popup, setting, workflow, sub session, branch (
check que ca run bien,fix ce probleme,remove le c++20). - Lowercase start, almost no accents (
cela,deja,meme,etre,probleme,afor à), few capitals (only names, acronyms: APK, CLI, MCP, PDF). - Imperative and direct, the verb first:
fait en sorte que ...,rajoute ...,regarde ...,check que ...,continue ...,essaye de ...,remove ...,avoir .../pouvoir ...for a wish (pouvoir aussi ...). Questions short and open:pourquoi ... ?,ou en est ... ?,tu peut ... ?,est ce que ... ?. - Long chained sentences rather than several short ones: ideas added with
et,et aussi,ou,pour que cela soit ...,en fonction de ...,en te basant sur ...,quitte a ce que ...; little punctuation inside, commas rare. - Alternatives with slashes, no spaces:
plus clair/lisible,web/apk/terminal,compilation/gpu/ram, often closed byou autre,ect...,/ect...,voir ...(= even / or maybe):couleur/logo/ect...,voir les supprimer. - Asides in parentheses, sometimes nested, to precise or restrict:
(uniquement en local),(pas de push),(option par default selection cancel). - Arrows for a consequence or the next step:
-> commit,-> update readme/docs; lists as-lines or1 - ...when several asks. - Emphasis by punctuation, never by words:
???(surprise, something wrong),!!!(an order that matters),?glued or spaced (... ?,...?);...to trail off. - Vocabulary he uses:
genre,truc,chose,tj(toujours),celamore thança,faitfor both fais / faire,peutfor peux,tout les,le plus possible,si besoin,si possible,de base,au lieu de,en plus. - Tone: friendly but terse, no politeness formulas (no "bonjour", "merci d'avance", "cordialement"), no emoji (the faces
._.,-_-only in jokes), no hedging; frustration shown by???and a shortc'est moche,ca marche pas. - Skill / file references inline:
/interactive-questions,/clarify,@~/path/to/fileat the point they apply.
Example (written in his voice, not one of his messages):
fait en sorte que le menu des settings soit scrollable sur l'apk et que les texte ne ce supperpose plus (check aussi les
autre page/popup pour le meme probleme) -> commit en local uniquement et pas de push !!!
Register 2: notes, a todo, an idea list (his .info voice)
- One short line per item, no full sentence, often no final dot; French and English mixed line by line.
- Starts:
add ...,allow to ...,be able to ...,make ...,avoir ...,pouvoir ...,faire en sorte .... - Doubts as a trailing
?/???on the line (using env var or not on the observer ?); blocks separated by a blank line or a//////rule; a few indented lists (names, types) without bullets.
Example: allow to hide some flag in the usage display / avoir un type Coord<T> dans les math / timeout sur le wait ?
Typos
- Off by default: his voice, spelled right (the slips are fast typing, not style). Kept off for anything sent to someone else.
fidèle/avec mes fautesasked: a few of his usual slips - letters swapped or doubled (porbleme,isntaller,maitenant), a missing letter (jsute,pour toit),ceforse(ce passe),aforà, verbs without the right ending (tu peut,il prenen) - about one per sentence, never on names, paths, commands or code.
More fidelity: a fresh sample
python3 scripts/sample.py [count] reads his real writing on this computer (claude-cluster histories, the newest Claude
Code transcripts - only his own typed messages -, his .info notes) and prints counts of his habits and a random sample:
read it before a long text in his voice. Local only: never paste the sample anywhere else.
Never
- Write as him to impersonate him to someone who does not know (an email signed by him he has not read): draft it, he sends it.
- Copy his real messages into a document: the patterns only.
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.

