haowjy
83 verified skills6,913 total stars
writing-issues
Logging and referencing writing issues: craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review. Use when an agent identifies something worth tracking beyond a single critique report: repeated tics across chapters, inconsistencies that affect multiple scenes, structural problems that need the author's attention, or patterns that should be fixed in revision.
testing214
writing-staffing
Team composition for writing workflows: which agents to spawn, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, dispatching researchers, staffing draft/revise loops, or setting up brainstorm fan-outs.
data-ai214
prose-critique
Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
testing214
prose-writing
Prose-level immersion patterns for narrative fiction. Use when writing or revising prose: the sentence-level and paragraph-level craft that pulls readers into the story. Project-specific voice comes from style files passed alongside this skill.
testing214
story-architecture
Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.
development214
brainstorming
Story brainstorming capture: minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities.
data-ai214
writing-principles
What fiction readers want (four reward channels) and the specific ways LLM training damages each one. Load when drafting prose, critiquing, or diagnosing why a passage feels flat.
testing191
cw/skills/prose-critique
Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does. Focus-area driven. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
testing191
style-analysis
How to analyze prose style and produce style reference files. Use when creating, updating, or evaluating style files: the reference documents that capture a project's voice patterns for writer and critic agents.
documentation191
story-context
Context scoping for writing agent spawns: use when deciding what context a spawned agent should receive, whether ephemeral story decisions should be materialized before handoff, and how much to pass. Poor context handoffs cause writers to invent contradictions and critics to miss relevant history.
testing191
scene-construction
How to build scenes: entry, dialogue, pacing, transitions. Use when writing or evaluating how scenes work on the page.
development191
cw/skills/scene-construction
How to build scenes: entry, dialogue, pacing, transitions. Use when writing or evaluating how scenes work on the page.
development191
cw/skills/prose-writing
Prose-level immersion patterns for narrative fiction. Use when writing or revising prose: the sentence-level and paragraph-level craft that pulls readers into the story. Project-specific voice comes from style files passed alongside this skill.
testing191
cw/skills/story-context
Context scoping for writing subagents: use when deciding what context a subagent should receive. Poor context handoffs cause writers to invent contradictions and critics to miss relevant history.
testing191
cw/skills/writing-staffing
Team composition for writing workflows: which subagents to use, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, staffing draft/revise loops, or setting up brainstorm fan-outs.
data-ai191
cw/skills/writing-principles
What fiction readers want (four reward channels) and the specific ways LLM training damages each one. Load when drafting prose, critiquing, or diagnosing why a passage feels flat.
testing191
cw/skills/story-architecture
Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.
development191
cw/skills/style-analysis
How to analyze prose style and produce style reference files. Use when creating, updating, or evaluating style files: the reference documents that capture a project's voice patterns for writer and critic agents.
documentation191
cw/skills/shared-dao
Shared vocabulary for creative writing projects. Load when establishing canonical story terms, resolving ambiguous names, checking term consistency, or deciding where vocabulary belongs in kb/.
testing191
cw/skills/kb-management
Maintaining the story knowledge base: creating, updating, and organizing wiki-style reference pages in kb/. Use when capturing finalized story knowledge, updating character profiles, documenting world mechanics, or restructuring the kb.
documentation191
writing-artifacts
Where writing artifacts live: kb for durable knowledge, work directory for scratch. Use when deciding where to read from or write to.
testing191
cw/skills/brainstorming
Story brainstorming capture: minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities.
data-ai191
cw/skills/writing-artifacts
Where writing artifacts live: kb/ for durable knowledge, work/ for scratch. Use when deciding where to read from or write to.
testing191
cw/skills/project-setup
One-time project setup for creative writing. Interviews you about your project, collects writing samples, proposes kb structure, and creates CLAUDE.md with project conventions.
tools191
cw/skills/writing-issues
Logging and referencing writing issues: craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review. Use when a pattern worth tracking is identified: repeated tics, inconsistencies across scenes, structural problems that need the author's attention.
testing191
llm-writing
Load when producing any written artifact for humans.
testing191
wiki-docs
Encyclopedic reference documentation for fictional worlds — wiki pages, character profiles, lore entries. Use when creating or updating reader-facing reference pages. Covers link discipline, citation conventions, and mermaid relationship diagrams. Distinct from the knowledge base, which is author/agent-facing knowledge.
testing150
story-decisions
Story decision capture and mining — recording what was decided, what was rejected, and why, inline with the artifacts they relate to. Use whenever story direction is being chosen, brainstorm options are being narrowed, character or world choices are being made, or past decisions need to be recovered from session history.
testing133
knowledge-graph
Project document navigation. Use when you need to understand how documents connect, find related content, identify orphaned pages, or orient on a project's structure before doing other work.
documentation133
mermaid
Rules and validation for Mermaid diagrams. Use when creating or editing Mermaid diagrams in documentation.
documentation133
orchestrate
Shared coordination model for writing orchestrators — delegation discipline, convergence loops, critique synthesis, and artifact persistence. Load when you coordinate work across multiple spawns rather than producing content directly.
testing133
orchestrate
Shared coordination model for writing orchestrators — delegation discipline, convergence loops, critique synthesis, and artifact persistence. Load when you coordinate work across multiple spawns rather than producing content directly.
testing133
wiki-docs
Encyclopedic reference documentation for fictional worlds — wiki pages, character profiles, lore entries. Use when creating or updating reader-facing reference pages. Covers link discipline, citation conventions, and mermaid relationship diagrams. Distinct from the knowledge base, which is author/agent-facing knowledge.
testing133
story-decisions
Story decision capture and mining — recording what was decided, what was rejected, and why, inline with the artifacts they relate to. Use whenever story direction is being chosen, brainstorm options are being narrowed, character or world choices are being made, or past decisions need to be recovered from session history.
testing133
cw-router
Quick guide to choosing the right creative writing skill or agent. Use when you need help deciding which skill to load or which agent to spawn for a specific task — brainstorming vs documentation, critique vs writing, analysis vs architecture, etc.
testing128
cw-style-skill-creator
Creative writing skill for creating style skills that teach Claude to write in specific styles. Use when you want to create style guides that the cw-prose-writing skill can follow. Creates either simple markdown files or full .skill packages. Audience is AI (Claude), format is directive and example-based.
development100
cw-router
Quick guide to choosing the right creative writing skill. Use when you need help deciding which creative writing skill to use for a specific task - brainstorming vs documentation, critique vs writing, etc.
testing100
cw-brainstorming
Creative writing skill for capturing story brainstorming. Use when the user is exploring narrative ideas, discussing characters, planning episodes, or thinking through story possibilities. Creates minimal working notes that preserve creative freedom by recording only what was stated and marking sources.
data-ai100
cw-prose-writing
Creative writing skill for drafting and editing narrative fiction prose. Use when writing new scenes, chapters, or dialogue, or when editing existing prose. Discovers and follows project-specific style guides, character voice conventions, and formatting preferences.
development100
cw-story-critique
Creative writing skill for analyzing and critiquing story content. Use when the user requests feedback, critique, or analysis of their writing. Provides balanced feedback calibrated to intended audience.
content-media100
cw-official-docs
Creative writing skill for creating canonical reference documentation (wikis) for fictional worlds, characters, and story events. Use when creating or updating wiki pages, official documentation, character profiles, location documentation, or lore pages. Creates polished, sourced, encyclopedic reference material.
testing100
meridian-spawn
Multi-agent coordination via the meridian CLI. Use this skill whenever you need to delegate work to another agent, run tasks in parallel, check on spawn progress, coordinate multiple agents, or inspect spawn outputs. Also use when you want to route work to a specific model or provider.
tools
meridian-work-coordination
Meridian work lifecycle and artifact placement. Use this whenever you need to create, switch, update, or complete a work item, or decide where work-scoped notes versus broader shared docs belong.
testing
meridian-cli
Mental model and principles for the meridian and mars CLIs. Use when an agent needs to discover what meridian can do, learn a subcommand, diagnose a failure, or understand why meridian behaves the way it does. Points at `meridian --help` and `meridian mars --help` as the canonical reference rather than duplicating them.
tools
story-architecture
Arc structure, narrative design, and pacing at multiple scales — saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals. Not prescriptive about methodology.
development
skill-creator
Author, edit, review, split, or refactor meridian skill files — the SKILL.md files with YAML frontmatter that live under `skills/<name>/` in a source submodule and carry reference material loaded into agents on demand. Load this skill whenever you're writing a skill from scratch, updating a SKILL.md body, adding or reorganizing `resources/`, splitting a long skill into variants, or deciding whether something should be a skill at all. Phrases that should trigger this skill: "write a skill", "create a skill", "add resources to this skill", "the SKILL.md needs updating", "split this skill", "this skill is too long", "refactor this skill's description".
development
prose-writing
Prose drafting technique for narrative fiction. Use when writing new scenes, chapters, or dialogue — whether in conversation with an author or producing a draft autonomously from a brief. Covers craft fundamentals; project-specific voice comes from style files passed alongside this skill.
testing
prose-writing
Prose drafting technique for narrative fiction. Use when writing new scenes, chapters, or dialogue — whether in conversation with an author or producing a draft autonomously from a brief. Covers craft fundamentals; project-specific voice comes from style files passed alongside this skill.
testing
prose-critique
Adversarial reading methodology for narrative fiction — find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
testing
prose-analysis
Mechanical prose metrics — sentence length, opener variety, dialogue ratio, repetition, pronoun distribution. Use when you need quantitative signals about prose before making subjective judgments, or when comparing a draft against the project's baseline.
data-ai
mermaid
Rules and validation for Mermaid diagrams. Use when creating or editing Mermaid diagrams in documentation.
documentation
meridian-work-coordination
Meridian work lifecycle and artifact placement. Use this whenever you need to create, switch, update, or complete a work item, or decide where work-scoped notes versus broader shared docs belong.
testing
meridian-spawn
Multi-agent coordination via the meridian CLI. Use this skill whenever you need to delegate work to another agent, run tasks in parallel, check on spawn progress, coordinate multiple agents, or inspect spawn outputs. Also use when you want to route work to a specific model or provider.
tools
meridian-privilege-escalation
How to escalate agent permissions in meridian when a spawn hits capability limits — sandbox tiers, approval modes, model/harness switching, and per-spawn overrides. Use when a spawned agent fails because of sandbox restrictions, missing tools, harness limitations, or insufficient permissions, and you need to change the spawn configuration to unblock it.
tools
knowledge-graph
Project document navigation. Use when you need to understand how documents connect, find related content, identify orphaned pages, or orient on a project's structure before doing other work.
documentation
knowledge-graph
Project document navigation. Use when you need to understand how documents connect, find related content, identify orphaned pages, or orient on a project's structure before doing other work.
documentation
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
development
agent-creator
Author, edit, review, or refactor meridian agent profiles — the markdown files with YAML frontmatter that live in an `agents/` directory and define reusable spawn configurations (model, system prompt, tools, permissions, skills). Load this skill whenever you're writing an agent from scratch, tweaking an existing profile, splitting one agent into several, reviewing an agent for quality, or deciding whether something should be an agent at all. Phrases that should trigger this skill: "write an agent", "create a profile", "edit this agent", "add a reviewer agent", "refactor the coder agent", "this agent's prompt needs work", "add tools to this profile", "tighten up this agent's description".
tools
brainstorming
Story brainstorming capture — minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities. Supports interactive conversation and autonomous report mode for fan-out exploration.
data-ai
writing-artifacts
Shared artifact convention between orchestrators — what goes where in `$MERIDIAN_FS_DIR/` and `$MERIDIAN_WORK_DIR/`, how artifacts flow between phases, and what each directory means. Use whenever work artifacts, style files, knowledge entries, drafts, or critique reports are being created, referenced, or discussed.
development
meridian-privilege-escalation
How to escalate agent permissions in meridian when a spawn hits capability limits — sandbox tiers, approval modes, model/harness switching, and per-spawn overrides. Use when a spawned agent fails because of sandbox restrictions, missing tools, harness limitations, or insufficient permissions, and you need to change the spawn configuration to unblock it.
tools
brainstorming
Story brainstorming capture — minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities. Supports interactive conversation and autonomous report mode for fan-out exploration.
data-ai
agent-creator
Author, edit, review, or refactor meridian agent profiles — the markdown files with YAML frontmatter that live in an `agents/` directory and define reusable spawn configurations (model, system prompt, tools, permissions, skills). Load this skill whenever you're writing an agent from scratch, tweaking an existing profile, splitting one agent into several, reviewing an agent for quality, or deciding whether something should be an agent at all. Phrases that should trigger this skill: "write an agent", "create a profile", "edit this agent", "add a reviewer agent", "refactor the coder agent", "this agent's prompt needs work", "add tools to this profile", "tighten up this agent's description".
tools
meridian-cli
Mental model and principles for the meridian and mars CLIs. Use when an agent needs to discover what meridian can do, learn a subcommand, diagnose a failure, or understand why meridian behaves the way it does. Points at `meridian --help` and `meridian mars --help` as the canonical reference rather than duplicating them.
tools
prose-critique
Adversarial reading methodology for narrative fiction — find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
testing
story-context
Context scoping for writing agent spawns — use when deciding what context a spawned agent should receive, whether ephemeral story decisions should be materialized before handoff, and how much to pass. Poor context handoffs cause writers to invent contradictions and critics to miss relevant history.
testing
story-context
Context scoping for writing agent spawns — use when deciding what context a spawned agent should receive, whether ephemeral story decisions should be materialized before handoff, and how much to pass. Poor context handoffs cause writers to invent contradictions and critics to miss relevant history.
testing
story-architecture
Arc structure, narrative design, and pacing at multiple scales — saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals. Not prescriptive about methodology.
development
wiki-docs
Encyclopedic reference documentation for fictional worlds — wiki pages, character profiles, lore entries. Use when creating or updating reader-facing reference pages. Covers link discipline, citation conventions, and mermaid relationship diagrams. Distinct from $MERIDIAN_FS_DIR/ which is author/agent-facing knowledge.
testing
wiki-docs
Encyclopedic reference documentation for fictional worlds — wiki pages, character profiles, lore entries. Use when creating or updating reader-facing reference pages. Covers link discipline, citation conventions, and mermaid relationship diagrams. Distinct from $MERIDIAN_FS_DIR/ which is author/agent-facing knowledge.
testing
mermaid
Rules and validation for Mermaid diagrams. Use when creating or editing Mermaid diagrams in documentation.
documentation
prose-analysis
Mechanical prose metrics — sentence length, opener variety, dialogue ratio, repetition, pronoun distribution. Use when you need quantitative signals about prose before making subjective judgments, or when comparing a draft against the project's baseline.
data-ai
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
development
skill-creator
Author, edit, review, split, or refactor meridian skill files — the SKILL.md files with YAML frontmatter that live under `skills/<name>/` in a source submodule and carry reference material loaded into agents on demand. Load this skill whenever you're writing a skill from scratch, updating a SKILL.md body, adding or reorganizing `resources/`, splitting a long skill into variants, or deciding whether something should be a skill at all. Phrases that should trigger this skill: "write a skill", "create a skill", "add resources to this skill", "the SKILL.md needs updating", "split this skill", "this skill is too long", "refactor this skill's description".
development
story-decisions
Story decision capture and mining — recording what was decided, what was rejected, and why, inline with the artifacts they relate to. Use whenever story direction is being chosen, brainstorm options are being narrowed, character or world choices are being made, or past decisions need to be recovered from session history.
testing
writing-artifacts
Shared artifact convention between orchestrators — what goes where in `$MERIDIAN_FS_DIR/` and `$MERIDIAN_WORK_DIR/`, how artifacts flow between phases, and what each directory means. Use whenever work artifacts, style files, knowledge entries, drafts, or critique reports are being created, referenced, or discussed.
development
story-decisions
Story decision capture and mining — recording what was decided, what was rejected, and why, inline with the artifacts they relate to. Use whenever story direction is being chosen, brainstorm options are being narrowed, character or world choices are being made, or past decisions need to be recovered from session history.
testing
writing-issues
Logging and referencing writing issues — craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review. Use when an agent identifies something worth tracking beyond a single critique report: repeated tics across chapters, inconsistencies that affect multiple scenes, structural problems that need the author's attention, or patterns that should be fixed in revision.
testing
writing-issues
Logging and referencing writing issues — craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review. Use when an agent identifies something worth tracking beyond a single critique report: repeated tics across chapters, inconsistencies that affect multiple scenes, structural problems that need the author's attention, or patterns that should be fixed in revision.
testing
writing-principles
What fiction readers actually want, framed as four composable reward channels (transportation, aesthetic, social simulation, flow), and the specific documented ways alignment training damages each one. Grounded in reader-psychology research and empirical NLP findings. Load when drafting prose, critiquing a draft, deciding whether to show or tell, diagnosing why a passage feels flat, or reasoning about why a scene is or isn't working.
testing
writing-principles
What fiction readers actually want, framed as four composable reward channels (transportation, aesthetic, social simulation, flow), and the specific documented ways alignment training damages each one. Grounded in reader-psychology research and empirical NLP findings. Load when drafting prose, critiquing a draft, deciding whether to show or tell, diagnosing why a passage feels flat, or reasoning about why a scene is or isn't working.
testing
writing-staffing
Team composition for writing workflows — which agents to spawn, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, dispatching researchers, staffing draft/revise loops, or setting up brainstorm fan-outs.
data-ai
writing-staffing
Team composition for writing workflows — which agents to spawn, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, dispatching researchers, staffing draft/revise loops, or setting up brainstorm fan-outs.
data-ai