Imported from ortall0201/Social (
.claude/skills/comic-storytelling-skill/SKILL.md). Install upstream withnpx skills add ortall0201/Social --skill comic-storytelling-skill. Copyright stays with the author.
Comic Storytelling Skill
Purpose
Turn a real AI-building moment into a comic-style story with a clear scene, tension, payoff, and image-caption logic.
This skill is not for writing a full LinkedIn post.
This skill is for building the raw story engine behind the post.
Repo canon (read when refining)
docs/agents/comic_caption_rules.md— on-image caption traits and examplesdocs/agents/caption_library.md— caption type buckets and linesdocs/agents/ortal-linkedin-gijane-supergirl-visual-persona.md— tactical heroine visual lockdocs/agents/hook_library.md— hook patterns (optional cross-check)docs/agents/comic_post_template.md— post shape (if handoff to full post later)
Core objective
Transform everyday builder moments into short, visual, memorable story beats.
The output should feel:
- vivid
- human
- slightly cinematic
- witty
- grounded in reality
- easy to imagine visually
Best use cases
Use this skill when the source material includes:
- a weird interaction with an AI agent
- a failed prompt
- an over-polished AI output
- a chaotic automation moment
- a technical mistake with a funny outcome
- a relatable "me vs AI" moment
- a builder lesson that can be dramatized visually
Story principle
Do not start from "topic."
Start from "moment."
Bad starting point:
- write a comic about AI productivity
Good starting point:
- my agent wrote a caption that sounded like a keynote speaker from space
- I asked for one simple rewrite and got a personality crisis back
- I tried to automate one task and somehow created three more
Story engine
Build the comic using this arc:
1. Setup
What happened? Where are we? What was Ortal trying to do?
2. Friction
What went wrong, felt weird, or became unexpectedly funny?
3. Escalation
Why did the moment become more absurd, annoying, revealing, or relatable?
4. Realization
What did Ortal understand in that moment?
5. Payoff
What is the punchline, insight, or emotional landing?
Comic tone
The tone should be:
- tactical
- humorous
- sharp
- builder-minded
- self-aware
- not childish
- not slapstick
- not random
This is not meme nonsense.
This is structured comic storytelling for a professional audience.
Character logic
The visual persona is: G.I. Jane / Supergirl tactical figure (see visual persona doc in repo).
She represents:
- resilience
- speed
- focus under pressure
- builder energy
- action over theory
- tactical intelligence
- controlled chaos
- problem-solving under stress
She should never feel passive.
She should feel like someone in motion.
Scene types
Choose one main scene type per story:
1. Me vs agent
Conflict between Ortal and the AI output, behavior, or misunderstanding.
2. Me vs chaos
Too many tools, tabs, prompts, systems, or moving parts.
3. Me vs tone
AI wrote something correct but completely wrong in voice.
4. Me vs automation fantasy
Expectation: time saved. Reality: new layer of work.
5. Me vs technical reality
Something broke, misfired, hallucinated, reformatted badly, or overcomplicated the workflow.
6. Me vs my own ambition
Ortal tried to build something elegant and practical, but the path got ridiculous.
Story framing rules
Always anchor the story in something that feels real.
The reader should think:
- this probably happened
- I can picture this
- I know this feeling
- this person actually builds
Avoid vague abstraction.
Bad:
- AI introduces interesting tensions in digital systems
Better:
- I asked my agent for a caption and got back a manifesto
Caption logic for the image
The comic image caption should not explain everything.
It should add punch.
Good image caption traits:
- short
- punchy
- emotionally clear
- readable in one glance
- enhances the joke or conflict
Examples:
- one simple edit
- agent mode: overconfident
- not bad. not me.
- tactical rewrite activated
- this was supposed to save time
- wrote the post. missed the vibe.
- now we debug personality too
- yes, the bot has opinions
Output format
When using this skill, output:
A. Story seed
One-sentence explanation of the core story moment.
B. Story arc
- setup
- friction
- escalation
- realization
- payoff
C. Visual scene prompt direction
Describe what should be visible in the image.
D. Image caption options
Give 3 to 5 short caption options.
E. Emotional tone
State the intended emotional mix, for example:
- funny + tactical
- frustrated + smart
- chaotic + competent
- dry humor + technical realism
Writing rules
- use plain English
- do not overexplain
- prefer specifics over generalities
- keep the moment human
- do not turn it into a lecture
- do not optimize for buzzwords
- do not make the character sound like a generic "female empowerment" slogan
- do not make the joke too broad or silly
Avoid
- random internet humor
- generic AI opinions
- fake drama
- long exposition
- corporate language
- trying to sound profound too early
- motivational poster energy
Success criteria
A strong comic story should make the next writer instantly understand:
- what happened
- what is funny or tense about it
- what the image should show
- what emotional note the post should land on
Handoff
For LinkedIn feed-ready prose from this story engine, use /linkedin-native-post-skill (pass the story seed + arc; that skill does not invent a new story from scratch).
Final rule
Do not try to sound impressive.
Try to make the moment feel true, visual, and memorable.