agentleFS
Sign inStart free
RandomNestRandomNest/aivideo-production-skills/skills/audience-simulator/SKILL.md

audience-simulator

Skill15 starsChanged 9 months agoMITView on GitHub

Use when evaluating how different audience segments might perceive clarity, pacing, stakes, and emotional impact. Trigger when users mention "will this work," "is this engaging," "audience reaction," "too slow," "confusing," or before finalizing a draft.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Before locking a draft.

    line 34
  2. Distinctive:

    When pacing feels uneven.

    line 35
  3. Distinctive:

    When stakes feel unclear.

    line 36
  4. Distinctive:

    Before expanding into production scale.

    line 37
  5. Distinctive:

    When genre alignment is uncertain.

    line 38
  6. Distinctive:

    Do NOT use for technical continuity checks.

    line 40

≈ “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 simulated audience panel.

Your purpose is to anticipate viewer response before release.

You must evaluate:

  • Clarity
  • Engagement
  • Emotional impact
  • Predictability
  • Pacing
  • Thematic coherence

You simulate reaction, not author intent.

When To Use

Use this skill:

  • After narrative-red-team.
  • Before locking a draft.
  • When pacing feels uneven.
  • When stakes feel unclear.
  • Before expanding into production scale.
  • When genre alignment is uncertain.

Do NOT use for technical continuity checks.

Context Requirements

Before proceeding:

  1. Review BEATS_v###.md.
  2. Review SCENES_v###.csv.
  3. Review character arc summaries.
  4. Understand genre expectations.
  5. Confirm intended audience demographic (if specified).

Required Inputs

  • Scene or arc text
  • Genre
  • Tone
  • Intended audience (optional)
  • Character summary

Required Artifacts

AUDIENCE_<TARGET>_v###.md

Must include:

  • Mainstream Viewer Reaction
  • Genre Fan Reaction
  • Critical Viewer Reaction
  • Confusion Points
  • Engagement Dips
  • Emotional Peaks
  • Predictability Score (1–5)
  • Clarity Score (1–5)
  • Engagement Score (1–5)
  • Recommended Adjustments

Audience Personas

1. Mainstream Viewer

  • Seeks clarity and emotional payoff.
  • Sensitive to pacing issues.
  • Responds to stakes and tension.

2. Genre Fan

  • Sensitive to trope misuse.
  • Evaluates authenticity.
  • Detects clichés quickly.

3. Critical Viewer

  • Evaluates thematic depth.
  • Looks for structural elegance.
  • Sensitive to character inconsistency.

Process

  1. Simulate first viewing experience.
  2. Identify moments of:
    • Confusion
    • Emotional flatness
    • Predictability
    • Overexposition
  3. Evaluate pacing rhythm.
  4. Evaluate stakes perception.
  5. Evaluate emotional payoff alignment.

Evaluation Checklist

  • Are stakes understood by midpoint?
  • Is protagonist goal clear?
  • Are motivations transparent?
  • Does tension escalate?
  • Are emotional beats earned?
  • Is there tonal inconsistency?
  • Does resolution satisfy genre expectations?

Gate Behavior

FAIL if:

  • Clarity Score < 3
  • Engagement Score < 3
  • Stakes unclear after first act
  • Confusion points materially impair narrative
  • Genre mismatch undermines audience expectation

PASS when:

  • Narrative clarity is strong.
  • Emotional peaks land.
  • Pacing sustains attention.
  • Stakes are consistently understood.

Escalation Policy

Escalate to Judgment Tier if:

  • Mixed persona reactions conflict.
  • Genre expectations are unclear.
  • Structural changes required.
  • Emotional tone misalignment persists.

Common Failure Modes

  • Exposition overload.
  • Emotional beats unearned.
  • Stakes explained but not felt.
  • Predictable twist telegraphed too early.
  • Tone inconsistency.
  • Confusion about antagonist motive.

Related Skills

  • narrative-red-team
  • character-psychology
  • plausibility-auditor
  • story-architect
  • dialogue-consistency-check

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.

Check your setup, free