# Lattice Auditor

> Audit lattice-based cryptography for LWE/RLWE parameter soundness, noise sampling correctness, rejection-sampling safety, and decryption-failure assumptions.

- Skill: `yue-zhou1/lattice-auditor-2` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add yue-zhou1/lattice-auditor-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yue-zhou1/lattice-auditor-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: Yue-Zhou1 (https://skillmd.com/u/yue-zhou1)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yue-zhou1/lattice-auditor-2

---


# lattice-auditor

Domain auditor for lattice-based cryptographic implementations.

## When to Use

- Auditing LWE/RLWE parameter sets and claimed security levels
- Reviewing noise/distribution sampling and rejection-sampling code
- Checking seed/domain separation and key derivation paths
- Validating decapsulation behavior and decryption-failure assumptions

## When NOT to Use

- Traditional ECC-only audits without lattice constructs
- Standardized KEM API/state/serialization/decapsulation conformance
  (ML-KEM/FIPS 203 implicit rejection, input checks, rounding) ->
  `pqc-kem-auditor`; this skill keeps generic LWE/RLWE parameter and
  sampler reasoning
- High-level protocol reviews detached from parameter/sampling internals
- Declaring suspected lattice issues confirmed without verification gates

## Core Review Areas

1. Parameter-set provenance and claimed security margins
2. Distribution/noise sampling correctness and bias control
3. Domain separation for seeds and derivation contexts
4. Decryption failure bounds and constant-time decoding boundaries
5. KEM decapsulation checks and reject-path correctness

## Workflow

### Phase 1: Parameter and provenance intake

- Read `references/lattice-checklist.md`
- Execute `workflows/parameter-review.md`
- Map claimed scheme parameters to concrete code constants

### Phase 2: Sampling and failure-path review

- Trace sampling paths for noise and rejection behavior
- Validate decryption failure assumptions against implementation behavior
- Confirm decapsulation reject paths are strict and constant-time where required

### Phase 3: Pattern hunt

- Read `references/finding-patterns.md`
- Prioritize sampling bias, seed reuse, and failure-bound underestimation

### Phase 4: Handoff

- Send surviving findings to `crypto-fp-check`
- Use `zkbugs-index` only after the finding survives verification

## Output Contract

Produce a lattice-specific handoff that includes:

- The parameter set, sampling routine, or decapsulation path involved
- The concrete failure bound or bias condition at risk
- Whether the issue is parameter, sampling, seed-separation, or reject-path related
- The next verification or reporting route

## Reference Index

- [references/lattice-checklist.md](references/lattice-checklist.md)
- [references/finding-patterns.md](references/finding-patterns.md)
- [workflows/parameter-review.md](workflows/parameter-review.md)