crypto-idea-evaluator
Use when turning a cryptography, ZKP, or lattice idea into a research question, claim map, feasibility assessment, evidence plan, risk register, or go/no-go decision.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- crypto-idea-evaluator
- description
- Use when turning a cryptography, ZKP, or lattice idea into a research question, claim map, feasibility assessment, evidence plan, risk register, or go/no-go decision.
02 资源文件 5
- 许可证LICENSE1.0 KB
- 参考文档references/evaluation-scenarios.md1.2 KB
- 参考文档references/protocol.md2.4 KB
- 参考文档SOURCE.md383 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Crypto Idea Evaluator
Convert an informal idea into falsifiable research claims and a decision-ready brief. Do not assume significance, novelty, correctness, security, or performance.
Scope
In scope: problem/claim formalization, baseline and threat-model selection, assumption/parameter inventory, proof and experiment obligations, feasibility/significance risks, ethics, and kill criteria.
Out of scope: declaring novelty without search, proving theorems, inventing results, writing a finished paper, or submitting/publishing anything.
Required Inputs
- the proposed construction, technique, observation, or target improvement;
- intended primitive/protocol, security notion/model, adversary, and use case;
- expected difference from known baselines;
- available theory, implementation, data, compute, and time constraints.
Ask for missing information only when it changes the core research question. Otherwise state assumptions.
Success Criteria
- The idea becomes explicit research questions and falsifiable claims.
- Functionality, security, efficiency, usability, and novelty claims are separated.
- Each claim has required proof, literature, parameter, or experimental evidence.
- Baselines, closest-work search needs, assumptions, threat model, parameters, and ethical risks are visible.
- Feasibility risks and kill/pivot criteria are concrete.
- The recommendation is proceed, proceed with prerequisites, pivot, or stop—never “promising” without evidence.
Failure Modes
- Vague idea: return alternative formalizations and request the decisive missing delta.
- Unstated security model: block security conclusions and list candidate models.
- Novelty premise: mark unverified and require a bounded prior-art search.
- Unavailable resources: propose a smaller falsifiable study or mark infeasible.
- Ethical/responsible-disclosure risk: require human review before data collection, attack execution, or disclosure.
- Contradictory goals: expose the tradeoff and request a priority decision.
Never fabricate prior art, proof obligations already discharged, benchmark results, parameters, or reviewer interest.
Workflow
- Apply protocol.md to formalize the object, claim map, baselines, model, assumptions, and evidence obligations.
- Create adversarial alternative explanations and fastest falsification tests.
- Define minimum viable theorem/prototype/experiment and kill criteria.
- Produce a staged research brief with dependencies and human decisions.
- Use evaluation-scenarios.md for future independent evaluation; do not claim it ran unless outputs were inspected.
Output Contract
Return: idea statement; research questions; claim-evidence matrix; threat/setup model; baselines and novelty-search brief; proof/parameter/experiment plan; significance and ethics analysis; risks; kill/pivot criteria; next three actions; bounded recommendation.
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.