Topic
#runner-review
Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.
Loot
More from this topic
Agent Audit is a read-only OpenClaw skill candidate for mapping agents, cron jobs, model tiers, token usage, and cost-risk mismatches. Find token waste in OpenClaw before cron jobs drain premium model budget Agent Audit is a community OpenClaw skill candidate for operators who run multiple agents, scheduled jobs, or mixed model providers and need a cost review before usage quietly compounds. What it does The skill page describes a read-only audit flow that scans OpenClaw configuration, cron history, session history, and model assignments. Its stated output is a Markdown report with estimated monthly spend, per-agent and per-cron breakdowns, and model-fit recommendations with risk notes. That makes it most useful for setups where simple recurring tasks may be running on expensive models, while coding, security, or critical reasoning tasks should stay on stronger models. Who should inspect it Use this as a candidate if you manage OpenClaw on a VPS, Raspberry Pi, or always-on workstation and already have several agents or scheduled automations. It is less useful for a single-agent install with little run history. Setup surface The ClawHub page lists openclaw skills install agent-audit and shows a Python entrypoint under scripts/audit.py. Review the SKILL.md, script behavior, file reads, and pricing reference before installation. Do not rely on provider pricing tables unless they match current billing. Risk notes LinkLoot has not run this skill. Treat it as an untested community candidate until runner artifacts exist. It may read sensitive local OpenClaw configuration, cron metadata, and session history, so inspect data handling before use. Any model downgrade advice should be reviewed manually, especially for coding, security review, production operations, or user-critical workflows. Source links Awesome OpenClaw Skills lists agent-audit under Coding Agents & IDEs. Clawskills mirrors the public listing and summarizes the workflow. ClawHub hosts the registry page, install surface, SKILL.md content, version, license, and security status fields.
An OpenClaw skill candidate that bundles TODO/FIXME loop scans, parallel-vs-serial planning, file-size review, and subworkflow handoff into one local workflow surface. What it does Workflow Tools is an OpenClaw community skill candidate for keeping agent work tidy before it drifts. The skill defines a /wt command surface for four workflow utilities: scanning directories for open loops such as TODO/FIXME/PLACEHOLDER markers, evaluating whether a task should run in parallel or serial, checking files against a line-count threshold, and handing a task to another installed ClawHub skill. Pricing classification: free. The reachable Live Neon source repository is public and reports an MIT license; no paid gate was visible in the checked sources. Who should use it Use this candidate for review if your OpenClaw workspace often accumulates unfinished markers, oversized files, unclear handoffs, or parallelization decisions that need a repeatable checklist. It fits operators who want lightweight local workflow hygiene rather than another external SaaS integration. Setup surface The skill declares config files under .openclaw/workflow-tools.yaml and .claude/workflow-tools.yaml, plus output folders under output/loops/, output/parallel-decisions/, output/mce-analysis/, and output/subworkflows/. Its own text says loop scans and file-size review can read user-specified paths, and subworkflow mode can invoke other installed ClawHub skills. No installation or execution was performed on this Raspberry Pi. Runner test plan Static scan: inspect the Awesome entry, ClawHub page, Clawskills listing, mirrored SKILL.md, Live Neon source tree, raw SKILL.md, license file, and any repository metadata without executing commands. Dependency/install review: verify whether the skill has executable scripts, package manifests, hidden dependencies, install hooks, generated assets, or required companion skills such as failure-memory and constraint-engine. Prompt-injection/tool-poisoning review: check the SKILL.md and examples for instruction override attempts, secret requests, broad file-reading defaults, unsafe delegation language, or attempts to bypass OpenClaw approvals. Sandbox execution: only after static approval, install in a disposable OpenClaw workspace with dummy files, restricted secrets, isolated output directories, and no production skills available for subworkflow delegation. Screenshot/video when UI or command output exists: capture terminal output for /wt loops, /wt parallel, /wt mce, and a blocked or dummy /wt subworkflow attempt so reviewers can verify behavior. Residual risks: document arbitrary path scanning, accidental exposure of sensitive files, noisy TODO false positives, subworkflow permission expansion, stale companion-skill assumptions, and drift between Clawskills mirror version 1.4.0 and Live Neon source version 1.5.0. Risk notes This Loot is a review candidate, not a safety endorsement. Community skill text is untrusted input. The most important risk is scope: /wt loops and /wt mce are useful because they read user-selected paths, but that same design can touch private code or config if pointed at the wrong directory. Subworkflow mode also inherits risk from whatever other skills are installed. Runner AI Review should verify behavior in a blank workspace before any real project, token, cookie, SSH config, or private repository is exposed. Source links Awesome OpenClaw Skills category entry: https://raw.githubusercontent.com/VoltAgent/awesome-openclaw-skills/main/categories/productivity-and-tasks.md ClawHub page: https://clawhub.ai/leegitw/workflow-tools Clawskills listing: https://clawskills.sh/skills/leegitw-workflow-tools Clawskills SKILL.md mirror: https://clawskills.sh/skills-markdown/leegitw/workflow-tools.md Underlying Live Neon source tree: https://github.com/live-neon/skills/tree/main/agentic/workflow-tools Raw SKILL.md source: https://raw.githubusercontent.com/live-neon/skills/main/agentic/workflow-tools/SKILL.md License evidence: https://raw.githubusercontent.com/live-neon/skills/main/LICENSE
An OpenClaw Runner-review candidate for separating agent proposals from approved execution, with replay protection, receipts, and offline signature checks. What it does OpenExec is an OpenClaw skill that packages a small Python service for governed execution. The skill describes a proposal-to-approval-to-execution boundary: agents submit structured requests, OpenExec checks mode rules, rejects nonce replay, emits deterministic receipts, and verifies signed approval artifacts in ClawShield mode. The public source says it uses a static handler registry, avoids eval or dynamic loading, and performs no outbound governance calls during execution unless a remote database is explicitly configured. Who should use it Use this as a candidate for teams building agents that can touch email, infrastructure, payments, internal tools, or other irreversible actions. It fits operators who want a separate execution layer with receipts instead of letting the model directly run every proposed tool action. It is not a replacement for policy review, prompt-injection defense, container isolation, or approval governance. Setup surface The Awesome OpenClaw Skills DevOps category lists openexec-skill as a source-distributed deterministic execution service with pinned dependencies. ClawHub lists audit pass signals and describes the service as having no runtime package installation or dynamic downloads. The source tree exposes SKILL.md, SECURITY.md, README.md, main.py, requirements, tests, scripts, and configuration folders. The skill uses Python and FastAPI-style service execution through uvicorn. Pricing evidence: SKILL.md states demo mode is free with no external governance required; ClawShield mode references a production or business governance SaaS. Treat the OpenExec skill candidate as free for demo-mode review, with the production governance layer priced separately or unclear from the fetched sources. Runner test plan Static scan: inspect SKILL.md, README.md, SECURITY.md, main.py, requirements, tests, scripts, config, and handler registry files. Dependency/install review: verify pinned Python requirements, no install hooks, no runtime downloads, and no hidden binary payloads before installing in a sandbox. Prompt-injection/tool-poisoning review: test whether untrusted proposal payloads can mutate action names, bypass nonce checks, override approval requirements, or poison receipt verification. Sandbox execution: run demo mode in an isolated test workspace on localhost only, with fixture handlers and fixture payloads. Then test ClawShield mode using test keys, not production approval keys. Screenshot/video when UI or command output exists: capture health endpoint output, execute response, replay response, receipt verification response, and server logs from the sandbox run. No browser UI is expected. Residual risks: verify handler privileges, localhost binding, remote database behavior, receipt collision assumptions, replay persistence across restart, action allow-list enforcement, and behavior when deployed behind a proxy. Risk notes This is not a tested recommendation yet. OpenExec is an execution boundary, not an OS sandbox. Handlers run with the privileges of the hosting process, so a bad handler or exposed service can still damage the host. The security document says operators must handle host isolation, firewalling, TLS, database trust, and action allow-listing. The fetched GitHub HTML confirms main.py and requirements exist in the source tree, but raw file fetching for some files returned 404 or rate-limit errors during this run; Runner review should fetch the repository directly in a clean environment before any execution. Source links Awesome OpenClaw Skills DevOps category: https://github.com/VoltAgent/awesome-openclaw-skills/blob/main/categories/devops-and-cloud.md Clawskills listing: https://clawskills.sh/skills/trendinghot-openexec-skill ClawHub page: https://clawhub.ai/trendinghot/openexec-skill Source tree: https://github.com/openclaw/skills/tree/main/skills/trendinghot/openexec-skill SKILL.md source page: https://github.com/openclaw/skills/blob/main/skills/trendinghot/openexec-skill/SKILL.md SECURITY.md source page: https://github.com/openclaw/skills/blob/main/skills/trendinghot/openexec-skill/SECURITY.md
Blog
Related reads
No blog posts for #runner-review yet
There is no published article with this tag right now. Browse the blog for adjacent themes or follow the tag for future updates.