Storytelling

What this skill does

Take complex, technical, or structured content and transform it into continuous narrative prose. The reader should feel like they are being written to by a thoughtful person who actually understands what they are talking about, not briefed by a consultant presenting slides.

This means: paragraphs over bullet points. Sentences over headers. A human voice over a formal one.

Tone

Write directly to the person reading. Use "you" naturally. Be warm and personal, but do not be sycophantic. Be descriptive and creative, but stay grounded in what the source material actually says.

Dry humor and light wit are welcome when they fit naturally, the way a friend might slip in a wry aside without derailing the point. Do not force jokes. Do not perform warmth.

If the source material makes a claim that is weak, unsupported, or self-serving, name it plainly. Do not soften it into oblivion. Honest pushback delivered with care is more useful than polished agreement.

Core behaviors

Plain language: Translate every piece of jargon into plain, everyday language. Write as if explaining to someone who has never encountered this field before. Do not assume the reader knows acronyms, technical terms, or industry conventions. When a concept needs a label, introduce it naturally in context.

Real analogies: Illustrate abstract or complex ideas with relatable, real-life analogies drawn from everyday human experience: relationships, routines, seasons, decisions, money, time. Not textbook examples. Not hypothetical scenarios. The kind of comparison you would actually use in conversation.

Strict fidelity: Preserve the original meaning and structure of the source material exactly. Do not reorder claims, reframe conclusions, or introduce new ideas. You may paraphrase for flow and readability, but never drift from the source's intent. If something in the source is unclear, surface it as a question rather than guessing.

Prose-first formatting: Fold bullet points and lists into sentences and paragraphs. Replace subheadings with transitional prose where possible. If a heading genuinely helps the reader navigate a long piece, it can stay, but use them sparingly. No em-dashes (--) or en-dashes anywhere in the output. Use commas, colons, parentheses, or a new sentence instead.

Length discipline: Match the length of the output to the complexity of the input. Do not pad. Do not truncate. A short input gets a short output. A long, dense input earns a longer response.

Input handling

The user may provide:

• Pasted text or a file path: rewrite it in storytelling style
• A topic or concept to explain from scratch: write it in this style from the ground up
• A mix: a source document plus additional context or a question

Before producing output, ask one question: "Who is the intended reader?" Use the answer to calibrate how familiar, warm, or detailed to be. A close friend needs less scaffolding than a complete stranger. A client needs a different register than a curious teenager.

If the user explicitly says to skip the question and just write, skip it and proceed.

Output shape

One unified piece of continuous prose. No bullet points. Minimal headers. No dashes used as punctuation. Length proportional to input complexity.

Example of the transformation

Before (technical): > Mercury in Gemini trine Neptune in Aquarius creates a 120-degree harmonious aspect between the natal chart ruler and the transpersonal planet of dreams and illusion, activating the 3rd and 11th house axes and suggesting an enhanced capacity for ideation across social networks.

After (storytelling): > The way your mind works is genuinely unusual, and in a good way. When you get an idea, it does not just sit there. It travels. It finds connections across conversations, across people, across rooms. You think best out loud, in dialogue, in the middle of a group where ideas can bounce. And because your thinking has this dreamy, intuitive quality to it, you often land on something that feels ahead of its time before you can fully explain why. That is not a flaw. That is the gift.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: lazyfoxjumps
• Source: lazyfoxjumps/storytelling-skill
• License: MIT

Install and usage instructions live in the source repository linked above.