hoo-verify-outcome SKILL.md skillA
hoo-verify-outcome from shalintripathi/organic-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shalintripathi/organic-os/hoo-verify-outcome@git:20260722.8498df5Pins git:20260722.8498df5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shalintripathi/organic-os
- Path
plugin/skills/hoo-verify-outcome/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260722.8498df5, committed Jul 22, 2026
- Size
- 5,083 bytes
- Repository stars
- 7
- License
- MIT
Use to re-check a recorded outcome against raw data - "verify that outcome", "did that change really do that", /organic-os:verify-outcome. Recomputes the delta from the connectors before reading what was claimed.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Verify an outcome (recompute first, read the claim second) Takes an item slug or a path to a record in `outcomes/`. The job is to recompute the number from raw data and only then look at what the record claimed, so the recomputation cannot be steered by the answer. Read-only over the brain except for the run report and the one signal in step 5. Nothing here changes an item's status, edits an outcome record, or touches the claimed numbers. ## 1. Identity, URL, windows - and nothing else `PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -c` into `core.outcomes.parse_outcome(<path>)`, and use ONLY these three from what comes back: - `item` - which item this is - `url` - the page to pull - `windows` - the before and after date ranges the claim was measured over **Do not read `claimed_before`, `claimed_after`, or `claimed_delta` yet, and do not print them.** This is the whole exercise. A number you have already seen is a number you will unconsciously reproduce: the pull gets framed around it, a mismatch gets re-run "to check", and the verification becomes a confirmation. Steps 2 and 3 happen with the claim unread. …
Read the whole file at its exact version.
How to install
mdr add shalintripathi/organic-os/hoo-verify-outcome@sha256:0058a29f7891f823The line at the top of this page pins the label git:20260722.8498df5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_gursjuao2jsv66m7)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 22, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5083 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
shalintripathi/organic-os · 7 stars · license MIT · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gursjuao2jsv66m7 GET https://markdownregistry.com/api/v1/resolve?ref=shalintripathi/organic-os/hoo-verify-outcome GET https://markdownregistry.com/api/v1/blob/0058a29f7891f82385de8e853ffcd113f31867a9c5409273ade0290ef4b62a6b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.