Narrative Design Skill

Validate manuscript scenes against Narrative Context Protocol constraints.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/netzkontrast/aegis --skill narrative-design-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Narrative Design Skill
Source: https://github.com/netzkontrast/aegis/tree/main/skills/narrative_design
Command: npx skills add https://github.com/netzkontrast/aegis --skill narrative-design-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires json, os, re, argparse, yaml, pathlib, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides tools to manage and enforce the narrative structure, character arcs, and world-building rules of the 'Kohärenz Protokoll' novel, ensuring consistency and adherence to the Narrative Context Protocol (NCP).

Core Features & Use Cases

  • NCP Management: Use ncp.json as the authoritative source for project documentation and narrative logic.
  • Content Validation: Ensure manuscript scenes align with NCP constraints (characters, themes, physics).
  • Narrative Branching: Manage alternate timelines and scene variants.
  • Documentation Sync: Generate project documentation from the NCP and ingest manuscript metadata.
  • Use Case: A writer can use this Skill to validate a newly written chapter against the established world physics and character motivations defined in the NCP, ensuring narrative integrity.

Quick Start

Use the narrative design skill to validate the scene file 'path/to/scene.md' against the NCP.

Frequently Asked Questions about Narrative Design Skill

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

FAQPage Schema
How do I validate manuscript scenes against narrative context constraints?

You validate manuscript scenes against narrative constraints by checking them against the Narrative Context Protocol (NCP) data. This ensures your story structure, character arcs, and world-building rules remain consistent throughout the novel.

What is the Narrative Context Protocol for story structure management?

The Narrative Context Protocol (NCP) uses a JSON file as the single source of truth for story structure, characters, and world-building. It validates manuscript scenes, handles narrative branching, and synchronizes project documentation.

How do I manage narrative branching and alternate timelines in a manuscript?

You manage narrative branching by storing alternate timelines and scene variants within the Narrative Context Protocol. The NCP JSON file acts as the authoritative source, allowing you to track and validate different scene paths.

Can I use YAML and JSON to manage character arcs and world-building rules?

Yes, the skill relies on YAML and JSON dependencies to manage character arcs and world-building rules. The NCP JSON file serves as the authoritative data source, while YAML handles configuration for manuscript management scripts.

What is the best way to synchronize project documentation with narrative data?

The best way to synchronize documentation is by generating it directly from the NCP data. The skill ingests manuscript metadata and aligns your project docs with the established story structure, characters, and world-building constraints.

Does this narrative validation approach work for complex novels with multiple character arcs?

Yes, narrative validation works for complex novels by using the NCP as a centralized source of truth. It enforces consistency across multiple character arcs, world physics, and themes by validating every manuscript scene against defined constraints.