scoring-checks SKILL.md skillA
scoring-checks from caliber-ai-org/ai-setup is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add caliber-ai-org/ai-setup/scoring-checks@git:20260428.99f2785Pins git:20260428.99f2785 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- caliber-ai-org/ai-setup
- Path
.agents/skills/scoring-checks/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260428.99f2785, committed Apr 28, 2026
- First version recorded
- Mar 29, 2026
- Size
- 12,017 bytes
- Repository stars
- 1,316
- License
- MIT
Add a new deterministic scoring check in src/scoring/checks/ that evaluates config quality. Follows the Check[] return pattern, uses point constants from src/scoring/constants.ts, and integrates via filterChecksForTarget() in src/scoring/index.ts. Use when user says 'add scoring check', 'new check', 'modify scoring criteria', or works in src/scoring/checks/. Do NOT use for display changes or refactoring scoring logic.
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
# Adding a Scoring Check Add a new deterministic check that evaluates a single aspect of AI agent config quality. All checks must be filesystem-based with no network calls or LLM inference. ## Critical - **Check must be deterministic**: Same filesystem state → same result every time. No randomness, no external APIs. - **Point values come from constants.ts**: Every `earnedPoints` and `maxPoints` must reference `POINTS_*` from `src/scoring/constants.ts`. Do NOT hardcode numbers. - **Always return `Check[]` array**: Export a function `check<Category>(dir: string): Check[]` where category is one of: `existence`, `quality`, `grounding`, `accuracy`, `freshness`, `bonus`. - **Every check must have**: `id` (kebab-case, unique), `name`, `category`, `maxPoints`, `earnedPoints`, `passed`, `detail`, and optional `suggestion`/`fix`. - **Fix object fields**: `action` (string describing what to do), `data` (context for the fix), `instruction` (user-facing guidance). - **Register in src/scoring/index.ts**: Add the import and spread the result into the `allChecks` array in `computeLocalScore()`. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_oaa6aq4p2acuk34j/2fe1ead62a0ee71ead06801b21db8d039d6f38c400568df7698ee99a9d8fa5f6.json
Then /plugin install scoring-checks@markdownregistry-oaa6aq4p2acuk34j in Claude Code. It installs git:20260428.99f2785, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add caliber-ai-org/ai-setup/scoring-checks@sha256:2fe1ead62a0ee71eThe line at the top of this page pins the label git:20260428.99f2785, 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_oaa6aq4p2acuk34j)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in caliber-ai-org/ai-setup/scoring-checks since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of scoring-checks from somewhere else? Ask it: where did my scoring-checks come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Mar 29, 2026 and Apr 28, 2026, about one every 10 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260428.99f2785 latest | 2026-04-28 | 99f2785 | 12,017 B | A | view · diff |
| git:20260425.203da12 | 2026-04-25 | 203da12 | 5,580 B | A | view · diff |
| git:20260424.9b749cd | 2026-04-24 | 9b749cd | 12,109 B | A | view · diff |
| git:20260329.8cf93fd | 2026-03-29 | 8cf93fd | 5,021 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/scoring-checks/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (12017 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
caliber-ai-org/ai-setup · 1,316 stars · license MIT · pushed 2026-09-24 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_oaa6aq4p2acuk34j GET https://markdownregistry.com/api/v1/resolve?ref=caliber-ai-org/ai-setup/scoring-checks GET https://markdownregistry.com/api/v1/blob/2fe1ead62a0ee71ead06801b21db8d039d6f38c400568df7698ee99a9d8fa5f6
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 caliber-ai-org/ai-setup
Every file in caliber-ai-org/ai-setup
Other files named scoring-checks
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.