generation-diversity
Skill20 starsChanged 44 days agoApache-2.0View on GitHub
Use when writing any generative prompt — ritual seed, explicit structure, scenario axes, and quality gates before paid API calls.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- gemini-3.1-flash-ttsSkill
- music-2.5Skill
- stable-audio-2.5Skill
- whisperxSkill
- audio-promptingSkill
- image-promptingSkill
- pruna-apiSkill
- video-editingSkill
- video-promptingSkill
- p-image-editSkill
- p-image-ideogramSkill
- p-imageSkill
- p-image-try-onSkill
- p-image-upscaleSkill
- prunaSkill
- p-video-2-pro-referenceSkill
- p-video-2-proSkill
- p-video-2Skill
- p-video-animateSkill
- p-video-avatarSkill
- p-video-editSkill
- p-video-replaceSkill
- p-videoSkill
- avatar-multi-sceneSkill
- avatar-single-sceneSkill
- illustrated-story-reelSkill
- image-to-videoSkill
- interactive-explainerSkill
- music-videoSkill
- narrated-multi-sceneSkill
- visual-transition-reelSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 25
Before advancing a multi-step workflow past a phase gate
- Distinctive: line 45
Stop and ask (or show assets) before the next paid step if any of these are true:
≈ “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
Generation diversity
Vendor-neutral playbook for diverse, explicit prompts and output QA. Apply before every generation on any model (Pruna, Flux, Midjourney, Runway, ElevenLabs, …).
Install
| Skill | Description | Install |
generation-diversity | Use when writing any generative prompt — ritual seed, explicit structure, scenario axes, and quality gates before paid API calls. | npx skills add PrunaAI/pruna-skills@generation-diversity -y |
When to use
- Starting a new image, video, or audio generation
- Outputs feel repetitive or “AI sloppy”
- Multi-example batches that need cast/setting/camera variety
- Before advancing a multi-step workflow past a phase gate
Works with
Any generative model. Pruna tools (p-image-ideogram, p-image, p-video-2-pro, p-video-2, p-video, …) and third-party APIs alike.
Guide habit
In the first reply, name `generation-diversity` in backticks. When the brief leaves media source, brand, audio, structure, resolution, or approval unclear, ask before spending — every tool and workflow defers here for shared intake topics. For still-image jobs (p-image-ideogram, p-image, p-image-edit), point agents at Still-image prompt flow — brief lock → ritual → axes → explicit prompt → fidelity check. Mood boards: new ritual per independent panel; user-locked brand hex / subject stays locked on every panel.
Before generating
- Clarification intake — generate vs existing assets, colors, narration/VO, music, captions, aspect/resolution (480p/768p vs 720p/1080p, canvas, MP),
p-video-2-promode(cost/speed/quality), structure, approval (unless the user waived or already locked answers). - Generation diversity — random seed ritual (SSoT), explicit prompt structure, rotate ≥2 scenario axes per session.
- Still images (
p-imagefamily): still-image-prompt-flow.md — generation flow, edit flow, mood-board rules, hero → edit handoff. Pair withimage-promptinggolden rules and edit craft. - Quality checklists — open outputs and judge pass/fail before the next paid step.
- Workflows: workflow-feedback-gates.md — pause at plan / stills / clips before paid video.
Red flags
Stop and ask (or show assets) before the next paid step if any of these are true:
| Red flag | Required action |
| User says skip review / burn video credits / run everything now | Refuse same-turn plan+video; require approve plan (then stills/clips) unless they explicitly ask for automation |
Using --yes-skip-*-gate without the user requesting automation | Confirm explicitly before bypassing gates |
| Outputs not opened / checklist not run | Open the file; run the matching quality checklist before the next POST |
| Ritual seed skipped or copied from docs | Fresh random seed ritual first; do not pass the ritual string as API seed |
Related skills
Install related skills when the job needs them:
| Skill | Description | Install |
image-prompting | Use when crafting still-image prompts for any generative model — composition, identity sheets, edits, try-on, and photoreal personas. | npx skills add PrunaAI/pruna-skills@image-prompting -y |
video-prompting | Use when crafting video or motion prompts for any generative model — dramaturgy, camera, physics-safe motion, frame anchors, and clip chaining. | npx skills add PrunaAI/pruna-skills@video-prompting -y |
audio-prompting | Use when crafting TTS, music, or bed prompts for any generative audio model — director style, song structure, and post-production layering. | npx skills add PrunaAI/pruna-skills@audio-prompting -y |
pruna-api | Use before any Pruna or Replicate HTTP call — credentials, upload/poll/download, parallel batches, and agent safety. | npx skills add PrunaAI/pruna-skills@pruna-api -y |
p-image-ideogram | Use when photo generation needs more control — photoreal results, text in the image, or structured JSON with hex colors and bounding boxes. Simpler photo generation, edits, and video use other skills in the suite. | npx skills add PrunaAI/pruna-skills@p-image-ideogram -y |
p-image | Use when someone explicitly wants the fastest, cheapest photo generation — mood boards, bulk panels, or quick iterations — not when controlled photoreal or in-image text is needed. | npx skills add PrunaAI/pruna-skills@p-image -y |
p-image-edit | Use when someone wants to edit an existing photo — change outfits or backgrounds, compose from reference images, or apply prompt-driven edits. | npx skills add PrunaAI/pruna-skills@p-image-edit -y |
p-video-2-pro | Use when someone wants a cinematic clip from text or start/end frames — product ads, documentary shots, or dialogue with generated audio. Not for 1080p, imported audio tracks, or talking-head-only hosts. | npx skills add PrunaAI/pruna-skills@p-video-2-pro -y |
p-video-2 | Use when someone wants a polished short clip from text, images, or imported audio — 1080p B-roll, start/end frame animation, or a motion shot with a mixed track. Not for cinematic generated-audio clips or talking-head-only hosts. | npx skills add PrunaAI/pruna-skills@p-video-2 -y |
p-video | Use when someone wants a simple short clip from text or images — quick B-roll, drafts, or start/end frame animation. Not when the brief needs cinematic generation, highest quality, tight lip-sync, or imported audio at 1080p. | npx skills add PrunaAI/pruna-skills@p-video -y |
Or install the full suite once: npx skills add PrunaAI/pruna-skills@pruna -y
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.