crypto-related-work-synthesis
Use when synthesizing a verified cryptography, ZKP, or lattice paper corpus into a taxonomy, historical development, claim comparison, tradeoff map, research gaps, or related-work section evidence base.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- crypto-related-work-synthesis
- description
- Use when synthesizing a verified cryptography, ZKP, or lattice paper corpus into a taxonomy, historical development, claim comparison, tradeoff map, research gaps, or related-work section evidence base.
02 资源文件 5
- 许可证LICENSE1.0 KB
- 参考文档references/evaluation-scenarios.md745 B
- 参考文档references/protocol.md1.6 KB
- 参考文档SOURCE.md391 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Crypto Related Work Synthesis
Synthesize relations among verified works. Do not substitute topical similarity for claim-level evidence or turn a corpus gap into global novelty.
Scope
In scope: corpus normalization, taxonomy, chronological/intellectual lineage, compatible comparison, assumption/model/parameter tradeoffs, contradictions, limitations, and evidence-linked gap statements.
Out of scope: broad discovery without a corpus, one-paper deep reading, proof verification, universal novelty, or prose polishing detached from evidence.
Required Inputs
- screened corpus with exact versions and verification status;
- synthesis question and intended contribution/section;
- inclusion/exclusion and coverage boundaries;
- claim-evidence records or access to inspected papers.
Success Criteria
- Work/version identity and claim-support status remain visible.
- Taxonomy axes are technically meaningful, mutually explained, and evidence-backed.
- Comparisons align security model, assumptions, parameters, functionality, and cost model.
- Historical influence/citation claims are verified rather than inferred from dates.
- Contradictions and non-comparable results remain explicit.
- Gap statements are bounded by corpus/search coverage and distinguish missing study from impossible/unknown result.
Failure Modes
- Abstract-only corpus: produce a provisional topic map, not technical synthesis.
- Mixed/unknown versions: stop affected comparisons until reconciled.
- Incompatible metrics: qualify rather than rank.
- Sparse corpus: return coverage gaps and next-search needs.
- Advocacy request: preserve adverse closest work and counterevidence.
Never fabricate citations, relationships, priorities, theorem content, or comparative superiority.
Workflow
- Apply protocol.md to normalize the corpus and build claim-level comparison axes.
- Construct taxonomy, lineage, tradeoff/contradiction matrix, and bounded research gaps.
- Trace every synthesis sentence to verified corpus entries or label it interpretation.
- Return an evidence map usable for writing, plus unresolved search/verification needs.
- Use evaluation-scenarios.md for future independent evaluation.
Output Contract
Return: corpus/version summary; synthesis question; taxonomy with rationale; chronology/influence map; claim-comparison matrix; assumption/model/parameter/cost tradeoffs; contradictions; bounded gaps; evidence-linked outline; excluded/unverified items; next searches.
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.