review-external-pr
mad-labs-org/tbh-meterAdversarial, security-first review of a pull request from an EXTERNAL or untrusted contributor — a fork PR, a first-time or unknown author, anyone without…
Scores out of 100 · grade B+
2026-08-13Works
40% of the score86/100
- References 2 files that are not in the repo: CONTRIBUTING.md, requirements-dev.txt.
Maintained
25% of the score100/100
- no commits in the last 12 weeks
Adopted
20% of the score22/100
- 38 stars on the source repo.
Documented
15% of the score90/100
- 2,197 words with worked examples.
- Ships 2 bundled files.
Install
npx skills add mad-labs-org/tbh-meter/review-external-prWhat the check found
| Finding | What it means |
|---|---|
| Missing files | It points at files that are not in the repository, so those steps will fail. |
Files it references that are not in the repository
What it says it does
Adversarial, security-first review of a pull request from an EXTERNAL or untrusted contributor — a fork PR, a first-time or unknown author, anyone without write access — before a maintainer merges it. Use this whenever you're reviewing, triaging, or deciding whether to merge a PR opened against tbh-meter by someone outside the maintainer team: 'review PR #123', 'someone opened a PR — is it safe to merge?', 'check this contributor's changes', 'can we take this fork PR?', 'is this contribution legit?'. This is supply-chain DEFENSE, not ordinary code review: every merged PR auto-updates onto every user's machine and ships a memory-reading .exe plus an unsandboxed Electron app, so the author and the PR description are UNTRUSTED and the diff is the only evidence. It posts its verdict as a real GitHub review — an inline comment pinned to each problematic line (via the pulls/reviews API), not just one summary comment. NOT for your own or a fellow maintainer's branch (use self-review for that), and prefer this over the generic review flow for anything coming from outside the team.
Also in mad-labs-org/tbh-meter
| Artifact | Score | What the check found | Type | Reach | Last commit |
|---|---|---|---|---|---|
| tbh-commitmad-labs-org/tbh-meter | clean | Skill | 38 stars | today | |
| meter-debugmad-labs-org/tbh-meter | clean | Skill | 38 stars | today | |
| self-reviewmad-labs-org/tbh-meter | clean | Skill | 38 stars | today | |
| reader-engineermad-labs-org/tbh-meter | clean | Subagent | 38 stars | today | |
| devmad-labs-org/tbh-meter | clean | Skill | 38 stars | today | |
| meter-engineermad-labs-org/tbh-meter | clean | Subagent | 38 stars | today |
Other code review skills
Browse all| Artifact | Score | What the check found | Category | Reach | Last commit |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowers | clean | Code review | 172,299 installs | yesterday | |
| scaffold-exercisesmattpocock/skills | clean | Code review | 237,069 installs | today | |
| financial-statementsanthropics/knowledge-work-plugins | clean | Code review | 3,707 installs | today | |
| review-contractanthropics/knowledge-work-plugins | clean | Code review | 3,005 installs | today | |
| backport-prvercel/next.js | clean | Code review | 142k stars | today | |
| create-prvercel/next.js | clean | Code review | 142k stars | today |
Put this measurement in your README
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://skillworks.kynth.studio/?q=mad-labs-org%2Ftbh-meter)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.
