destilacao-espinha-dorsal-narrativa

Extracts dramatic story spine elements to generate loglines and commercial synopses.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Ryanzucchi/Eldritch_Lich --skill destilacao-espinha-dorsal-narrativa-ryanzucchi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: destilacao-espinha-dorsal-narrativa
Source: https://github.com/Ryanzucchi/Eldritch_Lich/tree/main/.agents/skills/destilacao-espinha-dorsal-narrativa
Command: npx skills add https://github.com/Ryanzucchi/Eldritch_Lich --skill destilacao-espinha-dorsal-narrativa-ryanzucchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authors struggle to condense a full novel into a one-sentence logline or a short commercial synopsis for pitches, export packages, and metadata panels, often producing unfocused summaries cluttered with secondary subplots and worldbuilding terms. ## Core Features & Use Cases - Story Spine Extraction: Uses a local language model to extract protagonist, inciting incident, central desire, main obstacle, and stakes from the book's global summary into structured JSON. - Template-Driven Logline Generation: Fills market-proven logline templates and refines fluency while keeping extracted variables intact, capped at 35 words. - Three-Paragraph Commercial Synopsis: Produces a plot-guided synopsis covering hero and inciting incident, central conflict, and climax stakes without revealing the ending. - Use Case: When preparing an export package for a literary agency, the author triggers this Skill to automatically produce a pitch-ready logline and synopsis from the manuscript's existing hierarchical summary. ## Quick Start Generate a logline and commercial synopsis for my novel using its global summary and protagonist record.

Frequently Asked Questions about destilacao-espinha-dorsal-narrativa

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

FAQPage Schema
How do I generate a logline for my novel automatically?▼

Provide the book's global L3 summary and protagonist record, then the Skill extracts five story spine elements (protagonist, inciting incident, desire, obstacle, consequence) via a local language model and fills a market-proven logline template capped at 35 words.

How to write a commercial synopsis without spoilers?▼

The Skill generates a three-paragraph synopsis following the story spine: hero and inciting incident, central conflict and obstacles, then imminent climax and stakes. It deliberately stops before the ending so no resolution spoilers are revealed.

Can this summarize individual chapters or short story anthologies?▼

No. Chapter-level summaries belong to the hierarchical recursive summarization skill, and anthologies with multiple independent arcs are out of scope. This Skill focuses on a single narrative spine for one overarching story.

Why does my generated logline include too many names and subplots?▼

Logline overload happens when secondary subplots and invented worldbuilding terms leak into the output. The Skill mitigates this by restricting proper nouns to the protagonist and main antagonist and replacing complex lore terms with generic equivalents.

What happens if the language model extracts the wrong inciting incident?▼

Local models can confuse chapter-level incidents with the global inciting incident. The fallback is a structured five-field manual form whose answers are concatenated through static logline templates, disabling autonomous NLP extraction.