Narrative craft
Plug-and-play skills and prompts for every AI coding agent
npx -y skills add Amey-Thakur/AI-SKILLS --skill narrative-craftAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Tell a story that holds attention and makes a point, through character, tension, and concrete scenes. Use when using storytelling in writing: an essay, a talk, a case study, a brand story, a personal account.
SKILL.md
2.8 KB, as published. Nobody here has run it
Narrative craft
A story sticks where a summary slides off, because the reader lives it rather than being told it. The craft is the same whether the story is a paragraph in an essay or a whole piece: a character wanting something, something in the way, and a change.
Method
- Anchor on a character who wants something. The reader connects to a person (or a stand-in: a customer, a team, "you") with a goal and a stake. Without someone to care about and something they want, you have a report, not a story. State the want early.
- Introduce tension: the obstacle. The engine of every story is a problem, conflict, or obstacle between the character and their goal. Stories without tension are announcements ("we launched, it went great"). The struggle is the interesting part; do not skip to the win.
- Show through concrete scenes, do not summarize. A specific moment (the deploy at 2am, the customer's exact words) makes the reader experience it; "we faced challenges" makes them experience nothing. Sensory, specific detail is what turns telling into showing (see writing-with-evidence's specificity, aimed at emotion).
- Build an arc: setup, turn, resolution. Establish the situation and the want, hit the turning point (the crisis, the insight, the change), land the resolution and what changed. The change is the payoff; a story where nothing shifts leaves the reader asking "so what".
- Land the point through the story, not bolted on. The meaning should emerge from what happened, felt rather than lectured. A moral stapled to the end ("and that's why teamwork matters") deflates it; trust the story to carry the point (see story-narrative prompt for applying this).
- Cut to the tension. Start close to the interesting moment, not with throat-clearing backstory. Give only the setup the payoff needs. A tight story that starts late and ends on the turn beats a complete one that meanders.
Boundaries
- Narrative is a tool for making a point memorable and felt; it serves the message, so keep it pointed, not self-indulgent. A story that does not earn its length in a working document is padding.
- Honesty binds: use real detail where you have it, mark invented illustration as such, and never fabricate a customer, quote, or event as if real (see the ethics in case-study, story-narrative).
- Not every piece wants a story; a reference, a spec, or a quick update is worse for one. Reach for narrative where emotional truth or memorability is the goal (see technical-writing for the opposite).