principle-prove-it-works
GitHub任务完成后，通过直接检查真实产物（如运行代码、读取实际值）来验证结果，拒绝依赖代理指标或自我报告。建议编写确定性脚本以确保可重复验证，并将关键证据保留供审查。
Trigger Scenarios
Install
npx skills add sediman-agent/OpenSkynet --skill principle-prove-it-works -g -y
SKILL.md
Frontmatter
{
"name": "principle-prove-it-works",
"description": "Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'",
"disable-model-invocation": true
}
Prove It Works
Verify every task output by checking the real thing directly. Do not infer from proxies, self-reports, or "it compiles."
Why: Unverified work has unknown correctness. Indirect verification (file mtimes, output freshness, agent self-reports, cached screenshots) feels cheaper than direct observation. Acting on a wrong inference costs far more than checking the source.
Pattern: After completing any task, ask: "how do I prove this actually works?"
Check the real thing, not a proxy:
- Check process liveness directly, not indirectly through derived state
- Read the actual value, not a cached or derived representation
- When verification fails, suspect the observation method before suspecting the system
Code and features:
- Build it (necessary but not sufficient)
- Run it and exercise the actual feature path
- Check the full chain: does data flow from input to output?
- For integrations, test the full communication path end-to-end
Delegation: trust artifacts, not self-reports. When verifying delegated work, inspect the actual output artifact (git diff, file contents, runtime behavior), not the delegate's summary. Agents report what they intended, not always what happened.
Script the check when you can
The strongest proof is a deterministic script that re-runs the same comparison, not a one-time eyeball. Write the script, run it, and keep its output as an artifact a reviewer can re-run instead of trusting your word. A script comparing the old and new compiled output catches what a glance misses.
Keep the artifact visible for the human. Commit it only for large or complex work where the trail has to be auditable later, like a big port or migration (the show-me-your-work skill). Most work just needs it visible, not committed.
Version History
- c9d8953 Current 2026-07-05 19:53
