๐Ÿ“‹
AutomationPython

Status

by ffroliva

Status is an Automation skill for Claude Code, published by ffroliva in gflow-cli.

173 stars47 forkson ffroliva/gflow-cliAdded 2026/09/08+24% in starsRepository updated 2026/09/07
agenticai-agentsclaude-codecligenerative-aigoogle-flowimage-to-videoimagenmcpmcp-serverpythontext-to-videoveovideo-generation
Install in seconds
Install Status
Copy Status into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/ffroliva/gflow-cli/tree/develop/skills/status ~/.claude/skills/status

Requires Node.js. Downloads this skill only โ€” not the rest of the repository โ€” into your Claude Code skills folder.

Without Node.js

git clone https://github.com/ffroliva/gflow-cli.git

Clones the whole repository, then copy the skillโ€™s own directory into your skills folder yourself.

In this catalog

Source file
skills/status/SKILL.md in ffroliva/gflow-cli
Installs to
~/.claude/skills/status
Collection
One of 18 skills cataloged from this repository
Category
Automation โ€” 2226 skills

What Status does

Status surfaces the current plan state from gflow-cli, including the active plan, progress, and next task. Use it to resume work, check what comes next, or confirm which plan is active.

Status is cataloged under Automation on DirSkills. Status comes from a repository tagged agentic, ai-agents, claude-code, cli and generative-ai.

Documentation

README

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.py

Return: 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?"

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Status

  • What else does ffroliva publish alongside Status?

    Status is one of 18 skills that DirSkills catalogs from ffroliva/gflow-cli, the repository it ships in. Its siblings there include Changelog, Check and Documentation Review. Each one is a separate skill with its own page in this directory, installs the same way Status does, and is maintained by ffroliva in that same repository. The rest of the collection is listed on the ffroliva/gflow-cli page.

  • How does Status compare to other Automation skills?

    Status ranks #1974 by stars among the 2226 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Status against them. Open each page to compare what they document and how they install.

More from ffroliva/gflow-cli

Status is one of 18 skills cataloged on DirSkills from ffroliva/gflow-cli.

See all 18 skills โ†’
๐Ÿ“
1h ago

Changelog

Changelog shows unreleased changes and the last tagged version for quick comparison. Use it before a release or when you need a short view of queued and shipped work.
Writing
17347
โœ…
1h ago

Check

Check auto-fixes lint and formatting, then runs repo-wide verification for types, tests, doc links, and other quality gates before a commit. Use it when you want the codebase cleaned and checked against CI-style failures.
Quality
17347
๐Ÿ“š
1h ago

Documentation Review

Documentation Review checks release-facing docs for stale references, broken links, missing index entries, and drift between canonical and published pages. Use it before cutting a release or after major documentation changes.
Quality
17347
๐ŸŽฌ
1h ago

GFlow CLI

GFlow CLI automates Google Flow from the terminal or scripts for Veo video and Imagen image generation. It is used for text-to-video, image-to-video, image pipelines, batch runs, and other Flow credit workflows through a headed Chrome session.
Automation
17347
๐Ÿงช
1h ago

Issue Assessment

Issue Assessment reviews a gflow-cli issue against code, tests, and docs to decide whether the claim is confirmed, needs more info, or is already known. It also checks whether the issue can be verified end to end and drafts a reporter-facing reply.
Quality
17347
๐Ÿ› ๏ธ
1h ago

Issue Resolve

Issue Resolve drives an assessed gflow-cli bug to a draft PR in an isolated worktree. It is used for localized, verifiable fixes with test-first changes and browser-free validation, or to note when human e2e verification is still needed.
Automation
17347