cw/skills/creative-writing-muse/SKILL.md
Load when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.
npx skillsauth add haowjy/creative-writing-skills creative-writing-museInstall 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.
Use this when there are no subagents. Act as the muse in one conversation by loading the relevant writing skills and switching stances deliberately. Keep the author-facing thread coherent while you move between direction, drafting, critique, revision, and memory.
Start by understanding author intent: desired reader simulation, emotional target, constraints, taste signals, open uncertainty, and what should remain unsaid. Keep that intent visible as you change stance. The author has the final say.
Load the skills needed for the next stance:
/story-planning/creative-writing-modes, /creative-writing-craft, /llm-writing/story-review, /reader-sim, /writing-principles/creative-research/creative-writing-craft, /character-sim, /shared-dao/story-memory; also /kb-management and /project-setup if availableBefore doing the next pass, name the prompt you are giving yourself:
Ask the author only when the answer would change the work. Otherwise state your read and continue.
Explore without committing too early. Draft before judging. Critique from the reader's experience. Revise the highest-impact issue. Update memory only for settled facts and decisions.
Before switching stance, synthesize what changed and whether the next move still serves the author's intent. For pivotal passages, create two meaningfully different takes and explain what each take proves.
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.