Skip to content
Agentmart
Submit a tool
This entry duplicates creative-writing-muse, which is the one we list in search.

creative-writing-muse

Load when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.

Skill by FiredMosquito831

IndexedApache-2.0★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/firedmosquito831-creative-writing-muse

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Load when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.

Use cases: writing, research, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name
creative-writing-muse
Description
Load when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.
License
Apache-2.0
Instructions
56 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Creative Writing Muse

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.

## Choose the Stance

Load the skills needed for the next stance:

- **Direction:** `/story-planning`
- **Drafting:** `/creative-writing-modes`, `/creative-writing-craft`, `/llm-writing`
- **Critique:** `/story-review`, `/reader-sim`, `/writing-principles`
- **Research:** `/creative-research`
- **Voice and terms:** `/creative-writing-craft`, `/character-sim`, `/shared-dao`
- **Memory:** `/story-memory`; also `/kb-management` and `/project-setup` if available
- **Ledgers:** `/story-ledgers` — planning chapters, capturing what a chapter changed, answering what's still open / who knows what
- **Series:** `/series` — linking a book to a library, bootstrap and retcon lifecycle, the retcon detection catalog, handoff generation, series state card (optional library layer; advisory-only, no fourth gate)
- **Gates:** `/gates` — before accepting a pivotal chapter, before export, any scoring task
- **Demolition:** `/demolition` — offered before marking a chapter `final` (author may decline)
- **Voice:** `/voice` — voice capture, drift checks, retune when the prose stops sounding like the author

Note: in single-agent mode (this skill), the stance switch replaces subagent
isolation — demolition and drafting must never share a stance-turn.

## Self-Prompt Before Each Stance

Before doing the next pass, name the prompt you are giving yourself:

- What is the author's intent for this pass?
- What reader effect should the output create or protect?
- Which constraints, style references, canon, and vocabulary matter now?
- What should remain ambiguous, unresolved, rough, or strange?
- What output should this pass produce?
- What would be the wrong kind of success?

Ask the author only when the answer would change the work. Otherwise state your
read and continue.

## Keep Stances Separate

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.

From FiredMosquito831/my-writing-companion, Apache-2.0.

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Sep 11, 2026 (1 month ago)
Last release
Sep 11, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from FiredMosquito831

Cite this page

creative-writing-muse skill. Agent Mart. https://agentmart.dev/skills/firedmosquito831-creative-writing-muse (last updated 2026-10-24)