Gstack Orchestrate
PassAudited by VirusTotal on May 7, 2026.
Overview
Type: OpenClaw Skill Name: gstack-orchestrate Version: 1.6.0 The skill implements a complex orchestration workflow that uses the `Agent` tool to run parallel subtasks and performs extensive shell operations via the `Bash` tool. It contains several high-risk patterns, including the use of `eval` on the output of a local binary (`gstack-slug`) and a sophisticated telemetry/logging system that executes external binaries (e.g., `gstack-telemetry-log`, `gstack-timeline-log`) located in `~/.claude/skills/gstack/bin/`. While these capabilities appear aligned with the stated goal of managing a 'gstack' implementation, the combination of broad shell access, environment variable persistence to disk (`env.sh`), and the execution of external binaries creates a significant attack surface without clear evidence of malicious intent.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used, the skill can run parallel coding agents and change the current repository branch.
This shows the skill can delegate code work to subagents and apply their commits to the user's branch. That is powerful but matches the stated orchestration purpose and is described as approval-gated.
Dispatches each task as an `Agent` subagent with `isolation: "worktree"` ... Cherry-picks each successful task's commit onto your working branch in dependency order
Use it only on a clean, non-critical branch; review the task decomposition, generated commits, and test results before allowing review/ship steps to proceed.
Actual behavior also depends on locally installed gstack and superpowers components.
The skill depends on external tools and other skills that are not included in this artifact review. This is disclosed and expected for the workflow, but users should trust those dependencies too.
"requires": { "tools": ["jq", "git"], "siblingSkills": ["gstack/review", "gstack/ship"], "subSkills": ["superpowers:using-git-worktrees", "superpowers:dispatching-parallel-agents"] }Install the related skills and helper tools only from trusted sources, and review them separately if the repository or deployment path is sensitive.
Run history and task outputs may remain on disk after the orchestration finishes.
The skill stores persistent local orchestration state and subagent results, which may include repository names, branch names, task details, and implementation context.
Shared state directory: `~/.gstack/projects/<slug>/orchestrate/<branch-safe>/` holds `TASKS.md`, `env.sh`, `state.jsonl`, `results/<TASK_ID>.json`.
Review or clean ~/.gstack for sensitive projects, and keep telemetry disabled unless you intentionally want usage metrics recorded.