ghost-writing

Applies tone, British English, and formatting conventions when drafting or editing text.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/gnarea/clone --skill ghost-writing-gnarea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ghost-writing
Source: https://github.com/gnarea/clone/tree/main/skills/ghost-writing
Command: npx skills add https://github.com/gnarea/clone --skill ghost-writing-gnarea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting text on someone's behalf often produces output that sounds generic or inconsistent with their personal voice. This Skill enforces a specific set of writing conventions—tone, British English spelling, nomenclature, and formatting—so drafted or edited text reads as if the person wrote it themselves. ## Core Features & Use Cases - Formality-aware drafting: Selects informal, semi-formal, or formal rules based on context, covering chat messages, blog posts, documentation, specs, and Internet-Drafts. - British English enforcement: Applies -ise spellings, doubled consonants, British vocabulary ("licence", "whilst", "programme"), DD Month YYYY dates, and 24-hour times, while preserving American spellings in proper nouns and code identifiers. - Style and formatting rules: Enforces information density, active voice, Oxford commas, consistent list punctuation, and medium-appropriate link formatting from Markdown to plain text. - Use Case: Ask the assistant to draft a GitHub issue comment or edit a spec section, and the output follows the correct formality tier, spelling conventions, and formatting rules without manual correction. ## Quick Start Draft a semi-formal blog post paragraph about our release using my writing conventions.

Frequently Asked Questions about ghost-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-drafted text match my personal writing style?▼

Define explicit conventions for tone, spelling, and formatting, then apply them whenever drafting or editing. This Skill encodes rules for formality levels, British English, nomenclature, and punctuation so output consistently matches one voice.

How does the Skill choose between informal, semi-formal, and formal tone?▼

It determines formality from the context: chat messages and issue comments are informal, blog posts and documentation are semi-formal, and specs or Internet-Drafts are formal. When the context is ambiguous, it asks rather than guessing.

Does British English spelling apply to code identifiers and proper nouns?▼

No. Proper nouns and pre-existing identifiers such as CSS properties like background-color or license names like MIT License remain in American English. British spellings apply only to regular prose vocabulary.

Can I use these writing rules in plain-text emails without Markdown?▼

Yes. Formatting rules degrade gracefully by medium: Markdown links for docs and GitHub, platform-native syntax for rich-text tools, footnote-style references for formal plain-text email, and inline URLs for informal messages.

What are the limitations of rule-based ghostwriting conventions?▼

The rules cover tone, spelling, and formatting but cannot capture every stylistic nuance of a person's voice. Exemplar links for blog posts and specs help, yet ambiguous contexts still require user clarification to avoid mismatched formality.