Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Playbook for authoring, running, evaluating, and improving Gina sandbox workflows with safe defaults and repeatable operations.
Playbook for authoring, running, evaluating, and improving Gina sandbox workflows with safe defaults and repeatable operations.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Provides a practical workflow-authoring and operations standard for Gina sandbox automation. Creates and validates workflow definitions. Runs workflows and inspects artifacts/logs. Applies a repeatable eval -> optimize -> compare loop. Uses safe TypeScript/SQL/KV patterns for step logic.
You are creating or maintaining multi-step workflow orchestration. You need reproducible debugging from run artifacts. You want measurable improvements using baseline comparisons.
The task is a single action with no orchestration requirement. You only need high-level strategy language without runnable steps. You cannot provide explicit permissions or side effects.
Workflow intent and success criteria. Trigger definition and input schema. Required tools/data sources and permission scope. Optional baseline run ID for optimization.
Validated workflow definition (.ts). Runnable execution with traceable artifacts. Evaluation record with baseline comparison. Clear rollback path for regressions.
workflow create <id> workflow validate <id> workflow run <id> [--input JSON] workflow status <run-id> workflow logs <run-id> [--step <step-id>] workflow eval <run-id> workflow optimize <id> --baseline <run-id> workflow rollback <id> <opt-run-id>
Confirm workflow tooling is available (workflow list should succeed). Scaffold or open the target workflow in /workspace/.harness/workflows/. Keep active versions on @latest.ts naming when versioned variants exist. Validate before every run: workflow validate <id>. For risky changes, capture a baseline run and eval before editing.
For each workflow entry, explicitly define: Trigger. Inputs. Outputs. Side effects. Failure modes. Permission scope.
Validation failure from malformed step definitions. Runtime errors in TS/SQL/Bash steps. Missing tool permissions or tool availability. Data shape changes causing parse/cast failures. Timeout/retry exhaustion in external calls.
Use least privilege by step using allow and block. Declare permissions in the submission contract (no wildcard permissions). Never include raw secrets in skill text, logs, or examples. Treat writes (files, KV, external posts, trading actions) as explicit side effects.
Setup path that a reviewer can execute in under 10 minutes. One reproducible run artifact or run log example. Clear statement of expected outputs and acceptable failure behavior.
workflows/ SKILL.md references/ # implementation and API details scripts/ # optional helpers for repeatable checks assets/ # optional diagrams/screenshots
Deep technical references are intentionally split out: references/cli-and-definition.md references/eval-optimize-and-artifacts.md references/polymarket-patterns.md Use these as appendices while keeping this file focused on operational usage.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.