Ghost

Skill slogsdon/skills-vault-knowledge/skills/ghost

Use when you want to answer a question in Shane's voice, when asked to ghost-write as Shane, or when the /ghost command is invoked. Do NOT use for writing in Shane's voice when he is the author — this produces content as Shane, for external use.From its SKILL.md

Install

npx -y skills add slogsdon/skills-vault-knowledge --skill ghost

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 423 tokens by cl100k_base, as published. Nobody here has run it

Skill: /ghost [argument]

Write content in Shane's authentic voice by grounding in his vault's vocabulary and reasoning style — a mirror, not a generic imitation.

Don't: invent voice patterns not present in the vault. Don't use generic writing conventions — mirror what the vault actually reveals about Shane's style.

Steps

Parse the argument/topic from Shane's request.
Follow Qwen Protocol with:
- task: "Vault access (bash only, no MCP tools): obsidian search query='TERM' limit=10, obsidian read file='Note Name' (no .md). Answer the question or topic '[argument]' in Shane's authentic voice. Use the Ghost Writer Context file and vault notes to mirror his vocabulary, reasoning style, and tone. Produce content as Shane would write it."
- skill: "ghost"
Review Qwen's result, synthesize if needed, and present to Shane.

Fallback

If Qwen is unavailable:

Run obsidian search query='[argument]' limit=10 via bash to find notes related to the topic
Run obsidian search query='voice OR style OR writing' limit=10 via bash to find notes that reveal Shane's voice patterns
Run obsidian search query='Ghost Writer' limit=5 via bash to find the Ghost Writer Context file if it exists
Read 5–8 relevant notes by running obsidian read file='[note name]' via bash for each, to absorb his vocabulary and reasoning style
Produce the content in Shane's voice:
- Mirror his vocabulary (direct, specific, no hedging)
- Use his reasoning style (builds from first principles, acknowledges tradeoffs)
- Match his tone (intellectually engaged, occasionally dry, no fluff)
- Cite specific vault material where relevant, as he would
Present the ghost-written content to Shane

What ships with it

Read from the repository