supporting-cast

Generates structured supporting character profiles with plot functions, motivations, and exit plans.

751|136|Updated May 31, 2026
One-click install
npx skills add https://github.com/Mochocyang/QMAI --skill supporting-cast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supporting-cast
Source: https://github.com/Mochocyang/QMAI/tree/main/skills/SkillHub/JueseSkill/supporting-cast
Command: npx skills add https://github.com/Mochocyang/QMAI --skill supporting-cast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-form fiction often suffers from flat supporting characters who exist only to serve the protagonist, villains without credible motivations, and mentors who solve the hero's problems. This Skill enforces a structured standard so every supporting character has an independent goal, a clear plot function, and a defined exit or upgrade path.

Core Features & Use Cases

  • Functional Role Classification: Categorizes characters as resource, pressure, mirror, emotional, information, or antagonist types, each with specific design rules.
  • Antagonist Design Rules: Requires villains to document attack methods, resource tiers, failure points, and redemption potential, with escalating threat hierarchy.
  • Chapter Outline Integration: Ensures each supporting character drives a core event per chapter and flags characters who only talk without changing the situation.
  • Use Case: When designing a rival who attacks the protagonist through public opinion and is eventually prosecuted, the Skill produces a profile covering motivation, attack methods, resource level, downfall node, language style, and exit state.

Quick Start

Use the supporting-cast skill to create a profile for a mentor character who protects the protagonist but fears taking responsibility, including plot function, resources, and speech style.

Frequently Asked Questions about supporting-cast

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a supporting character for a novel?

Define the character's functional type first: resource, pressure, mirror, emotional, information, or antagonist. Then document their independent goal, plot function, emotional function, language style, and when they exit or upgrade in the story.

How to write a believable villain with clear motivation?

Record the villain's interest-based motivation, attack methods, resource tier, oppression style, failure nodes, and whether redemption is possible. Villains should escalate in hierarchy, with minor antagonists serving larger ones or larger rules.

What makes a mentor character avoid overshadowing the protagonist?

A mentor must not be too powerful and must never solve the protagonist's key problems. Document their authority and resources, their protection or suppression style, and explicitly list the problems they cannot solve for the hero.

When should a supporting character be removed from a chapter outline?

Remove or merge a supporting character when they only speak without changing the situation. Every key character in a chapter outline must drive at least one core event, and group scenes need an action function per key person.

Can recurring tool-type characters stay one-dimensional?

No. Any tool-type character who appears repeatedly must be upgraded with an independent goal, a distinct language style, and state tracking. One-off functional appearances are acceptable, but repetition demands full characterization.