check-alignment SKILL.md skillA
check-alignment from mangrovetechnologies/mangrove-agent is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mangrovetechnologies/mangrove-agent/check-alignment@git:20261021.b5b288ePins git:20261021.b5b288e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mangrovetechnologies/mangrove-agent
- Path
.claude/skills/check-alignment/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261021.b5b288e, committed Oct 21, 2026
- First version recorded
- May 9, 2026
- Size
- 3,836 bytes
- Repository stars
- 5
- License
- MIT
Check if a proposed change aligns with mangrove-agent's stated principles, architecture, and trading-bot safety invariants. Use when the user describes a change and asks "does this fit", "check alignment", "review this approach", or "/check-alignment <description>". Read-only analysis — does NOT modify anything. Adapted from the Mangrove workspace `check-alignment` skill with trading-bot-specific documents.
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
# Check Alignment Parse `$ARGUMENTS` as a natural-language description of a proposed change — could be a new feature, a refactor, a dependency change, a workflow tweak. Review the proposal against each of these documents. For every one that exists, state whether the proposal **aligns** or **conflicts**. If it conflicts, cite the specific principle or decision it violates and suggest a concrete adjustment. ## Documents to check ### 1. `SAGE.md` — project identity + persona - "What This Is" section: does the proposal still describe a local trading bot? Any scope drift toward cloud / hosted / multi-tenant breaks the v1 framing. - "Architecture" section: dual-protocol (REST + MCP), three-tier access (free / auth / x402), service-layer pattern. Does the proposal respect these layers, or does it duplicate logic? - "Project Context" + "Agent Identity": does the proposal change the user's project context or agent persona? Flag if yes — shared persona rules live in `SAGE.md`; the user chooses the agent's name, saved locally through `set_agent_name`. Identity changes are explicit, deliberate edits, not side effects of feature work. …
Read the whole file at its exact version.
How to install
mdr add mangrovetechnologies/mangrove-agent/check-alignment@sha256:825f052dad4a6d1bThe line at the top of this page pins the label git:20261021.b5b288e, 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_cnarjm2xajimnaz4)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 9, 2026 and Oct 21, 2026, about one every 41 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.b5b288e latest | 2026-10-21 | b5b288e | 3,836 B | A | view · diff |
| git:20261021.178b108 | 2026-10-21 | 178b108 | 3,738 B | A | view · diff |
| git:20260712.9f3adff | 2026-07-12 | 9f3adff | 3,742 B | A | view · diff |
| git:20260510.9f5009e | 2026-05-10 | 9f5009e | 3,753 B | A | view · diff |
| git:20260509.d34211f | 2026-05-09 | d34211f | 3,751 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 (3836 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
mangrovetechnologies/mangrove-agent · 5 stars · license MIT · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cnarjm2xajimnaz4 GET https://markdownregistry.com/api/v1/resolve?ref=mangrovetechnologies/mangrove-agent/check-alignment GET https://markdownregistry.com/api/v1/blob/825f052dad4a6d1be3fc30831e5b6e74464003be1d29d740c2cad9be90007487
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.