Output-Driven Dev
v1.0.0Guides defining success criteria and verification before coding to ensure deliverables are proven complete through measurable, reproducible evidence.
⭐ 0· 101·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (define success criteria and verification) align with the SKILL.md. There are no requested env vars, binaries, or installs that would be unrelated to its stated goal.
Instruction Scope
Runtime instructions are limited to defining outputs, writing verification steps, and documenting evidence. Example verification items mention running commands, opening URLs, and checking files as illustrative verification actions — which are appropriate for a verification template. The SKILL.md does not instruct reading unrelated system files, collecting secrets, or sending data to external endpoints outside normal verification activities.
Install Mechanism
No install spec and no code files — nothing is written to disk or downloaded. This is the lowest-risk model for a skill of this type.
Credentials
The skill declares no environment variables, credentials, or config paths. That is proportionate to an instruction-only checklist that only guides how to define and run verification.
Persistence & Privilege
always is false and the skill is user-invocable with normal autonomous-invocation allowed. That is expected for a helper skill; it does not request permanent presence or modify other skills or system-wide settings.
Assessment
This skill is a benign, instruction-only template to help agents and humans define success criteria and verification steps. It doesn't request credentials or install anything. Practical considerations before installing: (1) verification steps may instruct the agent to run commands, access URLs, or read files — ensure the agent's runtime permissions and network access are appropriately limited so verification actions cannot access sensitive data or exfiltrate information; (2) review any concrete verification commands the agent intends to run before allowing autonomous invocation; (3) if you want to restrict automation, keep the skill user-invocable only or apply agent-level policies that require approval for actions that touch network, filesystem, or external services.Like a lobster shell, security has layers — review code before you run it.
agentsvk97ck7y60jyer3728py2c5xzg583dd21developmentvk97ck7y60jyer3728py2c5xzg583dd21latestvk97ck7y60jyer3728py2c5xzg583dd21planningvk97ck7y60jyer3728py2c5xzg583dd21
License
MIT-0
Free to use, modify, and redistribute. No attribution required.