Bytesagain Workflow Builder

Create and run multi-step shell workflows with status tracking. Use when automating deployment sequences, chaining build steps, running CI pipelines locally,...

Security Scan

The skill's code and instructions match its stated purpose (building and running local shell-based workflows); it stores workflow JSON under the user's home directory and executes only the shell commands the user adds — no unexpected external credentials, network endpoints, or installers were found.

Purpose & Capability

Name/description (multi-step shell workflows) aligns with the included script: it creates, stores, lists, runs, and exports workflows saved under $HOME/.bytesagain-workflows. Declared requirements (bash, python3) are consistent with the implementation.

Instruction Scope

SKILL.md documents a CLI (bytesagain-workflow-builder) and usage that matches script behavior. However, there is no install spec that places the script on PATH — the repo includes scripts/script.sh which implements the CLI, but the SKILL instructs use of a command name without describing installation. The runtime instructions and the script do not access unrelated files, credentials, or external endpoints.

Install Mechanism

No install spec (instruction-only) — lowest-risk model. The repository includes a script file but there is no download-from-URL or package install step. No archives or external installers were used.

Credentials

The skill requests no environment variables or credentials. The script writes to a per-user directory ($HOME/.bytesagain-workflows) which is proportionate to its function. There are no unexpected credential names or config paths requested.

Persistence & Privilege

always:false and no special privileges requested. The skill persists only per-user workflow JSON under $HOME and does not modify other skills or system-wide configuration.

Assessment

This skill appears coherent and implements a local workflow runner that executes whatever shell commands you add. Important things to consider before installing/using: (1) The included script stores workflow JSON in $HOME/.bytesagain-workflows and logs up to ~200 characters of each step's stdout/stderr — don't add commands that print secrets you don't want persisted. (2) Steps are executed via the shell (subprocess.run with shell=True) so only add trusted commands; malicious or poorly written commands can modify your system or exfiltrate data. (3) There is no install spec to put a 'bytesagain-workflow-builder' binary on your PATH — you may need to inspect scripts/script.sh and decide how to install or invoke it safely (e.g., review the script, place it in a controlled path, or run it explicitly). (4) Sample templates include actions like rsync, docker push, and kubectl which can interact with remote systems — review credentials/targets before running. If you want higher assurance, review the script source locally, run commands in a sandbox/container, or add stricter output handling and step timeouts.

Build, run, and track multi-step workflows from the terminal. Define pipeline steps with shell commands, execute them in sequence, and monitor status with detailed progress tracking.

Usage

bytesagain-workflow-builder create "<name>"
bytesagain-workflow-builder add-step <id> "<step_name>" "<command>"
bytesagain-workflow-builder run <id>
bytesagain-workflow-builder status <id>
bytesagain-workflow-builder list
bytesagain-workflow-builder export <id>
bytesagain-workflow-builder template <type>

Commands

• create — Create a new named workflow and get its ID
• add-step — Add a shell command step to a workflow
• run — Execute all steps in sequence, stopping on failure
• status — Show per-step execution status and output
• list — List all workflows with step counts and last run time
• export — Export workflow definition as JSON
• template — Show starter templates (ci, deploy)

Examples

bytesagain-workflow-builder create "Release Pipeline"
bytesagain-workflow-builder add-step wf001 "Run Tests" "npm test"
bytesagain-workflow-builder add-step wf001 "Build" "npm run build"
bytesagain-workflow-builder add-step wf001 "Deploy" "rsync -av dist/ server:/var/www/"
bytesagain-workflow-builder run wf001
bytesagain-workflow-builder status wf001

Requirements

• bash
• python3

When to Use

Use when automating multi-step processes, building CI-like pipelines locally, tracking deployment steps, or managing repeatable task sequences with clear pass/fail status.