Use for marketing, social, replies, product copy, launch copy, and writing in the user's voice when their Emulo writing profile should guide the task.
SkillScore61Maintained
Automatic
◆Writing & Editing pack
Last verified 8/28/2026
What it changes
Passed 10 of 17 test cases with the skill, and 4 of 17 without it.
Without skill26%
With skill61%
Checks it passed that the model alone missed
The response halts context loading upon encountering the nonzero exit code.
The response invokes python "$EMULO_PY" plugin profile-path --domain write.
The response includes the exact recovery command run emulo and deepen write.
and 12 more in the full report
10 fixed4 passed either way7 still failing2 broke
Pass-rate lift
+35 pp
Tokens
+36%
Agent turns
0%
Response time
+43%
Model gemini-3.6-flashMeasured 8/28/2026v114 of 23 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Write a follow-up response to this pasted Slack thread: "A: hey, did you catch that memory leak in the worker pool? B: yeah fixed it in PR 42, just waiting on CI."
What was checked, without and with the skill
Checked
Without skill
With skill
The response matches the casual tone of the pasted conversation thread.
Passed
Passed
The response outputs the register selection statement in one short line before writing the text.
Missed
Passed
case-14 · gemini-3.6-flash · 8/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md13 linessingle file
Emulo write
Locate emulo.py two directories above this skill; fall back to ./emulo.py only for a direct repo checkout.
Store the resolved absolute runtime path as EMULO_PY, then run python "$EMULO_PY" plugin profile-path --domain write.
If it exits nonzero, give its exact recovery or targeted-deepen instruction and stop loading personal context.
Read every returned path completely. The first is the core working profile; the second is the writing profile. Apply both.
Pick the register from context; never ask. A writing profile with register sections (## Voice laws, ## Casual register, ## Professional register) loads voice laws always, plus exactly one register:
An explicit audience statement from the user ("for my boss", "make it formal") always wins.
Otherwise infer from what is in the task: a pasted thread with a manager, client, or customer, a formal email, documentation, or official product copy selects professional; a community reply, social post, chat banter, or a builder-to-builder thread selects casual; a pasted conversation selects the register matching that thread's own audience and tone.
State the pick in one short line ("using professional register") so it is correctable, then write; never block on register confirmation.
If the picked register has no section in the profile, load the voice laws only and never substitute the other register; say so in the same line ("professional register not mined yet, using voice laws only") and suggest run emulo and deepen write to mine it.
A flat profile without register sections applies in full, unchanged.
Never imitate a generic voice when the writing domain is inactive.