Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Workflows
v1.0.2Playbook for authoring, running, evaluating, and improving Gina sandbox workflows with safe defaults and repeatable operations.
⭐ 2· 677·4 current·5 all-time
byAsk Gina@askginadotai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (workflow authoring, running, evaluating) match the content: CLI commands, workflow file locations, run artifacts, and evaluation/optimize loop are all directly relevant. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
The SKILL.md and references describe workflow step types that include powerful runtime primitives (exec, fs.promises.*, kv.*, sql, callTool). This is expected for a workflow engine because steps must run shell commands, read/write files, and use KV/SQL. Because the playbook instructs authors/operators to scaffold/open workflows in /workspace/.harness/workflows and to validate/run them, you should review workflow code before executing runs—steps can execute arbitrary host commands and access files.
Install Mechanism
Instruction-only skill with no install spec and no code files to write to disk. Low installation risk.
Credentials
No environment variables, credentials, or config paths are requested. The playbook explicitly advises least-privilege and not including secrets in logs or skill text.
Persistence & Privilege
Skill does not request always:true, does not modify other skills, and is user-invocable only. No long-lived privileges or autonomous persistence are requested.
Assessment
This is a coherent operations playbook for creating and running sandbox workflows. It does describe and rely on workflow step capabilities that can execute shell commands, read and write files, and access KV/SQL; those are normal for a workflow system but mean you should never run unreviewed workflows. Before installing/using: (1) Confirm the 'workflow' CLI/runtime you will call is the expected/trusted tool on your system, (2) review any .ts workflow definitions in /workspace/.harness/workflows for untrusted exec/fs/kv usage, (3) keep secrets out of workflow code and logs, and (4) require explicit permission scopes and least privilege for any steps that perform writes or external actions.Like a lobster shell, security has layers — review code before you run it.
latestvk97bcqx055gt14fhtdt8xhcerh81q847
License
MIT-0
Free to use, modify, and redistribute. No attribution required.