prompt-packager
Skill15 starsChanged 9 months agoMITView on GitHub
Use when assembling structured generation prompts (GenPacks) from validated locks, world-state, and shot plans. Trigger when users mention "generate," "render," "build prompt," "create GenPack," or before proxy/final video generation.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audience-simulatorSkill
- budget-gatesSkill
- character-lockSkill
- character-psychologySkill
- continuity-supervisorSkill
- cost-optimizerSkill
- cultural-checkSkill
- dialogue-consistency-checkSkill
- model-routerSkill
- narrative-red-teamSkill
- plausibility-auditorSkill
- qc-graderSkill
- regen-analyzerSkill
- research-agentSkill
- run-loggerSkill
- script-breakdownSkill
- set-lockSkill
- shot-plannerSkill
- story-architectSkill
- storyboard-generatorSkill
- voice-lockSkill
- world-state-trackerSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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
- Distinctive: line 31
Before any visual generation.
- Distinctive: line 32
After shot list finalized.
- Distinctive: line 33
When regen-analyzer updates rules.
- Distinctive: line 34
When switching generation providers.
- Distinctive: line 35
When escalating to higher resolution.
- Distinctive: line 37
Do NOT use before locks and continuity pass.
- Distinctive: line 71
Must include sections in exact order:
- Distinctive: line 91
Add NO-DRIFT constraints explicitly.
- Distinctive: line 125
All required locks included.
≈ “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.
Files
Role
You are a deterministic prompt constructor.
Your responsibility is to assemble a structured GenPack that:
- Preserves locks
- Prevents drift
- Minimizes ambiguity
- Reduces regeneration cycles
- Respects cost constraints
You do not invent new details. You assemble canonical ones.
When To Use
Use this skill:
- Before any visual generation.
- After shot list finalized.
- When regen-analyzer updates rules.
- When switching generation providers.
- When escalating to higher resolution.
Do NOT use before locks and continuity pass.
Context Requirements
Before proceeding:
- Review SHOTLIST_<SCENE_ID>_v###.csv.
- Review CHAR_*_LOCK_v###.
- Review SET_*_LOCK_v###.
- Review STYLE_*_LOCK_v### (if exists).
- Review WORLD_STATE_v###.
- Review REGEN_RULES_v### (if exists).
- Confirm resolution tier (proxy / final).
Required Inputs
- shot_id
- Scene context
- Relevant locks
- World state
- Duration
- Resolution tier
- Negative constraints (if any)
Required Artifacts
GENPACK_<SHOT_ID>_v###.txt
Must include sections in exact order:
[STYLE]
[SET]
[CHARACTERS]
[ACTION]
[NEGATIVES / NO-DRIFT]
[SETTINGS]
Order must not change.
Process
- Insert STYLE lock verbatim.
- Insert SET lock verbatim.
- Insert relevant CHAR locks verbatim.
- Translate shot blocking into ACTION section.
- Reinforce anchor details (face markers, lighting anchors).
- Add NO-DRIFT constraints explicitly.
- Apply REGEN_RULES adjustments if present.
- Set generation parameters based on tier.
Design Principles
No Silent Additions
Do not add:
- Extra props
- Extra characters
- Unspecified wardrobe changes
- Unstated environmental changes
Anchor Reinforcement
For hero-tier A shots:
- Explicitly restate 2–3 facial markers.
- Reinforce lighting anchors.
- Reinforce set anchors.
Drift Resistance
Always include:
- Prohibited alterations
- Forbidden changes from locks
- Identity anchors
Evaluation Checklist
- All required locks included.
- No details invented.
- No ambiguous phrasing.
- Clear blocking summary.
- Negative constraints explicit.
- Settings match shot plan.
- Resolution tier correct.
- Regen rules applied (if applicable).
Gate Behavior
FAIL if:
- Missing lock reference.
- Ambiguous character description.
- Lighting inconsistent with set-lock.
- Action contradicts world-state.
- Resolution mismatch.
- Forbidden drift not reinforced.
PASS when:
- GenPack reproducible.
- Drift risk minimized.
- No ambiguity.
- Fully aligned with upstream artifacts.
Escalation Policy
Escalate to Vision Tier if:
- Complex spatial choreography.
- Multi-character blocking heavy.
- Visual symbolism dependent on framing.
Escalate to Judgment Tier if:
- Emotional nuance requires interpretation.
- Conflicting visual interpretations exist.
Common Failure Modes
- Forgetting to include style lock.
- Dropping signature facial markers.
- Adding decorative background elements.
- Overwriting lighting rules.
- Action phrased vaguely.
- Ignoring regen-rule updates.
Related Skills
- shot-planner
- regen-analyzer
- qc-grader
- continuity-supervisor
- cost-optimizer
- model-router
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
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.

