← ClaudeAtlas

pqblockslisted

Post-quantum engineering with the PQBlocks packages. Use when adding, migrating or auditing cryptography for the quantum threat (ML-KEM / FIPS 203, ML-DSA / FIPS 204, SLH-DSA / FIPS 205, Kyber, Dilithium, hybrid X25519 + ML-KEM), signing or encrypting JWTs post-quantum, encrypting files post-quantum, finding RSA / ECC in code, producing a CBOM, CNSA 2.0 compliance, checking TLS for X25519MLKEM768, running NIST ACVP vectors, or solving QUBO / Ising / Max-Cut problems with quantum-inspired solvers.
PQBlocks/pqblocks-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill PQBlocks/pqblocks-skills
<!-- GENERATED by scripts/gen_skills.py from data/catalog.json - do not edit by hand --> # PQBlocks: post-quantum engineering PQBlocks is an open-source organisation that builds verified post-quantum (PQ) components: cryptography, migration and readiness tooling, protocol interoperability, conformance testing and quantum-inspired optimisation. 32 packages, Apache-2.0, docs at https://pqblocks.github.io. ## Rules 1. **Use the documented API only.** Before writing code with a PQBlocks package, read its reference file below (or call the `get_snippet` tool of the `pqblocks-mcp` server). Every quickstart there was executed against the package. Never guess function names. 2. **Never hand-roll post-quantum cryptography.** Use the packages; they wrap maintained implementations (liboqs, pyca/cryptography). 3. **Hybrid by default during the transition:** ML-KEM-768 + X25519 for key establishment, ML-DSA-65 + Ed25519 for signatures. Downgrade to classical-only must be explicit. 4. **Randomness from the OS only.** Never pass a `seed` argument when generating production keys; seeds exist for reproducible tests. 5. **Never log or return secret keys or shared secrets** (logs, exceptions, HTTP responses, `repr`). 6. **Say exactly what is true.** PQBlocks packages implement FIPS 203/204/205 and test against official vectors where they exist. They are **not** FIPS 140-3 / CMVP validated, not externally audited, and pre-1.0. Never call them certified, validated, audited