standards-review SKILL.md skillA
standards-review from pantheon-org/tekhne is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pantheon-org/tekhne/standards-review@git:20260711.6d8d5c4Pins git:20260711.6d8d5c4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pantheon-org/tekhne
- Path
skills/software-engineering/standards-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260711.6d8d5c4, committed Jul 11, 2026
- Size
- 6,934 bytes
- Repository stars
- 10
- License
- MIT
Review a saved standards document via a one-standard-at-a-time interview. Prompts the user for the file path, parses individual standards, then presents each one for evaluation with concrete options (Accept / Revise / Reject / Defer). Produces a summary report at the end.
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
# Standards Review Review a set of project standards through a structured, one-at-a-time interview. Each standard is presented individually with actionable options; the user picks one and moves on. Ends with a confirmed recap and a written report. ## Mindset Every standard should be clear, enforceable, and necessary. If it's not all three, it needs work. The interview is a triage loop — for each standard, present it, get the user's action, and move on. Do not over-analyse a single standard or extend the interview beyond the user's stated scope. ## When to Use - A team has codified standards (in `RULES.md`, `CONTRIBUTING.md`, or similar) and wants to audit them - Onboarding to a new project and reviewing whether existing standards still apply - Before a migration or refactor, checking which standards are still relevant - After a period of drift, to clean up stale or contradictory standards - The user explicitly asks for a "standards review" or to "audit our rules" ## Prerequisites - The standards file must exist at a path the agent can read. - The file must have parseable structure (Markdown headings, numbered lists, or line-separated entries). ## Workflow …
Read the whole file at its exact version.
How to install
mdr add pantheon-org/tekhne/standards-review@sha256:3a850ffb508615fdThe line at the top of this page pins the label git:20260711.6d8d5c4, 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_bumr345gelj43vni)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 11, 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 (6934 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
pantheon-org/tekhne · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bumr345gelj43vni GET https://markdownregistry.com/api/v1/resolve?ref=pantheon-org/tekhne/standards-review GET https://markdownregistry.com/api/v1/blob/3a850ffb508615fdaad0a40b9db5ef485ef700404da0c4bc6c3a2df403049e15
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.