audit SKILL.md skillA
audit from harmix/open-stanley is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add harmix/open-stanley/audit@git:20260912.ec207d5Pins git:20260912.ec207d5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- harmix/open-stanley
- Path
open-stanley/skills/audit/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260912.ec207d5, committed Sep 12, 2026
- Size
- 3,386 bytes
- Repository stars
- 5
- License
- MIT
Check a LinkedIn/X post or comment for the things that get it demoted, flagged as AI, or skipped by readers — AI-flagged vocabulary and structures, platform rules (hashtags, links, length, hook), unsupported claims without receipts, and overlap with the user's past posts — using the bundled stanley-audit linter. Use whenever the user asks "does this sound like AI", "check this post", "review before I publish", "why isn't this getting reach", or pastes a draft they wrote elsewhere; the write…
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
# Audit
Run the linter, then read the result like an editor, not a checklist.
```
skills/stanley/scripts/stanley-audit <file-or-`-` for stdin> --platform linkedin|x|comment --vault <vault> [--json]
```
Exit 0 = clean. BLOCK findings are things a 2026 feed or a founder reader would punish; fix them before the human sees the draft. WARN needs a judgment call; INFO is for the human pass. `references/rules.md` explains every rule and the evidence behind it, so you can tell the user *why* rather than "the linter said".
## What the linter cannot catch (do these yourself)
1. **Is the claim actually the person's?** A draft can pass every rule and still assert something they never said ("As CEO, I was tracking commercial commitments" was written by a tool, not the founder, and he cut it). Check the draft's claims against the story file and the user's own words. If a sentence has no source in either, mark it `[unclaimed]` in the handover.
2. **Is it fresh?** For anything presented as news, open the source and check the date against `freshness_days` in `voice.md`. Papers from 2024–25 are not news in 2026.
…Read the whole file at its exact version.
How to install
mdr add harmix/open-stanley/audit@sha256:21649037ce05aab0The line at the top of this page pins the label git:20260912.ec207d5, 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_gf42z44vyhu36o53)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 12, 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 (3386 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
harmix/open-stanley · 5 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gf42z44vyhu36o53 GET https://markdownregistry.com/api/v1/resolve?ref=harmix/open-stanley/audit GET https://markdownregistry.com/api/v1/blob/21649037ce05aab09c6418a339325f5bfce012b77e7f344d58f4f30e3ebf4f90
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.
More from harmix/open-stanley
Every file in harmix/open-stanley