Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files.

MITAuto-check: notes

Install Paper Claim Audit

skills CLI
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill paper-claim-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wanshuiyin/Auto-claude-code-research-in-sleep paper-claim-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills-codex/paper-claim-audit .claude/skills/paper-claim-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
paper-claim-audit
GitHub stars
17k
Used in
1 other repo
Token cost
~3.5k tokens
SKILL.md length
905 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files.

  • Works in 4 steps: Collect Files (Executor — Codex) → Fresh Reviewer Audit (GPT-6-Astra — NEW… → Write Report (Executor — Codex) → …
  • User says 审查论文数据
  • SKILL.md covers Why This Exists, How This Differs From Other…, Core Principle and Workflow, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Paper Claim Audit is an agent skill from wanshuiyin/Auto-claude-code-research-in-sleep. Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files. Uses a fresh Codex reviewer with no prior context; base output is same-family provisional. Use when user says "审查论文数据", "check paper claims", "verify numbers", "论文数字核对", or before submission to ensure paper-to-evidence fidelity.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: ARIS ⚔️ (Auto-Research-In-Sleep) — Lightweight Markdown-only skills for autonomous ML research: cross-model review loops, idea discovery, and experiment automation. No framework… The licence is MIT.

When your agent uses it

  • User says 审查论文数据
  • Check paper claims
  • Before submission to ensure paper-to-evidence fidelity

Example prompts

  • “审查论文数据”
  • “check paper claims”
  • “verify numbers”
  • “/paper-claim-audit”

Requirements

  • Pre-approved tools (allowed-tools): Bash(*), Read, Write, Edit, Grep, Glob

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Collect Files (Executor — Codex)
  2. Fresh Reviewer Audit (GPT-6-Astra — NEW thread, no reply)
  3. Write Report (Executor — Codex)
  4. Print Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 26b95cf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(*)
    • Read
    • Write
    • Edit
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Paper Claim Audit loads about 3.5k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 905 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wanshuiyin/Auto-claude-code-research-in-sleep at commit 26b95cf, republished under its MIT licence (© wanshuiyin). 905 words, ~3,455 tokens.

Download SKILL.mdSave it as .claude/skills/paper-claim-audit/SKILL.md (or your agent's skills folder).
name
paper-claim-audit
description
Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files. Uses a fresh Codex reviewer with no prior context; base output is same-family provisional. Use when user says "审查论文数据", "check paper claims", "verify numbers", "论文数字核对", or before submission to ensure paper-to-evidence fidelity.
allowed-tools
Bash(*), Read, Write, Edit, Grep, Glob
argument-hint
[paper-directory]

Paper Claim Audit: Zero-Context Evidence Verification

Codex assurance: write review_independence: same-family and acceptance_status: provisional into base audit JSON. A fresh Codex PASS may advance the pipeline but cannot produce submission-ready yes. Missing/failed review emits BLOCKED; overlay/deterministic acceptance uses accepted.

Verify that every claim in the paper matches raw evidence for: $ARGUMENTS

Why This Exists

The executor writes experiments AND writes the paper. It "knows" what the results should be. This creates confirmation bias:

  • Rounding 84.7% up to 85.3%
  • Reporting best seed instead of average
  • Citing metrics from a different experiment config
  • Claiming "improves by 15%" when the delta is actually 12.8%

A fresh reviewer with zero prior context catches these because it has no expectations — it just compares paper text vs raw files.

How This Differs From Other Audit Skills

SkillQuestion it answers
/experiment-auditIs the experiment code honest? (fake GT, normalization fraud)
/result-to-claimDoes the data scientifically support this claim?
/paper-claim-auditDoes the paper report the data truthfully and precisely?

Core Principle

Zero-context, fresh reviewer. The auditor receives ONLY:

  • Paper .tex files (the claims)
  • Raw result files (the evidence)

It does NOT receive:

  • ❌ EXPERIMENT_LOG.md
  • ❌ EXPERIMENT_TRACKER.md
  • ❌ AUTO_REVIEW.md
  • ❌ NARRATIVE_REPORT.md
  • ❌ Any executor summary or interpretation
  • ❌ Any prior audit results
  • ❌ Any conversation history

This is stricter than reviewer-independence — it's zero-context evidence audit.

Workflow

Step 1: Collect Files (Executor — Codex)

Locate paper and result files WITHOUT reading or interpreting them.

Paper files (claims) — paths shown relative to the shell's working directory so you can find them with ls; when writing them into audited_input_hashes, use paths relative to the paper dir (no paper/ prefix) per the "Submission Artifact Emission" section below:

paper/main.tex                # → hash key: main.tex
paper/sections/*.tex          # → hash key: sections/*.tex
paper/tables/*.tex (if separate)   # → hash key: tables/*.tex

Result files (evidence):

results/*.json, results/*.jsonl, results/*.csv, results/*.tsv
outputs/*.json, outputs/*.csv
wandb-summary.json (if exists)
**/metrics.json, **/eval_results.json
**/config.yaml, **/args.json (experiment configs)

Exclude (no summaries, no interpretations):

EXPERIMENT_LOG.md, EXPERIMENT_TRACKER.md, AUTO_REVIEW*.md
NARRATIVE_REPORT.md, PAPER_PLAN.md, findings.md
Any .md file that is an executor-written summary
Step 2: Fresh Reviewer Audit (GPT-6-Astra — NEW thread, no reply)

CRITICAL: Use a fresh reviewer agent every run. Never reuse an old reviewer context for this audit.

text
spawn_agent:
  model: gpt-6-astra
  reasoning_effort: ultra
  message: |
    You are a paper-to-evidence auditor. You have ZERO prior context about
    this research. You will receive only paper source files and raw result
    files. Your job is to verify that every number in the paper exactly
    matches the raw evidence.

    Paper files to read:
    [list .tex file paths]

    Result files to read:
    [list .json/.csv/.yaml file paths]

    ## Audit Protocol

    ### A. Extract Every Quantitative Claim
    For each number, percentage, comparison, or scope statement in the paper:
    - Location (section, table, caption, or inline text)
    - Exact claim text
    - The number or comparison being made

    ### B. Trace Each Claim to Evidence
    For each extracted claim, find the supporting raw data:
    - Which result file contains this number?
    - What is the EXACT value in that file?
    - Match status: exact_match / rounding_ok / mismatch

    ### C. Check These Specific Failure Modes

    1. **Number inflation**: Paper says 85.3%, raw file says 84.7%
       Rule: only standard rounding to displayed precision is allowed

    2. **Best-seed cherry-pick**: Paper says "achieves 90.2%" but
       that's the best of 5 seeds; mean is 87.1%
       Rule: check if paper specifies "average" / "best" / "median"

    3. **Config mismatch**: Paper compares Method A vs Baseline B,
       but they used different hyperparameters / datasets / splits
       Rule: verify config files show same settings for compared methods

    4. **Aggregation mismatch**: Paper says "average over 5 seeds"
       but result files show only 3 runs
       Rule: count actual runs vs claimed count

    5. **Delta error**: Paper says "improves by 15%" but
       actual delta is (85.3 - 73.1) / 73.1 = 16.7%
       Rule: verify arithmetic of all relative improvements

    6. **Caption-table mismatch**: Figure caption describes
       something different from what the figure/table actually shows
       Rule: cross-check every caption against its content

    7. **Scope overclaim**: Paper says "consistently outperforms"
       but only tested on 2 datasets
       Rule: check if language matches actual evaluation scope

    ## Output Format (per claim)
    For each claim, report:
    - claim_id: sequential number
    - location: section/table/figure
    - paper_text: exact quote from paper
    - paper_value: the number claimed
    - evidence_file: which raw file
    - evidence_value: the actual number
    - status: exact_match | rounding_ok | ambiguous_mapping |
              missing_evidence | config_mismatch | aggregation_mismatch |
              number_mismatch | scope_overclaim | unsupported_claim
    - details: explanation if not exact_match

    Overall verdict: PASS | WARN | FAIL
Step 3: Write Report (Executor — Codex)

Parse the reviewer's response and write PAPER_CLAIM_AUDIT.md:

markdown
# Paper Claim Audit Report

**Date**: [today]
**Auditor**: GPT-6-Astra ultra (fresh zero-context thread)
**Paper**: [paper title from tex]

## Overall Verdict: [PASS | WARN | FAIL]

## Claims Verified: [N total]
- exact_match: [count]
- rounding_ok: [count]
- ambiguous_mapping: [count]
- missing_evidence: [count]
- mismatch: [count]

## Issues Found

### [FAIL/WARN] Claim #N: [description]
- **Location**: Section X / Table Y / Figure Z
- **Paper says**: "..."
- **Evidence shows**: ...
- **Status**: [status]
- **Fix**: [specific correction needed]

## All Claims (detailed)

| # | Location | Paper Value | Evidence Value | Status |
|---|----------|-------------|---------------|--------|
| 1 | Table 2 | 85.3% | 85.28% | rounding_ok |
| 2 | Abstract | "15% improvement" | 12.8% | number_mismatch |
| ... |

Also write PAPER_CLAIM_AUDIT.json for machine consumption.

Step 4: Print Summary
📋 Paper Claim Audit Complete

  Claims verified: 24
  exact_match:     18
  rounding_ok:      3
  ambiguous:         1
  ⚠️ mismatch:      2

  Overall: ⚠️ WARN

  See PAPER_CLAIM_AUDIT.md for details.

When to Run

  1. After /paper-write — first check before improvement loop
  2. After /auto-paper-improvement-loop — recheck if improvement loop changed numbers
  3. Before submission — final verification

Integration with Other Skills

Read by /auto-paper-improvement-loop (if exists)
if PAPER_CLAIM_AUDIT.json exists:
    read mismatched claims
    fix them as priority items in the improvement round
Advisory, Never Blocking

Same pattern as /experiment-audit:

  • PASS → continue normally
  • WARN → print warning, continue, flag draft as "check numbers before submission"
  • FAIL → print alert, continue, but do NOT mark as submission-ready

Render HTML view (auto, when RENDER_HTML = true, default)

After writing paper/PAPER_CLAIM_AUDIT.md and paper/PAPER_CLAIM_AUDIT.json, invoke /render-html on the audit report:

/render-html "paper/PAPER_CLAIM_AUDIT.md" --json "paper/PAPER_CLAIM_AUDIT.json"

Uses full review gate (audit-class artifact; base Codex review is fresh same-family provisional). Output: paper/PAPER_CLAIM_AUDIT.html with embedded source SHA256 + .review.json sidecar.

Non-blocking: if /render-html fails (helper missing, secondary Codex agent unavailable, file write error), log the failure and treat the audit as complete — the JSON + MD verdict files are canonical; the HTML view is a human-reader convenience.

Skip if RENDER_HTML = false is set in AGENTS.md / CLAUDE.md or passed as — render html: false.

Key Rules

  • Fresh thread EVERY run. Never use a continuation reply. Never carry context.
  • Zero executor interpretation. Only file paths. No summaries.
  • Only raw results. No EXPERIMENT_LOG, no AUTO_REVIEW, no human summaries.
  • Rounding rule. Only standard rounding to displayed precision. 84.7% → 84.7% or 85% is OK. 84.7% → 85.3% is NOT OK.
  • Review class. Base Codex reviewer is same-family provisional; only an overlay may record cross-family accepted.
Show full SKILL.md (358 more words)Show less

Review Tracing

After each reviewer agent call, save the trace following shared-references/review-tracing.md (Policy C — forensic; never silently skip). Use save_trace.sh (resolved per the chain in shared-references/integration-contract.md §2) or write files directly to .aris/traces/<skill>/<date>_run<NN>/. Respect the --- trace: parameter (default: full).

Submission Artifact Emission

This skill always writes paper/PAPER_CLAIM_AUDIT.json, regardless of caller or detector outcome. A detector-negative run (paper has no numeric claims) emits verdict NOT_APPLICABLE; a paper-with-numeric-claims-but-no- raw-results run emits BLOCKED. Silent skip is forbidden — paper-writing Phase 6 and verify_paper_audits.sh both rely on this artifact existing at a predictable path.

The artifact conforms to the schema in shared-references/assurance-contract.md:

json
{
  "audit_skill":      "paper-claim-audit",
  "verdict":          "PASS | WARN | FAIL | NOT_APPLICABLE | BLOCKED | ERROR",
  "reason_code":      "all_numbers_match | rounding_drift | missing_raw_results | ...",
  "summary":          "One-line human-readable verdict summary.",
  "audited_input_hashes": {
    "main.tex":                              "sha256:...",
    "sections/5.evidence.tex":               "sha256:...",
    "/abs/path/to/results/run_2026_04_19.json": "sha256:..."
  },
  "trace_path":       ".aris/traces/paper-claim-audit/<date>_run<NN>/",
  "thread_id":        "<codex mcp thread id>",
  "executor_model":   "codex-gpt-6-astra",
  "executor_family":  "openai",
  "reviewer_model":   "gpt-6-astra",
  "reviewer_family":  "openai",
  "review_independence": "same-family",
  "acceptance_status": "provisional",
  "reviewer_reasoning": "ultra",
  "generated_at":     "<UTC ISO-8601>",
  "details": {
    "total_claims":   <int>,
    "mismatches":     [ ... per-claim issue records ... ],
    "result_files":   [ ... raw files consulted ... ]
  }
}
audited_input_hashes scope

Hash the declared input set passed into this audit invocation — i.e. the exact .tex files and raw result / config files this run read — not a repo-wide union and not the reviewer's self-reported subset. If a caller passed only main.tex + a single result file, hash those two files and no others. The external verifier rehashes these entries; any mismatch flags STALE.

Path convention (must match what verify_paper_audits.sh expects): keys are paths relative to the paper directory (the arg passed to the verifier) for in-paper files — so main.tex, not paper/main.tex — and absolute paths for out-of-paper files such as external results/ dirs. The verifier resolves relative entries via os.path.join(paper_dir, key); prefixing with paper/ produces paper/paper/main.tex and false-fails as STALE.

Verdict decision table
Input stateVerdictreason_code example
No numeric claims detected in paperNOT_APPLICABLEno_numeric_claims
Numeric claims detected, no raw result files foundBLOCKEDno_raw_evidence
All claims reconcile to raw dataPASSall_numbers_match
Minor rounding drift only, no material mismatchWARNrounding_drift
Any material mismatch (wrong number, config mismatch)FAILclaim_mismatch
Reviewer invocation failed (network / malformed)ERRORreviewer_error
Thread independence

Every invocation uses a fresh reviewer agent. Never continue a prior audit via send_input. Do not accept prior audit outputs (PROOF_AUDIT, CITATION_AUDIT, EXPERIMENT_LOG, AUTO_REVIEW summaries) as input to this audit — the fresh thread preserves reviewer independence per shared-references/reviewer-independence.md.

Human-readable sibling

paper/PAPER_CLAIM_AUDIT.md is written alongside the JSON for readers. The JSON is authoritative for verify_paper_audits.sh; the Markdown is for humans. The parent skill (paper-writing Phase 6) plus the verifier decide whether the verdict blocks finalization — this skill itself never blocks; it only emits.

© wanshuiyin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/skills-codex/paper-claim-audit of wanshuiyin/Auto-claude-code-research-in-sleep.

Open the folder on GitHubat commit 26b95cf

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wanshuiyin/Auto-claude-code-research-in-sleep, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Paper Claim Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Paper Claim Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Paper Claim Audit this skillwanshuiyin/Auto-claude-code-research-in-sleep17k1 repos~3.5kAutomated safety check: NotesMIT
Claimsruvnet/ruflo74k1 repos~1.1kAutomated safety check: PassMIT
Zero Trustsickn33/agentic-awesome-skills47k2 repos~3.2kAutomated safety check: PassMIT
Gaia Architecture Comparisonruvnet/ruflo74k—~1.3kAutomated safety check: NotesMIT
Cloudflare Zero Trustsickn33/agentic-awesome-skills47k2 repos~2.8kAutomated safety check: WarnMIT
Bio Copy Number Subclonal Copy NumberGPTomics/bioSkills1.2k2 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Claims

    ruvnet/ruflo

    Claims-based authorization for agents and operations. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 1 repo~1.1k tokens
    Backend & APIsAuto-check passed
  • Zero Trust

    sickn33/agentic-awesome-skills

    Implement zero-trust network architecture. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~3.2k tokens
    Backend & APIsAuto-check passed
  • Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap

    74k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Cloudflare Zero Trust

    sickn33/agentic-awesome-skills

    Protect internal apps with Cloudflare Access, device posture, and Zero Trust policies.

    47k GitHub starsUsed in 2 repos~2.8k tokens
    DevOps & CloudAuto-check: warnings
  • Resolve subclonal copy number, whole-genome doubling, and copy-number tumor evolution from bulk sequencing with Battenberg, TITAN, and MEDICC2.

    1.2k GitHub starsUsed in 2 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Perf Comparison

    ClickHouse/ClickHouse

    Evaluate ClickHouse performance test results from existing CI/dashboard data or local perf.py runs.

    50k GitHub stars~3.9k tokensUpdated today
    DatabasesAuto-check: notes

More from wanshuiyin/Auto-claude-code-research-in-sleep

All 26 skills in this repo
  • Academic Poster Builder

    wanshuiyin/Auto-claude-code-research-in-sleep

    Builds an academic conference poster as a single HTML and CSS file with measurement-based gates, real paper figures and a print-ready PDF rendered through headless Chromium.

    17k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check: notes
  • Proof Run Orchestrator

    wanshuiyin/Auto-claude-code-research-in-sleep

    Runs a mathematical proof project as a stateful pipeline of run directories: a local attempt first, then a manual GPT Pro handoff package, with an optional DeepSeek audit.

    17k GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check passed
  • Render HTML

    wanshuiyin/Auto-claude-code-research-in-sleep

    Render an ARIS Markdown / JSON artifact (IDEAREPORT, AUTOREVIEW, KILLARGUMENT, PAPERPLAN, research-wiki state, etc.) into a single-file HTML view designed for human reading.

    17k GitHub starsUsed in 1 repo~5.4k tokens
    Auto-check: notes
  • Experiment Audit

    wanshuiyin/Auto-claude-code-research-in-sleep

    Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.

    17k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check: notes
  • Integrity Forensics

    wanshuiyin/Auto-claude-code-research-in-sleep

    Run the Anti-Autoresearch integrity-forensics DETERMINISTIC slice (numeric core + rules-only reporter) against a paper via a SHA-pinned thin launcher, then convert the verdict into a typed policy…

    17k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Interview Cheatsheet

    wanshuiyin/Auto-claude-code-research-in-sleep

    Generate a long-form Chinese interview-prep cheat sheet on a specific ML/LLM topic — formulas with derivations, from-scratch PyTorch code, comparison tables, and 25 高频面试题 (L1 必会 / L2 进阶 / L3 顶级 lab).

    17k GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check: notes

Questions about Paper Claim Audit

What does Paper Claim Audit do?

Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files. Paper Claim Audit is an agent skill from wanshuiyin/Auto-claude-code-research-in-sleep. Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files.

When should I use Paper Claim Audit?

Paper Claim Audit fits situations like: user says 审查论文数据; check paper claims; before submission to ensure paper-to-evidence fidelity.

How do I install Paper Claim Audit in Claude Code?

Run `npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill paper-claim-audit -a claude-code`. Or copy the skill folder (skills/skills-codex/paper-claim-audit in wanshuiyin/Auto-claude-code-research-in-sleep) into .claude/skills/paper-claim-audit in your project. Claude Code loads it when a task matches its description.

How do I install Paper Claim Audit in Codex?

Run `npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill paper-claim-audit -a codex`. Or copy the skill folder (skills/skills-codex/paper-claim-audit in wanshuiyin/Auto-claude-code-research-in-sleep) into .agents/skills/paper-claim-audit in your project. Codex loads it when a task matches its description.

Can I use Paper Claim Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill paper-claim-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paper-claim-audit, .gemini/skills/paper-claim-audit, .github/skills/paper-claim-audit and .opencode/skills/paper-claim-audit in your project.

What does Paper Claim Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Paper Claim Audit is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(*), Read, Write, Edit, Grep, Glob.

Does Paper Claim Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Paper Claim Audit safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Paper Claim Audit use?

Paper Claim Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Paper Claim Audit use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Paper Claim Audit?

Skills that share tags, products or a category with Paper Claim Audit: Claims (ruvnet/ruflo, 74k stars), Zero Trust (sickn33/agentic-awesome-skills, 47k stars), Gaia Architecture Comparison (ruvnet/ruflo, 74k stars) and Cloudflare Zero Trust (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Paper Claim Audit?

wanshuiyin (a GitHub user) maintains it in wanshuiyin/Auto-claude-code-research-in-sleep, which has 17,205 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.

Source: wanshuiyin/Auto-claude-code-research-in-sleep on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.