narrative-writing
Extract narrative structure entities from text. Use when analyzing stories, chapters, acts, episodes, prologues, epilogues, plot branches, campaigns, events, and story arc progression.
Datos de origen
- Repositorio
- bivex/loreSystem
- Última actividad en el origen
- 21 de marzo de 2026 a las 15:19
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 0
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- narrative-writing
- description
- Extract narrative structure entities from text. Use when analyzing stories, chapters, acts, episodes, prologues, epilogues, plot branches, campaigns, events, and story arc progression.
# narrative-writing
Domain skill for narrative structure extraction.
## Entity Types
| Type | Description |
|------|-------------|
| `story` | Main narrative container |
| `chapter` | Individual story chapter |
| `act` | Major story division (three-act structure) |
| `episode` | Story episode or subdivision |
| `prologue` | Introduction, backstory setup |
| `epilogue` | Conclusion, aftermath |
| `plot_branch` | Story branch or divergence |
| `branch_point` | Decision point in narrative |
| `alternate_reality` | Alternative timeline or reality |
| `consequence` | Outcome of a decision or event |
| `ending` | Story ending variant |
| `campaign` | Multi-story campaign container |
| `event` | Narrative event or incident |
| `event_chain` | Sequence of linked events |
## Extraction Rules
1. **Identify narrative structure**: Is this a new story or continuation? What act/chapter/episode?
2. **Extract hierarchy**: Stories contain acts, acts contain chapters, chapters contain episodes
3. **Track branching**: Decision points, alternative paths, multiple outcomes
4. **Link events**: Events chain together; track cause-and-effect sequences
5. **Note pacing**: Where acts break, where tension rises/falls
## Output Format
Write to `entities/narrative.json`:
```json
{
"stories": [
{
"id": 1,
"world_id": 1,
"name": "The Shadow War",
"description": "...",
"story_type": "linear",
"content": "...",
"choice_ids": [],
"connected_world_ids": [],
"is_active": true,
"created_at": "2026-02-14T10:00:00+00:00",
"updated_at": "2026-02-14T10:00:00+00:00",
"version": 1
}
],
"events": [
{
"id": 2,
"world_id": 1,
"name": "The Great Battle",
"description": "...",
"start_date": "2026-02-14T10:00:00+00:00",
"end_date": null,
"outcome": "ongoing",
"participant_ids": [3],
"created_at": "2026-02-14T10:00:00+00:00",
"updated_at": "2026-02-14T10:00:00+00:00",
"version": 1
}
],
"next_id": 3
}
```
## Key Considerations
- **Continuity**: Chapter numbers and story references must be consistent
- **Hierarchy**: All chapters reference their story; episodes reference chapters
- **Branching**: Capture all possible narrative paths at branch points
- **Events own characters by reference**: Characters mentioned in events must appear in `participant_ids`.
Ver en GitHub