narrative-writer

Converts ordered canon beats into a continuous, present-tense prose narrative.

178|18|Updated May 3, 2026
One-click install
npx skills add https://github.com/UfukNode/Noustiny --skill narrative-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: narrative-writer
Source: https://github.com/UfukNode/Noustiny/tree/main/hermes-additions/skills/creative/narrative-writer
Command: npx skills add https://github.com/UfukNode/Noustiny --skill narrative-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms an ordered canon spine into a single, publishable prose read with consistent voice and seamless transitions.

Core Features & Use Cases

  • Converts a root-to-head canon into flowing prose written in present tense.
  • Maintains tonal continuity and motif carry-through across beats for a cohesive final read.
  • Produces publishable prose output suitable for readings or publication, not JSON or tool calls.

Quick Start

Provide the seed and ordered canon beats, then request a single continuous prose read.

Frequently Asked Questions about narrative-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert ordered canon beats into a continuous prose narrative?

Yes, narrative prose rendering maintains tonal continuity and motif carry-through across all beats. This ensures a cohesive final read suitable for publication rather than disjointed scene summaries.

What do I need to provide to generate present-tense prose from my canon?

The prose output is pure text written in present tense without any JSON, code blocks, or tool calls. It is designed specifically for readings or final publication, not technical parsing.

How do I maintain tonal continuity when converting a canon spine into prose?

Maintaining tonal continuity happens automatically during the root-to-head canon conversion. The rendering process applies consistent voice and seamless transitions across all beats for a cohesive final read.

Best way to turn a root-to-head canon into publishable prose without formatting artifacts?

The best way is to use a dedicated prose rendering process that outputs pure text. This approach converts your ordered canon spine directly into a flowing read, entirely avoiding JSON or code artifacts.