Update to Cryptography Research Skills

{
  "description": "Draft or review cryptography prior-work comparisons and comparison tables by aligning models, construction variants, costs, and evidence. Use for positioning results, not literature discovery alone or benchmark execution.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 243
    },
    {
      "relative_path": "references/comparison-method.md",
      "size_in_bytes": 6727
    },
    {
      "relative_path": "references/source-patterns.md",
      "size_in_bytes": 8899
    },
    {
      "relative_path": "references/theorem-variant-cases.md",
      "size_in_bytes": 5283
    }
  ],
  "name": "crypto-prior-work-comparison",
  "skill_md_contents": "---\nname: crypto-prior-work-comparison\ndescription: Draft or review cryptography prior-work comparisons and comparison tables by aligning models, construction variants, costs, and evidence. Use for positioning results, not literature discovery alone or benchmark execution.\n---\n\n# Crypto Prior-Work Comparison\n\nMake clear what improves, under which conditions, and at what cost. Compare complete supported variants: one theorem's guarantee and another's efficiency do not form a new result.\n\nUse established cryptographic terms for the objects compared. Prefer “corrupted parties” when that is the set meant; name the supplied correlations, protocol phases, subprotocols, and comparison criteria instead of generic “endpoints,” “layers,” or “scalar” modifiers. Describe the actual communication operation and the specific overhead or parameter dependence that improves. Preserve precise technical uses and source-defined terms; wording does not establish a stronger comparison.\n\n## Fix what is being compared\n\nRecover the target claim before selecting baselines. Identify the task and output guarantee; adversary, corruption, assumptions and setup; construction version and parameter regime; and the cost's phase, unit, aggregation, denominator, and exclusions. Include only axes that matter to this comparison. Theory-only comparisons use definitions, theorems, and analytical bounds; they need no code or benchmarks.\n\nSelect the smallest baseline set that answers the claim: the closest predecessor, the strongest relevant result on each claimed axis, and other work that changes the interpretation. Use relevance, not the largest available ratio. A separate literature search is needed only if the supplied sources cannot support that choice.\n\n## Build and write the comparison\n\n1. Map each substantive claim or table cell to a primary-source version and locator. Verify attributions against that source; distinguish unverified supplied evidence. Preserve author implementations, independent reproductions, ports, and transformed variants as different lineages.\n2. Separate theorem-level, asymptotic, concrete analytical, and empirical results. Label numbers as measured, rerun, inherited, derived, estimated, or projected as applicable. A component rate or ideal-resource proxy is not end-to-end performance.\n3. Normalize comparable axes and disclose differences affecting the conclusion next to it. Missing or unreported work is not zero. A measured configuration without established concrete security cannot support a security-matched ranking merely from its parameter width.\n4. State the result and its mechanism or tradeoff under the aligned conditions. Give absolute values before ratios; recompute totals, conversions, amortization, and break-even points. Reconcile text, headers, captions, and formulas.\n5. Use the narrowest supported conclusion. Preserve prior work's remaining advantages and state incomparability where a conversion is unsupported.\n\nReview or suggested wording is read-only unless edits are requested. When editing, preserve the manuscript's notation and voice. Do not strengthen security, performance, or priority claims for rhetorical effect.\n\n## Optional detail\n\n- [Comparison method](references/comparison-method.md): substantial sections/tables, uncertain normalization, or mixed numerical provenance.\n- [Source patterns](references/source-patterns.md): examples of comparison structures and known table-consistency pitfalls.\n- [Theorem variant cases](references/theorem-variant-cases.md): incompatible variants, compressed quantitative premises, or a correction that changes a comparison's cost.\n\nUse `cryptography-writing` only when the task also requires broader narrative organization, and `crypto-literature-evidence` when additional source research is needed. The comparison itself should remain self-contained. Return reconstructible claims and material unresolved mismatches, without forcing a fixed paragraph order or evidence template onto a small edit.\n"
}