open-source-review SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
open-source-review from finolabs/vibecode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add finolabs/vibecode/open-source-review@git:20261112.f39c870Pins git:20261112.f39c870 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- finolabs/vibecode
- Path
skills/open-source-review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261112.f39c870, committed Nov 12, 2026
- First version recorded
- Nov 11, 2026
- Size
- 6,018 bytes
- Repository stars
- 4
- License
- MIT
Review a repository's readiness to be published as open source and report findings with evidence. Use before making a repository public, before a first public release, when publishing a plugin or skill package to a marketplace, when asked whether a repository is safe or ready to open source, or when checking a public repository's settings (branch and tag protection, secret scanning, vulnerability reporting).
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
# Open source review A read-only review: it finds and reports, it does not publish. Fixes, history rewrites, visibility changes and releases each need the owner's explicit authority. After a repository is public, run it again before each MINOR release and whenever `SECURITY.md`, CI or the repository settings change; a patch release does not need one. ## 1. Fix the scope Name the repository, the exact commit, and what will become public: the working tree, the full git history, release archives, or a packaged plugin. History counts unless the owner will publish a fresh history; say which. Done when the scope line is written in the report. ## 2. Run every check Mark each item **PASS**, **FAIL**, **N/A** (with why) or **BLOCKED** (with what is missing), and attach evidence: the command and its output, or the file and line. A tool that is not installed is BLOCKED, not PASS, unless the check names a fallback; a fallback result names the method it used. ### License - A `LICENSE` file at the root, and the same SPDX id in every manifest (`package.json`, plugin manifests, `pyproject.toml`). - Notices for vendored or copied third-party code, with their original licenses kept. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gsjmehpdep25jjj2/f1c9033bac40bf1b2b69d695b0294d2aa8d5042bb75edea4923b0c790393801f.json
Then /plugin install open-source-review@markdownregistry-gsjmehpdep25jjj2 in Claude Code. It installs git:20261112.f39c870, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add finolabs/vibecode/open-source-review@sha256:f1c9033bac40bf1bThe line at the top of this page pins the label git:20261112.f39c870, 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_gsjmehpdep25jjj2)
1 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 finolabs/vibecode/open-source-review 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 open-source-review from somewhere else? Ask it: where did my open-source-review 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 5 versions of this file, between Nov 11, 2026 and Nov 12, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261112.f39c870 latest | 2026-11-12 | f39c870 | 6,018 B | A | view · diff |
| git:20261112.767e3e7 | 2026-11-12 | 767e3e7 | 9,946 B | A | view · diff |
| git:20261112.0e06d0c | 2026-11-12 | 0e06d0c | 10,369 B | A | view · diff |
| git:20261112.97d8713 | 2026-11-12 | 97d8713 | 10,268 B | A | view · diff |
| git:20261111.8b208c3 | 2026-11-11 | 8b208c3 | 9,308 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/open-source-review/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 (6018 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
finolabs/vibecode · 4 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gsjmehpdep25jjj2 GET https://markdownregistry.com/api/v1/resolve?ref=finolabs/vibecode/open-source-review GET https://markdownregistry.com/api/v1/blob/f1c9033bac40bf1b2b69d695b0294d2aa8d5042bb75edea4923b0c790393801f
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 finolabs/vibecode
Every file in finolabs/vibecode