Agent skill · Documentation

vibe-creating-prompt

Judges whether a user's input suits the Vibe Creating style of video-prompt writing, and when it does, distills single-scene prompts, multi-shot descriptions, emotional imagery, or mixed input into prompts that are easier for a video model to generate from — while preserving any user-specified dialogue, voiceover, music, sound effects, and other hard constraints. Use when a user wants to turn an idea, story, feeling, or rough/over-specified prompt into a strong text-to-video prompt (Seedance, Sora, Kling, Veo, Runway, etc.), or asks to "rewrite", "improve", "clean up", or "vibe-ify" a video pr

Alisa0808github.com/Alisa0808GitHub ↗
claude-codecodexNOASSERTION
Install
npx skills add Alisa0808/vibe-creating-skill --skill vibe-creating-prompt --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 16 KB
Bundled scripts: none
Path: skills/vibe-creating-prompt/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 119
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Vibe Creating Prompt Skill ## Overview Vibe Creating distills what the user *actually wants to express* so the model can lock onto the visual center, the emotional direction, and the continuity of the experience. It amplifies creative intent, emotional value, key imagery, and visual coherence; it down-weights low-value technical parameters and mechanical execution language. This skill is a *judgment-first* rewriter. It does not blindly shorten or "vibe-ify" everything. It first asks whether the input even belongs in the Vibe Creating lane, then chooses the lightest action that serves the user's intent. ## Quick Start When you receive an input, run three steps: 1. **Judge whether it suits Vibe Creating (VC).** Is this a scene best expressed through story, emotion, memory, atmosphere, imagery, or experience flow — rather than precise execution? 2. **Decide the most appropriate handling right now.** Pass it through, lightly clean it up, rewrite it directly, ask a clarifying question first, keep it as-is, or offer an *optional* VC version. 3. **Only ask for what's missing.** Request the minimum information needed to complete the chosen action. Never interrogate the user just to satis

What's inside
Steps it walks through
  1. Overview
  2. Quick Start
  3. Decision Framework — Scenario × Expression × Information
  4. Scenario fit (S)
  5. Expression form (E)
  6. Routing matrix (default action per cell)
  7. Four hard routing rules
  8. Information-density check (I)
  9. Interaction Policy
  10. Camera Language Policy
  11. Sound & Constraint Priority
  12. Rewrite Modes
  13. Output Rules
  14. Length & form
Ships with 1 file
  • SKILL.zh.md
About this skill
What does the vibe-creating-prompt skill do?

Judges whether a user's input suits the Vibe Creating style of video-prompt writing, and when it does, distills single-scene prompts, multi-shot descriptions, emotional imagery, or mixed input into prompts that are easier for a video model to generate from — while preserving any user-specified dialogue, voiceover, music, sound effects, and other hard constraints. Use when a user wants to turn an idea, story, feeling, or rough/over-specified prompt into a strong text-to-video prompt (Seedance, Sora, Kling, Veo, Runway, etc.), or asks to "rewrite", "improve", "clean up", or "vibe-ify" a video pr

How do I install it?

Run `npx skills add Alisa0808/vibe-creating-skill --skill vibe-creating-prompt --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Alisa0808/vibe-creating-skill, a repository with 119 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going