crypto-paper-review
Use when pre-reviewing, peer reviewing, stress-testing, or assessing submission readiness of a cryptography, ZKP, lattice, or security paper for a leading research venue.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- crypto-paper-review
- description
- Use when pre-reviewing, peer reviewing, stress-testing, or assessing submission readiness of a cryptography, ZKP, lattice, or security paper for a leading research venue.
02 资源文件 5
- 许可证LICENSE1.0 KB
- 参考文档references/evaluation-scenarios.md960 B
- 参考文档references/protocol.md2.5 KB
- 参考文档SOURCE.md381 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Crypto Paper Review
Perform an adversarial, evidence-located review. Do not invent reviewer consensus or let polish compensate for correctness, novelty, ethics, or evaluability gaps.
Scope
In scope: venue fit, contribution/significance, novelty/prior art, definitions/theorems/proofs/reductions, ZKP/lattice specifics, parameters/complexity, experiments/artifacts, clarity, ethics/disclosure/open science, reproducibility, and revision priority.
Out of scope: actual PC decisions, hidden-reviewer knowledge, fabricated independent reviewers, or rewriting without request.
Required Inputs
- exact manuscript/version and supplements/artifacts;
- target venue and current official policies, if venue-specific;
- claimed contributions and evidence map when available;
- desired mode: quick triage, full review, methodology/proof focus, or re-review.
Success Criteria
- Every major claim is tested against evidence and closest-work context.
- Findings cite exact manuscript/artifact locations and consequences.
- Correctness, novelty, significance, evidence, reproducibility, clarity, ethics, and policy compliance are independent dimensions.
- ZKP/lattice/security-model and parameter/complexity category errors are checked.
- Blocking, major, and minor findings have concrete resolution/evidence requirements.
- Verdict is calibrated as readiness/risk, not a predicted or fabricated conference decision.
- A re-review verifies each claimed repair and detects regressions.
Failure Modes
- Missing manuscript/artifact/version: limit review and mark unseen evidence.
- Unknown venue policy: give venue-neutral review; do not claim compliance.
- Citation/full proof inaccessible: keep dependent claims unverified.
- Same-agent multi-perspective pass: label it non-independent.
- Manuscript advocacy pressure: preserve disconfirming findings.
Never fabricate citations, proof checks, artifact runs, reviewer opinions, scores, or acceptance probabilities.
Workflow
- Apply protocol.md to freeze claims/evidence and target-venue gates.
- Run sequential lenses: fit/significance; novelty; correctness/security; parameters/evidence; reproducibility/ethics; exposition/adversarial challenge.
- Consolidate duplicate findings without erasing disagreement or uncertainty.
- Return severity-ranked report, readiness verdict, and revision plan.
- In re-review, map each prior finding to exact changed evidence.
- Use evaluation-scenarios.md for future independent evaluation.
Output Contract
Return: scope/version/policy snapshot; paper and contribution summary; strengths; blocking/major/minor findings with locations; claim-evidence and domain audits; novelty/closest-work risks; artifact/ethics/compliance risks; questions to authors; readiness verdict; ordered revision plan; unverified items.
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.