Execute
alirezarezvani/claude-skills
/cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.
Query VelaTerm plan-execute workflows by session: find planner, executor and optional reviewer IDs, tasks, states, rounds, delivery receipts and saved session properties.
MITAuto-check passed
Install Vflow
$ npx skills add vlinx-io/VelaTerm --skill vflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vlinx-io/VelaTerm vflow --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/vlinx-io/VelaTerm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vflow .claude/skills/vflow && 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 "vflow" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vflow into .claude/skills/vflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vflow", 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/vlinx-io/VelaTerm/tree/dev/skills/vflowType 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 vlinx-io/VelaTerm --skill vflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vlinx-io/VelaTerm vflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vflow .agents/skills/vflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vflow" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vflow into .agents/skills/vflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vflow", 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 vlinx-io/VelaTerm --skill vflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vlinx-io/VelaTerm vflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vflow .cursor/skills/vflow && 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 "vflow" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vflow into .cursor/skills/vflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vflow", 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/vlinx-io/VelaTerm.git --path skills/vflow--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 vlinx-io/VelaTerm --skill vflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vlinx-io/VelaTerm vflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vflow .gemini/skills/vflow && 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 "vflow" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vflow into .gemini/skills/vflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vflow", 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 vlinx-io/VelaTerm vflowInstalls 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 vlinx-io/VelaTerm --skill vflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vflow .github/skills/vflow && 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 "vflow" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vflow into .github/skills/vflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vflow", 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 vlinx-io/VelaTerm --skill vflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vlinx-io/VelaTerm vflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vflow .opencode/skills/vflow && 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 "vflow" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vflow into .opencode/skills/vflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vflow", 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
vflow- GitHub stars
- 270
- Token cost
- ~912 tokens
- SKILL.md length
- 426 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Query VelaTerm plan-execute workflows by session: find planner, executor and optional reviewer IDs, tasks, states, rounds, delivery receipts and saved session properties.
- A workflow ID is unknown
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The user asks which execute sessions belong to a plan session
What it does
Vflow is an agent skill from vlinx-io/VelaTerm. Query VelaTerm plan-execute workflows by session: find planner, executor and optional reviewer IDs, tasks, states, rounds, delivery receipts and saved session properties. Use when a workflow ID is unknown or the user asks which execute sessions belong to a plan session. Lookup is read-only; it does not dispatch, message, stop or accept work.
Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: VelaTerm = Codex + iTerm2, The Best ADE for AI Coding. The licence is MIT.
When your agent uses it
- A workflow ID is unknown
- The user asks which execute sessions belong to a plan session
Example prompts
- “/vflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 98b5f2f. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Vflow loads about 912 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 426 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 vlinx-io/VelaTerm at commit 98b5f2f, republished under its MIT licence (© vlinx-io). 426 words, ~912 tokens.
Download SKILL.mdSave it as
.claude/skills/vflow/SKILL.md (or your agent's skills folder).- name
- vflow
- description
- Query VelaTerm plan-execute workflows by session: find planner, executor and optional reviewer IDs, tasks, states, rounds, delivery receipts and saved session properties. Use when a workflow ID is unknown or the user asks which execute sessions belong to a plan session. Lookup is read-only; it does not dispatch, message, stop or accept work.
vflow
Use saved backend associations rather than guessing from session names or reading SQLite directly.
vflow list
vflow list <plan-session>The first form queries the calling session. The second accepts a full session ID, an ID prefix of at least eight characters, an exact name, or a unique name substring. Quote names containing spaces. An ambiguous reference returns candidates; choose an exact ID. Lookup can inspect another session, including an archived session, in the same connected VelaTerm instance.
Read the JSON result:
session,parent,ancestors,children: the resolved session, its parent, ancestor chain and actual direct children, with saved properties and per-session settings.workflows: associated overall workflows, including saved configuration, state, round, latest handoff summary, review configuration/status, planner, executor, optional reviewer, recent delivery receipts, and splittasks.workflows[].tasks: each task's name, prompt, independent workflow ID, state, round, and executor.workflowIdson a session: its direct workflow memberships;parentSessionIdrecords its tree parent.
An empty workflows array does not mean there are no children. Inspect children separately and do not
call every child a workflow executor. An executor may be absent before its first dispatch. Activity and
delivery receipts do not prove task completion; check the saved state and execution evidence.
Session objects include project/group placement, agent and native conversation IDs, engine, directory,
worktree and baseline ref, permissions, collaboration mode, preset, executable, shell, shortcut, mark,
sort order, creation/archive timestamps, collapse/fork state, and saved model/effort, Codex, Claude and
auto-continue settings. launchModelSettings separately reports model/effort explicitly saved in launch
arguments. Null means the value was not saved; do not invent an effective default.
redactedFields identifies masked launch input, environment values and URL credentials/query/fragment.
Environment variable names remain visible. These masked values are not evidence that a setting is empty.
Show full SKILL.md (145 more words)Show less
Workflow members can read a saved complete execution report with vflow read-report <workflow-id> --message-id msg-UUID. This does not dispatch or review work. For tool history, use vrefer <executor-session-id>; summaries can be truncated.
For ordinary session hierarchy or properties without workflow details, use vself [session] --json.
Inside a workflow member session, vflow status <workflow-id> reads that workflow's detailed status.
Unlike list, status requires the caller to be its owner, planner, executor or reviewer. Existing dispatch,
stop, block, accept and finish commands retain their role and round checks. Read-only lookup does not authorize
those actions. For an already authorized planning/execution handoff, read
../vspawn/references/plan-execute.md and follow that protocol.
The commands require a VelaTerm-hosted session and its injected VLX_* environment. If vflow list
reports an unknown action, the running backend predates lookup support; report the version mismatch
instead of treating it as an empty workflow or editing the database.
© vlinx-io, 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/vflow of vlinx-io/VelaTerm.
Open the folder on GitHubat commit 98b5f2f
Compare with similar skills
Vflow 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 |
|---|---|---|---|---|---|---|
| Vflow this skillvlinx-io/VelaTerm | 270 | — | ~912 | Automated safety check: Pass | MIT | |
| Executealirezarezvani/claude-skills | 28k | — | ~831 | Automated safety check: Pass | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Ulw Executecode-yeongyu/oh-my-openagent | 70k | — | ~6.3k | Automated safety check: Pass | Custom licence | |
| Executebrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~370 | Automated safety check: Notes | Custom licence | |
| Safe SQL Executionsupabase/supabase | 111k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Ulw Execute
code-yeongyu/oh-my-openagent
Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents.
Execute
brycewang-stanford/Auto-Empirical-Research-Skills
Executes all registered notebooks, strips noisy cell metadata, and syncs Jupytext pairs.
- Official
Safe SQL Execution
supabase/supabase
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
Execution
alsk1992/CloddsBot
Execute trades on prediction markets with slippage protection and order management
More from vlinx-io/VelaTerm
All 26 skills in this repoAssess Patch Risk
vlinx-io/VelaTerm
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility.
Vspawn
vlinx-io/VelaTerm
Explicitly spawn a standalone child session under the current vlx-term session, passing the task in as its first message (mirrors spawntask).
Deep Security Scan
vlinx-io/VelaTerm
A skill your agent uses when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan.
Define Security Policy
vlinx-io/VelaTerm
Define, review, or update SECURITY.md guidance for a repository or component.
Track Findings
vlinx-io/VelaTerm
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories.
Verify Fix
vlinx-io/VelaTerm
Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability.
Questions about Vflow
What does Vflow do?
Query VelaTerm plan-execute workflows by session: find planner, executor and optional reviewer IDs, tasks, states, rounds, delivery receipts and saved session properties. Vflow is an agent skill from vlinx-io/VelaTerm. Query VelaTerm plan-execute workflows by session: find planner, executor and optional reviewer IDs, tasks, states, rounds, delivery receipts and saved session properties.
When should I use Vflow?
Vflow fits situations like: A workflow ID is unknown; the user asks which execute sessions belong to a plan session.
How do I install Vflow in Claude Code?
Run `npx skills add vlinx-io/VelaTerm --skill vflow -a claude-code`. Or copy the skill folder (skills/vflow in vlinx-io/VelaTerm) into .claude/skills/vflow in your project. Claude Code loads it when a task matches its description.
How do I install Vflow in Codex?
Run `npx skills add vlinx-io/VelaTerm --skill vflow -a codex`. Or copy the skill folder (skills/vflow in vlinx-io/VelaTerm) into .agents/skills/vflow in your project. Codex loads it when a task matches its description.
Can I use Vflow 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 vlinx-io/VelaTerm --skill vflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vflow, .gemini/skills/vflow, .github/skills/vflow and .opencode/skills/vflow in your project.
What does Vflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Vflow is instructions for the agent only.
Does Vflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vflow 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 Vflow use?
Vflow 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 Vflow use?
About 912 tokens (SKILL.md is roughly 3.6k 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 Vflow?
Skills that share tags, products or a category with Vflow: Execute (alirezarezvani/claude-skills, 28k stars), Debugging Executions (n8n-io/n8n, 207k stars), Ulw Execute (code-yeongyu/oh-my-openagent, 70k stars) and Execute (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vflow?
vlinx-io (a GitHub user) maintains it in vlinx-io/VelaTerm, which has 270 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.
Source: vlinx-io/VelaTerm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.