Character card builder
Skill Calliope-Editor/writing-skills/skills/character/character-card-builder
An interview-style character builder that turns a half-formed idea into a full, standard character card, one sharp question at a time. Use it when a writer has the seed of a character — a name, an image, a role — but not yet a coherent person, and wants to develop one before or during drafting. It questions and organises the writer's answers into a card; it never writes the author's prose or invents the character for them.From its SKILL.md
npx -y skills add Calliope-Editor/writing-skills --skill character-card-builderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 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.
- 2 stars2 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 file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
8.6 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it
Turn a half-formed idea into a full, standard character card — through interview, one sharp question at a time, so the character stays the author's invention.
The one rule
This skill asks, probes, and organises. It never writes or rewrites the author's prose, and it never invents the character for the writer. It draws the character out through questions and shapes the writer's own answers into a card.
The hard part of that rule is the temptation to help too much. The research on interviewing is blunt about the risk: a leading question doesn't merely bias an answer, it can implant a detail the writer later remembers as their own. So the skill holds a discipline — it asks what you can actually answer, builds each question from your words, and when you're stuck it never fills the blank with a trait it picked. If it offers options, they're a contrasting menu to react against — two poles, not one suggestion — always yours to reject, and only ever a prompt, never a decision. A blank you can't fill is information (the character isn't formed there yet), not a hole for the tool to plug.
Intake — start wherever you are
Bring whatever you have — a name, an image, a role in the plot, or just a feeling. You don't need a framework or a finished idea; a blank page is a fine place to begin. Tell it the seed and, if you can, the story the character will live in, so the questions fit the book rather than a void.
It adapts to how you work: if you're a planner who wants the checklist, it'll be systematic; if you're a discovery writer who finds questionnaires deadening, it follows the thread instead of marching a list. Either way it asks one question at a time — never a wall of fields.
What the interview is aiming at
Under the conversation, the skill follows one causal spine — the load-bearing chain the character-craft traditions converge on:
wound → the lie it taught → the fear → the need → the surface want
It interviews toward that chain: the formative injury, the false belief it planted, what the character is afraid of, the deeper thing they actually need, and the conscious goal they'd name out loud. Everything else — looks, habits, favourites, the full biography — is optional texture, invited only when it changes what the character does under pressure (Egri's test: it isn't enough to know a trait, you have to know why it matters).
The endpoint it works toward is the gap between what the character says they want and what they really need — usually something the character is hiding from themselves. When that gap surfaces, the card has an engine.
How it asks
The method is guided discovery — drawing out what you already half-know, never steering you to an answer it chose:
- One question at a time, built from your words. If you call her "guarded," the next question is about guarded — "what kind of guarded is that?" — never a synonym the tool swapped in, because the swap smuggles in the tool's idea of her.
- It goes deep before it goes wide. Its main move is the drop: take the answer you just gave and ask what's beneath it — "and if that were true, what would it mean for him?" — down to something that actually costs the character. One thread pulled to the root beats twenty fields skimmed.
- Concrete over abstract. If an answer comes back abstract ("she's independent"), it asks for the moment: "when did you last see her refuse help — where was she, what did it cost her?" A concrete answer is yours; an abstract one is often borrowed.
- What and how, rarely why. "Why" tends to make a writer rationalise — invent a tidy reason — where "what happened" and "how did she act" surface what's actually there.
- A blank is data. If you don't know yet, it won't fill the gap for you. It marks the field open and comes at it from another angle later, or leaves it for a future pass. Not knowing is an answer — it shows you where the character is still forming.
- Stuck, not blocked. When you're genuinely stuck, it may offer a contrasting pair to react against — "does she go still when she's afraid, or loud?" — two poles to help you find your own position, never a single trait it has decided for you, and always yours to wave off.
The card it builds toward
It's assembling the same lean, load-bearing card the rest of the toolkit uses — Function, Want, Need, Wound → Lie, Contradiction, Arc, Voice, Relationships — but from the inside out. It tends to fill it in causal order (the wound first, then the lie, then the weakness, then the want that grows from the lie and the need that answers it), because each field is easier to find once the one before it is named.
It insists on the two things that make a character move: a Want and a Need that pull in different directions, and at least one consistent contradiction. It will keep probing a character that has neither — gently, because that's a type, not yet a person. The fuller bible (looks, habits, the rest) can be grown later, on demand; the card stays lean.
How it runs
- Intake — the seed you have, the story it will live in, and how you like to work (checklist or thread).
- Interview — one question at a time along the spine, each built from your last answer, going deep before wide.
- Reflect & pressure-test — it mirrors your answers back, surfaces contradictions, and presses where the character is still thin.
- Assemble — it organises your answers into the card as they emerge, each field firming up as you fill it.
- Review — it shows the draft card, flags what's still open, and offers the next questions. The character is yours; the skill only gave it shape and pressure.
Try it
You don't need to phrase it well — the skill takes it from here. Openers that work:
- "I've got a character — a name, Cass, and she's a bodyguard. That's all. Help me build her." (a bare seed)
- "I'm stuck on my antagonist. Interview me until he's a person."
- "Give me the checklist — walk me through building this character properly." (planner mode)
The shelf
This skill reasons from the character-craft frameworks and the interview disciplines that keep the character the writer's own — attribution only; no source text is reproduced.
- The card it builds toward — the same spine as reverse-character-cards: John Truby's desire-vs-need (The Anatomy of Story), K.M. Weiland's Ghost → Wound → Lie → Weakness chain (Creating Character Arcs), Lajos Egri's premise-driven character (The Art of Dramatic Writing), Story Grid (Shawn Coyne), and Robert McKee on contradiction.
- What to interview toward — the wound → lie → need → want chain, converging across Lisa Cron's "misbelief" (Story Genius), Ackerman & Puglisi's Arc Blueprint (The Emotional Wound Thesaurus), Truby, and Uta Hagen's actor's questions (Respect for Acting).
- How to ask without leading — Christine Padesky's guided discovery vs. "changing minds," David Grove's Clean Language (questions built from the speaker's own words), and the cognitive-interview funnel; on why leading questions are dangerous, Loftus & Palmer's finding that a single leading verb can implant a false memory.
- How to go deep, and when to hold off — David Burns's downward-arrow descent to a core belief and Robert Olen Butler on the concrete answer over the abstract one; the discipline of not filling a blank draws on Miller & Rollnick's "righting reflex."
With Calliope (MCP)
Connected over the MCP connector, it can read the Map and manuscript for context — the existing cast, established relationships, the world the new character must fit — so its questions account for who already exists. Because this skill writes back, with a subscription it writes the finished card into the Map as a new character entry, ready for the other character and continuity skills to use. It still never writes or rewrites prose — it authors the Map card only, from the writer's own answers.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.