Independently review The Blind Machine paper
AI agent skillIndependently review The Blind Machine paper the way a careful, skeptical referee would — verifying every claim against evidence rather than accepting it.
Download & use this skill
Download .tar.gz
Install the whole repository into your agent's skills directory in one command — it unpacks as a
ready-to-use review/ folder (change -C
to your skills path):
curl -fsSL https://blindmachine.org/skills/review/archive | tar xz -C ~/.claude/skills
Or fetch just the recipe to read or execute inline:
curl https://blindmachine.org/skills/review.md
---name: reviewdescription: >- Independently review The Blind Machine paper the way a careful, skeptical referee would — verifying every claim against evidence rather than accepting it. Use this whenever someone wants to review, referee, critique, fact-check, or assess The Blind Machine paper (blindmachine.org/papers/the-blind-machine): "review this paper", "referee report", "are the claims supported?", "check their numbers / security analysis / citations", "find problems with the paper", or "is anything overclaimed?". Walks six dimensions — claim-evidence integrity, the security catalog, honesty/overclaiming, citations and cross-references, reproducibility, and scope — and returns a severity-ranked review with a concrete fix per finding.---# Independently review The Blind Machine paperYou are an AI agent asked to **independently review** the paper *The Blind Machine:Governed Computation on Encrypted Data with Certificate-Bound, ReproducibleVerification*. Act as a careful, skeptical referee: your job is to find problems,not to praise. The paper is unusually checkable — its experiments are reproducibleand its numbers trace to committed result files — so verify claims against evidencerather than accepting the prose. Prefer a specific, reproducible finding over ageneral impression.## Inputs- The manuscript at https://blindmachine.org/papers/the-blind-machine (the `.md` form is the raw source).- The companion **replicate** skill (https://blindmachine.org/skills/replicate). Where a claim rests on an experimental number, re-run the relevant experiment or inspect its committed `results/` file rather than trusting the prose.## ProcedureWork through all six dimensions in **`references/review-dimensions.md`**, whichtells you exactly what to check in each:1. Claim-evidence integrity2. Security analysis (the per-attack catalog)3. Honesty and overclaiming4. Citation and cross-reference integrity5. Reproducibility6. Scope and framingFor the numeric claims in dimensions 1 and 3, check each value against**`references/claim-evidence-map.md`**, which lists the headline numbers and whereeach one comes from. Flag any value that does not match its source, any transposeddigit, and any table whose rows disagree with its cited data file.## OutputALWAYS return the review in this shape:```# Review: The Blind Machine**Verdict:** <one line — is the paper's central claim supported, and what is the biggest risk?>## Findings (most severe first)For each finding:- **Severity:** critical | high | medium | low- **Location:** section / table / line- **Problem:** what is wrong- **Evidence:** the source value or rule that proves it- **Fix:** the concrete change## Dimension summaryOne line per dimension (1-6) saying whether it is clean or where it failed.```State a dimension is clean explicitly rather than omitting it. Do not inventfindings; if you could not verify something (e.g., you could not run theexperiments), mark it **unverified** and say why. A short, honest review thatverified less is better than a long one that guessed.## Reference files- `references/review-dimensions.md` — the detailed checklist for each of the six dimensions.- `references/claim-evidence-map.md` — the headline numbers and their sources, for fact-checking dimensions 1 and 3.
Part of the Independently review The Blind Machine paper agent skill.