Video Generation
bytedance/deer-flow
Generates short videos from a structured JSON prompt, optionally guided by a reference image used as the first or last frame.
Surfaces the current state of work in gflow-cli. An agent skill from ffroliva/gflow-cli.
Install Status
$ npx skills add ffroliva/gflow-cli --skill status -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ffroliva/gflow-cli status --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ffroliva/gflow-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/status .claude/skills/status && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "status" agent skill from https://github.com/ffroliva/gflow-cli/tree/develop/skills/status into .claude/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ffroliva/gflow-cli/tree/develop/skills/statusType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ffroliva/gflow-cli --skill status -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ffroliva/gflow-cli status --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ffroliva/gflow-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/status .agents/skills/status && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "status" agent skill from https://github.com/ffroliva/gflow-cli/tree/develop/skills/status into .agents/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ffroliva/gflow-cli --skill status -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ffroliva/gflow-cli status --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ffroliva/gflow-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/status .cursor/skills/status && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "status" agent skill from https://github.com/ffroliva/gflow-cli/tree/develop/skills/status into .cursor/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ffroliva/gflow-cli.git --path skills/status--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ffroliva/gflow-cli --skill status -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ffroliva/gflow-cli status --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ffroliva/gflow-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/status .gemini/skills/status && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "status" agent skill from https://github.com/ffroliva/gflow-cli/tree/develop/skills/status into .gemini/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ffroliva/gflow-cli statusInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ffroliva/gflow-cli --skill status -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ffroliva/gflow-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/status .github/skills/status && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "status" agent skill from https://github.com/ffroliva/gflow-cli/tree/develop/skills/status into .github/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ffroliva/gflow-cli --skill status -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ffroliva/gflow-cli status --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ffroliva/gflow-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/status .opencode/skills/status && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "status" agent skill from https://github.com/ffroliva/gflow-cli/tree/develop/skills/status into .opencode/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
status- GitHub stars
- 264
- Token cost
- ~872 tokens
- SKILL.md length
- 404 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Surfaces the current state of work in gflow-cli. An agent skill from ffroliva/gflow-cli.
- Works in 3 steps: If the caller passed a slug (e.g.… → Otherwise check conversation context for… → If neither, run the script without…
- Tasks that involve AI video generation
- SKILL.md covers Variants, What the script returns…, Feature slug resolution and Integration
- Calls uv
What it does
Status is an agent skill from ffroliva/gflow-cli. Surfaces the current state of work in gflow-cli. Three variants at different levels of detail: full state (status), next task only (next), active plan identity (active). All variants run scripts/dev/activeplan.py and filter its output to the requested detail level.
Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Media & Creative, covering AI video generation. The repository describes itself as: Drive Google Flow from the command line: Veo video and Imagen images, scripted, batched and pipeline-ready. Ships an MCP server so coding agents can drive it too, giving you and… The licence is MIT.
When your agent uses it
- Tasks that involve AI video generation
Example prompts
- “Use the status skill to surface the current state of work in gflow-cli. An agent skill from ffroliva/gflow-cli”
- “/status”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- If the caller passed a slug (e.g. shell-multi-prompt), pass it as --feature .
- Otherwise check conversation context for a feature name mentioned this session.
- If neither, run the script without --feature (falls back to root PLAN.md).
What it can do on your machine
Read from SKILL.md and the folder at commit cb6d501. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Status loads about 872 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 404 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ffroliva/gflow-cli at commit cb6d501, republished under its MIT licence (© ffroliva). 404 words, ~872 tokens.
Download SKILL.mdSave it as
.claude/skills/status/SKILL.md (or your agent's skills folder).- name
- status
- description
- Surfaces the current state of work in gflow-cli. Three variants at different levels of detail: full state (status), next task only (next), active plan identity (active). All variants run scripts/dev/active_plan.py and filter its output to the requested detail level.
- version
- 1.0
status — Plan State Reader
Three variants for different contexts. All backed by scripts/dev/active_plan.py.
Variants
status [feature] — Full state
The full picture: which plan file is active, its goal, progress (X/N tasks complete), and the next unchecked task block.
Script invocation:
# With a feature name (from $ARGUMENTS or conversation context):
uv run python scripts/dev/active_plan.py --feature <slug>
# Without a feature name (uses root PLAN.md):
uv run python scripts/dev/active_plan.pyReturn: the complete script output verbatim.
When to call:
- Starting a session: "where did we leave off?"
- After completing a task: "what comes next?"
- Before adding scope: "does this belong to the current plan?"
next [feature] — Next task only
The single next unchecked task block. No header noise.
Script invocation: same as status.
Return: only the content from --- Next task --- onward. Drop the Plan / Title /
Goal / Progress header lines entirely.
If no --- Next task --- separator is present (root PLAN.md mode), return the full
script output — the phase block is already task-level content.
If the script output contains "All steps complete", say so and suggest:
/gflow:changelogto review unreleased changes/gflow:releaseif the phase is fully done
When to call:
- "What do I do right now?" — between tasks, no orientation needed
- Resuming mid-session after a context switch
active — Plan identity only
Just which plan is active and its goal. No task detail.
Script invocation: same as status.
Return: only the header lines — Plan path, Title, Goal, Progress count.
- If the output contains
--- Next task ---, stop before that separator. - If no separator is present (root PLAN.md mode —
_summarise_root_plan()output), return the full output; it contains only orientation-level content with no task block.
When to call:
- Before
/gflow:predictor/gflow:scenario: confirm the proposal fits the active scope - Quick check: "are we in a superpowers plan or the root PLAN.md?"
- When context is long and you need a one-line anchor without task block noise
Show full SKILL.md (124 more words)Show less
What the script returns (reference)
- Superpowers plan active: file path · title · goal · progress (X/N steps complete) · next unchecked task block
- No superpowers plan: the first incomplete phase from
PLAN.md(scope, sequence, definition of done) - All complete: "All steps complete." — prompt user toward
/gflow:changelog+/gflow:release
Feature slug resolution
- If the caller passed a slug (e.g.
shell-multi-prompt), pass it as--feature <slug>. - Otherwise check conversation context for a feature name mentioned this session.
- If neither, run the script without
--feature(falls back to rootPLAN.md).
Integration
- Claude Code: invoke via
/gflow:status,/gflow:next, or/gflow:active(thin wrappers around this skill). - Cursor / Aider / Codex: include this file in context; call the variant by name.
- Antigravity (
agy): read this file before asking "what's the next task?".
© ffroliva, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/status of ffroliva/gflow-cli.
Open the folder on GitHubat commit cb6d501
Compare with similar skills
Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Status this skillffroliva/gflow-cli | 264 | — | ~872 | Automated safety check: Pass | MIT | |
| Video Generationbytedance/deer-flow | 83k | 4 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Video Shotseternityspring/reelbench-skills | 868 | 2 repos | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Video Cover Imageitwanger/toBeBetterJavaer | 18k | — | ~3.3k | Automated safety check: Pass | None | |
| Seedancesongguoxs/seedance-prompt-skill | 2.9k | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| HyperFrames Video Entry Pointheygen-com/hyperframes | 59k | 3 repos | ~5.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Video Shots
eternityspring/reelbench-skills
拉片：把一条成片拆成逐镜头的分析表——每个镜头的时长、景别、类别、运镜、画面. An agent skill from eternityspring/reelbench-skills.
Video Cover Image
itwanger/toBeBetterJavaer
Generate matched 3:4, 16:9, and 4:3 short-video cover images from toBeBetterJavaer video scripts or AI/Java technical topics.
Seedance
songguoxs/seedance-prompt-skill
This skill should be used when the user asks to "generate video prompts", "create Seedance prompts", "write video descriptions", mentions "Seedance", "seedance", "即梦", "即梦平台", "视频提示词", "视频生成"…
HyperFrames Video Entry Point
heygen-com/hyperframes
Entry point for making, editing and rendering videos from HTML compositions with HyperFrames, routing each request to the right workflow.
Lanshu Create AI Presenter Video
cclank/lanshu-create-ai-presenter-video
Turn a topic or finished script into a complete, publish-ready explainer video — led by an AI presenter from an authorized adult presenter image, or performed in one of nine visual explainer styles…
More from ffroliva/gflow-cli
All 17 skills in this repoGflow CLI
ffroliva/gflow-cli
A skill your agent uses when the user wants to drive Google Flow (Veo image-to-video, Veo text-to-video, Imagen / Nano Banana image generation) from the terminal or a script — including…
Issue Assessment
ffroliva/gflow-cli
A skill your agent uses when triaging a GitHub issue for gflow-cli — a reporter's bug claim, a freshly-filed issue, or deciding whether and how to act on one.
Issue Resolve
ffroliva/gflow-cli
A skill your agent uses when an assessed gflow-cli issue (verdict CONFIRMED-BUG or LIKELY-BUG) has localized, verifiable scope and should be driven to a fix.
Live Verify
ffroliva/gflow-cli
Two-part gate for gflow-cli feature/fix work. An agent skill from ffroliva/gflow-cli.
Video Production
ffroliva/gflow-cli
A skill your agent uses when the user wants a finished video out of gflow rather than a single clip — a scripted scene, a talking-head or dialogue piece, an explainer, a product montage, a story…
Check
ffroliva/gflow-cli
Auto-fix lint and formatting, then report types and tests. An agent skill from ffroliva/gflow-cli.
Related
Categories
Questions about Status
What does Status do?
Surfaces the current state of work in gflow-cli. An agent skill from ffroliva/gflow-cli. Status is an agent skill from ffroliva/gflow-cli. Surfaces the current state of work in gflow-cli.
When should I use Status?
Status fits situations like: tasks that involve AI video generation.
How do I install Status in Claude Code?
Run `npx skills add ffroliva/gflow-cli --skill status -a claude-code`. Or copy the skill folder (skills/status in ffroliva/gflow-cli) into .claude/skills/status in your project. Claude Code loads it when a task matches its description.
How do I install Status in Codex?
Run `npx skills add ffroliva/gflow-cli --skill status -a codex`. Or copy the skill folder (skills/status in ffroliva/gflow-cli) into .agents/skills/status in your project. Codex loads it when a task matches its description.
Can I use Status in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ffroliva/gflow-cli --skill status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/status, .gemini/skills/status, .github/skills/status and .opencode/skills/status in your project.
What does Status need to run?
Going by SKILL.md and its folder, Status needs the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Status access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Status safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Status use?
Status is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Status use?
About 872 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Status?
Skills that share tags, products or a category with Status: Video Generation (bytedance/deer-flow, 83k stars), Video Shots (eternityspring/reelbench-skills, 868 stars), Video Cover Image (itwanger/toBeBetterJavaer, 18k stars) and Seedance (songguoxs/seedance-prompt-skill, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Status?
ffroliva (a GitHub user) maintains it in ffroliva/gflow-cli, which has 264 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.
Source: ffroliva/gflow-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.