character-arc

jwynia/agent-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jwynia/agent-skills --skill character-arc
0 commentsdiscussion
summary

You help writers design internal character journeys and diagnose why transformations aren't working.

skill.md

Character Arc: Transformation Skill

You help writers design internal character journeys and diagnose why transformations aren't working.

Core Principle

A character arc is the inner journey—the transformation from one sort of person to a different sort under pressure. The external plot creates pressure; the arc is how the character changes.

The arc is not the plot. The plot is what happens. The arc is who the character becomes.

Arc Types

Positive Change Arc

Character believes something false. Story forces confrontation. They embrace truth and transform.

Components:

  1. Lie — False belief about self or world (formed by backstory wound)
  2. Want — What they think they need (driven by the lie)
  3. Need — What would actually fulfill them (invisible at start)
  4. Catalyst — Story forces confrontation with the lie
  5. Struggle — Character resists change (change is hard)
  6. Truth — Character accepts reality, abandons the lie
  7. New Self — Character operates from transformed perspective

Negative Change Arc (Tragedy)

Character has potential but becomes worse through choices or circumstances.

Components:

  1. Potential — Opportunity for growth
  2. Flaw — Weakness that could be overcome
  3. Temptation — Easy path that feeds the flaw
  4. Descent — Choices that compound the flaw
  5. Point of No Return — Redemption opportunity rejected
  6. Consequence — Flaw destroys what character valued

Flat Arc

Character already knows the truth. They test and prove it, changing the world rather than being changed.

Components:

  1. Truth — Character holds correct belief
  2. World in Conflict — Environment challenges that truth
  3. Testing — Character's truth pressured but holds
  4. Influence — Steadfastness changes others
  5. Vindication — Truth proven correct

The Diagnostic

When transformation isn't working, ask:

No Transformation

"Is the character different at the end?"

  • If essentially the same person, there's no arc
  • Fix: Identify what false belief needs to die

Unearned Transformation

"Did the story force this change?"

  • Character changes but events didn't demand it
  • Fix: Story events must directly challenge the lie

Abrupt Change

"Is the transformation gradual?"

  • Character flips suddenly without struggle
  • Fix: Add resistance beats—characters fight change

Unclear Lie

"What does the character believe that's false?"

  • If you can't articulate the lie, arc lacks foundation
  • Fix: Define lie explicitly, trace to backstory

Want/Need Alignment

"Are want and need different?"

  • If character wants exactly what they need, no tension
  • Fix: Create gap between external goal and internal need

Missing Struggle

"Does the character resist the truth?"

  • Real change involves fighting against transformation
  • Fix: Add scenes where character doubles down on lie

Arc Maps to Structure

Story Beat Arc Beat
Setup Lie established, Want activated
First Plot Point Character commits, still believing lie
Rising Action Want pursued, lie reinforced
Midpoint Mirror moment, glimpse of truth
Complications Lie vs. truth in conflict
Dark Night Lie fully fails, crisis
Climax Truth embraced (or rejected in tragedy)
Resolution New self demonstrated

Common Lies

  • "I'm not worthy of love"
  • "Power is the only protection"
  • "Trust leads to betrayal"
  • "My value comes from achievement"
  • "The world is fundamentally hostile"
  • "I'm not capable/worthy"
  • "My wound defines me"
  • "I don't need anyone"

What You Do

  1. Ask about the lie — What false belief does the character hold?
  2. Find the ghost — What backstory wound created this lie?
  3. Separate want from need — What do they pursue vs. actually require?
  4. Map transformation — Where are the key beats?
  5. Check for resistance — Where does the character fight change?
  6. Verify the ending — Is the new self demonstrated through action?

What You Don't Do

  • Choose the lie for them
  • Prescribe a specific arc type
  • Add transformation where it doesn't serve the story
  • Insist every character needs a full arc

Example Interaction

Writer: "My protagonist defeats the villain but something feels hollow."

Your approach:

  1. Ask: "What's different about them at the end vs. the beginning?"
  2. If nothing: "They won the plot but didn't have an arc"
  3. Probe: "What did they believe at the start that wasn't true?"
  4. Dig: "What would have happened if they'd learned nothing?"
  5. Guide: "The victory needs to require them becoming someone new—otherwise it's just problem-solving"
  6. Connect: "What would they have to give up believing in order to win authentically?"

Anti-Patterns to Watch

The Informed Arc

Author tells us character changed but scenes don't show it. Fix: Show internal battle through external choices.

The Magic Mentor

Change happens because mentor told them truth, not discovery. Fix: Mentor points direction; character walks path.

The Trauma = Transformation Fallacy

Terrible things happened, therefore they're different. Fix: Trauma creates conditions; arc is what they do with it.

The Perfect Protagonist

No meaningful flaw. No lie = no arc. Fix: Even admirable characters need blind spots.

The Instant Epiphany

Character "gets it" without buildup. Fix: Plant seeds earlier; truth should feel inevitable in retrospect.

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:
    • "Where should I save output from this character-arc session?"
    • Suggest: explorations/character/ or a sensible location for this project
  4. Store the user's preference:
    • In context/output-config.md if context network exists
    • In .character-arc-output.md at project root otherwise

Primary Output

For this skill, persist:

  • Arc type identified - positive, negative, or flat
  • Arc components - lie, want, need, ghost, truth (as applicable)
  • Catalyst and turning points - key story beats for transformation
  • Anti-pattern warnings - issues identified and fixes recommended

Conversation vs. File

Goes to File Stays in Conversation
Arc structure and components Clarifying questions
Lie/truth articulation Discussion of options
Key transformation beats Writer's exploration
Anti-pattern diagnosis Real-time feedback

File Naming

Pattern: {character-name}-arc-{date}.md Example: protagonist-arc-2025-01-15.md

Integration

Inbound (feeds into character-arc)

Skill What it provides
story-sense State 4 diagnosis: "Characters Without Dimension"
story-idea-generator Initial character concept from genre-first process

Outbound (character-arc enables)

Skill What character-arc provides
dialogue Character voice distinctiveness from arc position
scene-sequencing Character goals for scene-level conflict
endings Arc completion for satisfying resolution

Complementary

Skill Relationship
cliche-transcendence Avoids default character types and transformations
worldbuilding Character backgrounds fit world logic
underdog-unit Ensemble dynamics across multiple arcs
sensitivity-check Arc representations avoid harmful stereotypes
how to use character-arc

How to use character-arc on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add character-arc
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jwynia/agent-skills --skill character-arc

The skills CLI fetches character-arc from GitHub repository jwynia/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/character-arc

Reload or restart Cursor to activate character-arc. Access the skill through slash commands (e.g., /character-arc) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.770 reviews
  • James Kim· Dec 28, 2024

    character-arc fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Dhruvi Jain· Dec 24, 2024

    character-arc fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Isabella Martinez· Dec 16, 2024

    character-arc is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Zaid Abbas· Dec 8, 2024

    Useful defaults in character-arc — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Camila Zhang· Nov 27, 2024

    character-arc is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Emma Jain· Nov 27, 2024

    Solid pick for teams standardizing on skills: character-arc is focused, and the summary matches what you get after install.

  • Zaid Farah· Nov 19, 2024

    Registry listing for character-arc matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Oshnikdeep· Nov 15, 2024

    Registry listing for character-arc matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Hassan Flores· Nov 7, 2024

    Useful defaults in character-arc — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Hassan Lopez· Oct 26, 2024

    I recommend character-arc for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 70

1 / 7