standpoint-review SKILL.md skillA
standpoint-review from chrono-meta/forge-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrono-meta/forge-harness/standpoint-review@v0.1Pins v0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrono-meta/forge-harness
- Path
plugins/fh-commons/skills/standpoint-review/SKILL.md- Versions recorded
- 2
- Latest version
- v0.1, committed Nov 1, 2026
- First version recorded
- Nov 1, 2026
- Size
- 15,789 bytes
- Repository stars
- 31
- License
- MIT
Standpoint review — check a change from the side that RECEIVES it: copy the receiving repo (or a clean install of the package) into an isolated folder, apply the change there, run that repo''s OWN checks, have a reviewer judge the change against that repo''s OWN rules with none of the author''s explanation, then verify every finding against the source before acting on it. Use when asked whether a change breaks, or still works with, another repo, app, harness or package consumer that depends on…
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
# standpoint-review — review a change from the side that receives it **Input**: the change (a diff such as `git diff <base>..HEAD > change.diff`, a dependency bump, or a package build) and the repo or package that receives it. **What it is, in one line**: family diversity (another model reads the diff) raises resolution *within one standpoint*. Standpoint review changes *which ground truth* the change is checked against: the receiving side's own rules, tests and conventions. A defect that only exists relative to the receiver's conventions is invisible from the author's repo however many models read it. **Why this exists (operator decision 2026-11-01)**: in forge-harness (FH) the standpoint axis runs as an engine — a rule (`knowledge/shared/harness-core/field_verdict_crossfamily_gate.md` §7) plus a commit-hook field (`standpoint:`) — for sessions running inside the harness repo. Someone who only installs the plugin gets neither. This skill is the same procedure as a doorway they can call. The rule file stays the canon; read it whenever it is present. This skill does not replace it. …
Read the whole file at its exact version.
How to install
mdr add chrono-meta/forge-harness/standpoint-review@sha256:9ef0a0cb369fe1e4The line at the top of this page pins the label v0.1, 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_dindldkcarw5sdhg)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Nov 1, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1 latest | 2026-11-01 | da2f3f3 | 15,789 B | A | view · diff |
| v0.1 | 2026-11-01 | a06f675 | 14,297 B | A | view |
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 (15789 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
chrono-meta/forge-harness · 31 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dindldkcarw5sdhg GET https://markdownregistry.com/api/v1/resolve?ref=chrono-meta/forge-harness/standpoint-review GET https://markdownregistry.com/api/v1/blob/9ef0a0cb369fe1e411d3ae11d0a1198f7d347d6132a6e90408c05cdbb9d2e4a5
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.