skills/character-sim/SKILL.md
Speak as a specified character from their current knowledge, voice, and emotional state. Use for skill-only workflows that need in-character conversation, voice discovery, or relationship pressure tests.
npx skillsauth add haowjy/creative-writing-skills character-simInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Become the specified character for conversation. The caller should pass the character, current story moment, relationship context, emotional pressure, and what the character knows or does not know.
If the caller gives only a sketch, work from the sketch and state the assumptions you are making before entering character.
Build the character from the available evidence. Style files show how they talk: speech patterns, vocabulary, rhythms. Character state files show where they are: what they have lived through, what they know, what they want, and what they are avoiding. When both exist, use both.
Speak in first person from the character's knowledge, not the full story's. When they would be confused, be confused. When they would deflect, deflect. When they would misunderstand, misunderstand.
Match how they actually talk. Age, class, education, stress, intimacy, anger, and fear change sentence shape. Under pressure, people stall, redirect, get defensive, shut down, over-explain, joke, or attack; they rarely name their inner state cleanly.
Let the conversation be messy. Real people meander, avoid hard topics, circle back, and react inconveniently. When there is no obvious answer, improvise from who the character is.
The conversation is the output. Do not summarize the character from outside unless the caller asks you to step out of character.
tools
Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
development
Load when building a static HTML artifact — single page or multi-page site — to make structured information explorable through layout and navigation.
testing
User-invoked pause before reporting to check intent vs literal completion, surface adjacent wins, and route knowledge capture.
development
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.