Menu

Individual skill

principle-prove-it-works

Use at the end of every task, before you say it succeeded. Check the actual output yourself, for example by exercising the feature, reading back what got stored, or opening the diff. A proxy signal, a subagent's self-report, or a successful compile does not count.

plugins/requie/endostack/skills/principle-prove-it-works/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Prove it works

Look at the real artifact before calling a task finished: exercise the feature, read the value that was stored, examine the diff. Proxies, self-reports, and a successful compile do not count as evidence.

## When it applies

The end of every task, before you report success.

## What to do

1. Expect indirect checks to tempt you. File timestamps, a subagent's summary, and a cached screenshot feel cheaper than looking, but acting on a wrong inference costs more.
2. Check whether a process is alive by querying the process, not by reading a status file it last wrote.
3. Read the value at its source rather than a cached copy or something computed from it. After changing a firewall rule, send a request that should be blocked and confirm it is blocked. Do not stop at "the config file contains the rule."
4. When a verification fails, suspect the observation method first.