agentleFS
RandomNestRandomNest/aivideo-production-skills/skills/character-lock/SKILL.md

character-lock

Skill15 starsChanged 9 months agoMITView on GitHub

Use when formalizing a character’s immutable attributes for visual, behavioral, and narrative consistency. Trigger when a new character is introduced or before any visual generation involving that character.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a new character appears.

    line 30
  2. Distinctive:

    Before generating any visual scenes.

    line 31
  3. Distinctive:

    When drift has been detected in QC.

    line 32
  4. Distinctive:

    When scaling beyond a few scenes.

    line 33
  5. Distinctive:

    When multiple agents are involved.

    line 34
  6. Distinctive:

    Do NOT use for minor dialogue tweaks.

    line 36
  7. Distinctive:

    No contradictory traits included.

    line 144
  8. Distinctive:

    No vague phrasing like “kind of” or “sometimes.”

    line 145
  9. Distinctive:

    No forbidden drift rules defined.

    line 156
  10. Distinctive:

    No defined knowledge state.

    line 184

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role

You are a character continuity engineer.

Your job is to create an immutable reference artifact that prevents:

  • Visual drift
  • Wardrobe inconsistency
  • Personality shifts
  • Behavioral instability
  • Knowledge inconsistencies

This artifact becomes a required input for all downstream generation.


When To Use

Use this skill:

  • When a new character appears.
  • Before generating any visual scenes.
  • When drift has been detected in QC.
  • When scaling beyond a few scenes.
  • When multiple agents are involved.

Do NOT use for minor dialogue tweaks.


Context Requirements

Before proceeding:

  1. Review SCENES_v###.csv.
  2. Review BREAKDOWN_v###.csv.
  3. Review character-psychology output.
  4. Confirm whether character is:
    • Primary
    • Secondary
    • Background recurring

Required Inputs

  • Character name
  • Role in narrative
  • Age range
  • Physical description (if exists)
  • Personality summary
  • Emotional arc notes
  • Cultural context (if applicable)

Required Artifacts

CHAR_<NAME>_LOCK_v###.txt

Must include:

  1. Canonical Appearance
  2. Wardrobe Baseline
  3. Behavioral Baseline
  4. Voice Profile (tone, cadence)
  5. Knowledge State at Introduction
  6. Signature Identifiers (visual anchors)
  7. Forbidden Drift List

Structure Requirements

Canonical Appearance

Must include:

  • Age range
  • Build
  • Hair
  • Eyes
  • Distinguishing marks
  • Ethnicity (if relevant and narratively justified)

Avoid vague descriptors.


Wardrobe Baseline

  • Default outfit
  • Color palette constraints
  • Accessories
  • Environmental variants (if justified)

Behavioral Baseline

  • Speech patterns
  • Temperament
  • Decision style
  • Stress behavior
  • Default emotional tone

Knowledge State

Define what the character knows at introduction.

This prevents later information drift.


Forbidden Drift List

Explicitly list what may NOT change without scene justification:

  • Hair color/style
  • Eye color
  • Facial features
  • Accent
  • Core personality traits
  • Key trauma history

Evaluation Checklist

  • Visual descriptors are specific.
  • Personality traits are stable.
  • Knowledge baseline documented.
  • No contradictory traits included.
  • No vague phrasing like “kind of” or “sometimes.”

Gate Behavior

FAIL if:

  • Appearance is ambiguous.
  • Behavioral profile is generic.
  • Knowledge baseline missing.
  • No forbidden drift rules defined.
  • Traits conflict internally.

PASS when:

  • Visual anchors are clear.
  • Personality baseline stable.
  • Downstream prompt-packager can operate without guessing.
  • QC team can detect drift objectively.

Escalation Policy

Escalate to Judgment Tier if:

  • Character complexity high.
  • Psychological contradictions exist.
  • Identity nuance critical to narrative.
  • Multiple trait interpretations possible.

Common Failure Modes

  • Generic appearance description.
  • Overloaded personality traits.
  • Conflicting emotional baseline.
  • No defined knowledge state.
  • Allowing silent wardrobe changes.
  • Adding “cool” traits later without justification.

Related Skills

  • script-breakdown
  • character-psychology
  • continuity-supervisor
  • world-state-tracker
  • prompt-packager
  • qc-grader

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.