[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B8TWHNND34XGYDXM8A8TTC":3,"skill-same:01M7B8TWHNND34XGYDXM8A8TTC":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M7B8TWHNND34XGYDXM8A8TTC","performing-post-quantum-cryptography-migration",null,"Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203\u002F204\u002F205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use when planning or executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-post-quantum-cryptography-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-post-quantum-cryptography-migration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-post-quantum-cryptography-migration\ndescription: 'Assesses organizational readiness for post-quantum cryptography migration\n  per NIST FIPS 203\u002F204\u002F205 standards. Performs cryptographic inventory scanning to\n  identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS\n  configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium\n  (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for\n  OpenSSL. Use when planning or executing the transition from classical to post-quantum\n  cryptographic algorithms across enterprise infrastructure.\n\n  '\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- post-quantum\n- PQC\n- CRYSTALS-Kyber\n- ML-KEM\n- ML-DSA\n- FIPS-203\n- FIPS-204\n- hybrid-TLS\n- crypto-agility\nversion: '1.0'\nauthor: mukul975\nlicense: Apache-2.0\nnist_csf:\n- PR.DS-01\n- PR.DS-02\n- PR.DS-10\nmitre_attack:\n- T1600\n- T1573\n- T1553\n- T1040\n---\n\n# Performing Post-Quantum Cryptography Migration\n\n## When to Use\n\n- When assessing organizational readiness for the NIST post-quantum cryptography transition\n- When building a cryptographic inventory to identify quantum-vulnerable algorithms across infrastructure\n- When evaluating hybrid TLS 1.3 configurations using X25519MLKEM768 key exchange\n- When testing CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) algorithm support\n- When implementing crypto-agility to support both classical and post-quantum algorithms\n- When preparing migration roadmaps aligned with NIST IR 8547 deprecation timelines\n- When configuring oqs-provider with OpenSSL 3.x for post-quantum algorithm support\n\n## Prerequisites\n\n- Python 3.8+ with `cryptography`, `requests`, `pyOpenSSL` libraries\n- OpenSSL 3.0+ (3.5+ recommended for native ML-KEM\u002FML-DSA support)\n- oqs-provider for OpenSSL (for hybrid TLS testing with older OpenSSL)\n- Network access to target servers for TLS assessment\n- Administrative access for infrastructure scanning\n- Familiarity with PKI, TLS, and cryptographic protocols\n\n## Core Concepts\n\n### NIST Post-Quantum Cryptography Standards\n\nNIST published three finalized PQC standards on August 13, 2024:\n\n| Standard | Algorithm | Renamed To | Purpose | Based On |\n|----------|-----------|------------|---------|----------|\n| FIPS 203 | CRYSTALS-Kyber | ML-KEM | Key Encapsulation Mechanism | Module lattice |\n| FIPS 204 | CRYSTALS-Dilithium | ML-DSA | Digital Signatures | Module lattice |\n| FIPS 205 | SPHINCS+ | SLH-DSA | Digital Signatures (backup) | Stateless hash |\n\n**ML-KEM (FIPS 203)** -- Primary standard for key exchange and encryption. Replaces\nRSA and ECDH for key establishment. Three security levels: ML-KEM-512, ML-KEM-768,\nML-KEM-1024.\n\n**ML-DSA (FIPS 204)** -- Primary standard for digital signatures. Replaces RSA and\nECDSA for signing. Three security levels: ML-DSA-44, ML-DSA-65, ML-DSA-87.\n\n**SLH-DSA (FIPS 205)** -- Backup signature standard using hash-based approach. Intended\nas fallback if lattice-based ML-DSA is found vulnerable. Larger signatures but\nconservative security assumptions.\n\n### Quantum-Vulnerable Algorithms\n\nThese classical algorithms are vulnerable to quantum attack via Shor's algorithm:\n\n| Algorithm | Usage | Quantum Threat | Migration Priority |\n|-----------|-------|---------------|-------------------|\n| RSA-2048\u002F4096 | Key exchange, signatures, encryption | Shor's algorithm breaks factoring | Critical |\n| ECDH (P-256, P-384) | TLS key exchange | Shor's algorithm breaks ECDLP | Critical |\n| ECDSA | Code signing, TLS certificates | Shor's algorithm breaks ECDLP | Critical |\n| DSA | Legacy signatures | Shor's algorithm breaks DLP | Critical |\n| DH (Diffie-Hellman) | Key exchange | Shor's algorithm breaks DLP | Critical |\n| AES-128 | Symmetric encryption | Grover's halves key strength | Medium (upgrade to AES-256) |\n| SHA-256 | Hashing | Grover's reduces to 128-bit | Low (still adequate) |\n\n### NIST Migration Timeline (IR 8547)\n\n- **2024**: Standards published, migration planning should begin\n- **2030**: Deprecation of quantum-vulnerable algorithms for most federal systems\n- **2035**: Complete removal of quantum-vulnerable algorithms from NIST standards\n- **Now**: \"Harvest now, decrypt later\" attacks make early migration essential for\n  long-lived secrets and data requiring long-term confidentiality\n\n### Hybrid TLS Key Exchange\n\nDuring the transition period, hybrid key exchange combines a classical algorithm with\na post-quantum algorithm. If either algorithm is secure, the connection remains protected.\n\n```\nHybrid Key Exchange: X25519MLKEM768\n  = X25519 (classical ECDH) + ML-KEM-768 (post-quantum)\n\nClient Hello:\n  supported_groups: X25519MLKEM768, X25519, secp256r1\n  key_share: X25519MLKEM768\n\nServer Hello:\n  selected_group: X25519MLKEM768\n  key_share: X25519MLKEM768\n\nShared Secret = KDF(X25519_shared || MLKEM768_shared)\n```\n\n## Instructions\n\n### Phase 1: Cryptographic Inventory Scanning\n\nThe first step in PQC migration is discovering all cryptographic algorithm usage\nacross the enterprise. This includes TLS configurations, certificates, code libraries,\nkey stores, and protocol configurations.\n\n```python\n# Scan TLS endpoints for quantum-vulnerable algorithms\npython scripts\u002Fagent.py --action scan_tls \\\n    --targets targets.txt \\\n    --output tls_inventory.json\n```\n\nThe scanner identifies:\n- TLS protocol versions in use\n- Key exchange algorithms (RSA, ECDH, DH -- all quantum-vulnerable)\n- Certificate signature algorithms (RSA, ECDSA)\n- Cipher suite configurations\n- Certificate key sizes and expiration dates\n\n### Phase 2: Crypto-Agility Assessment\n\nEvaluate the organization's ability to swap cryptographic algorithms without\nmajor infrastructure changes:\n\n```python\n# Assess crypto-agility readiness\npython scripts\u002Fagent.py --action assess_agility \\\n    --scan-results tls_inventory.json \\\n    --output agility_report.json\n```\n\nKey assessment areas:\n1. **Protocol flexibility**: Can TLS configurations be updated without downtime?\n2. **Library versions**: Do deployed crypto libraries support PQC algorithms?\n3. **Certificate infrastructure**: Can CA issue PQC certificates?\n4. **Key management**: Can KMS handle larger PQC key sizes?\n5. **Hardware constraints**: Can HSMs support PQC operations?\n\n### Phase 3: Hybrid TLS Readiness Testing\n\nTest whether infrastructure supports hybrid key exchange with X25519MLKEM768:\n\n```python\n# Test hybrid TLS support on target servers\npython scripts\u002Fagent.py --action test_hybrid_tls \\\n    --target server.example.com:443 \\\n    --output hybrid_tls_report.json\n```\n\n**OpenSSL 3.5+ (native ML-KEM support):**\n```bash\n# Test with native PQC support\nopenssl s_client -connect server.example.com:443 \\\n    -groups X25519MLKEM768\n```\n\n**OpenSSL 3.0-3.4 with oqs-provider:**\n```bash\n# Configure oqs-provider\n# \u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf\n[openssl_init]\nproviders = provider_sect\n\n[provider_sect]\ndefault = default_sect\noqsprovider = oqsprovider_sect\n\n[default_sect]\nactivate = 1\n\n[oqsprovider_sect]\nactivate = 1\nmodule = \u002Fusr\u002Flib\u002Foqs-provider\u002Foqsprovider.so\n\n# Test hybrid TLS\nOPENSSL_CONF=\u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf \\\nopenssl s_client -connect server.example.com:443 \\\n    -groups x25519_mlkem768\n```\n\n**Web Server Configuration for Hybrid TLS:**\n\nApache httpd:\n```apache\nSSLEngine on\nSSLCertificateFile \u002Fetc\u002Fssl\u002Fcerts\u002Fserver.crt\nSSLCertificateKeyFile \u002Fetc\u002Fssl\u002Fprivate\u002Fserver.key\nSSLOpenSSLConfCmd Curves X25519MLKEM768:X25519:prime256v1\nSSLProtocol -all +TLSv1.2 +TLSv1.3\n```\n\nNGINX:\n```nginx\nssl_ecdh_curve X25519MLKEM768:X25519:prime256v1;\nssl_protocols TLSv1.2 TLSv1.3;\nssl_prefer_server_ciphers on;\n```\n\n### Phase 4: ML-KEM Key Encapsulation Validation\n\nValidate that ML-KEM (CRYSTALS-Kyber) key encapsulation works correctly in your\nenvironment:\n\n```python\n# Test ML-KEM key encapsulation at all security levels\npython scripts\u002Fagent.py --action test_mlkem \\\n    --output mlkem_validation.json\n```\n\nML-KEM parameter comparison:\n\n| Parameter | ML-KEM-512 | ML-KEM-768 | ML-KEM-1024 |\n|-----------|-----------|-----------|------------|\n| Security Level | NIST Level 1 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 800 bytes | 1,184 bytes | 1,568 bytes |\n| Ciphertext Size | 768 bytes | 1,088 bytes | 1,568 bytes |\n| Shared Secret | 32 bytes | 32 bytes | 32 bytes |\n| Comparable To | AES-128 | AES-192 | AES-256 |\n\n### Phase 5: ML-DSA Digital Signature Validation\n\nValidate ML-DSA (CRYSTALS-Dilithium) signature operations:\n\n```python\n# Test ML-DSA digital signatures\npython scripts\u002Fagent.py --action test_mldsa \\\n    --output mldsa_validation.json\n```\n\nML-DSA parameter comparison:\n\n| Parameter | ML-DSA-44 | ML-DSA-65 | ML-DSA-87 |\n|-----------|----------|----------|----------|\n| Security Level | NIST Level 2 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 1,312 bytes | 1,952 bytes | 2,592 bytes |\n| Signature Size | 2,420 bytes | 3,293 bytes | 4,595 bytes |\n| Secret Key Size | 2,560 bytes | 4,032 bytes | 4,896 bytes |\n\n### Phase 6: Migration Roadmap Generation\n\nGenerate a prioritized migration roadmap based on inventory and assessment results:\n\n```python\n# Generate complete migration roadmap\npython scripts\u002Fagent.py --action roadmap \\\n    --scan-results tls_inventory.json \\\n    --agility-results agility_report.json \\\n    --output migration_roadmap.json\n```\n\nThe roadmap prioritizes systems by:\n1. **Data sensitivity**: Systems handling long-lived secrets migrate first\n2. **Exposure level**: Internet-facing services before internal\n3. **Crypto-agility**: Systems that can easily swap algorithms first\n4. **Compliance requirements**: Federal\u002Fregulated systems per NIST IR 8547 timeline\n5. **Dependency chains**: Libraries and frameworks before applications\n\n## Examples\n\n### Full Assessment Pipeline\n\n```bash\n# Step 1: Scan all TLS endpoints\npython scripts\u002Fagent.py --action scan_tls --targets hosts.txt --output scan.json\n\n# Step 2: Assess crypto-agility\npython scripts\u002Fagent.py --action assess_agility --scan-results scan.json --output agility.json\n\n# Step 3: Test hybrid TLS on critical servers\npython scripts\u002Fagent.py --action test_hybrid_tls --target critical.example.com:443\n\n# Step 4: Validate ML-KEM support\npython scripts\u002Fagent.py --action test_mlkem --output mlkem.json\n\n# Step 5: Validate ML-DSA support\npython scripts\u002Fagent.py --action test_mldsa --output mldsa.json\n\n# Step 6: Generate migration roadmap\npython scripts\u002Fagent.py --action roadmap --scan-results scan.json --agility-results agility.json --output roadmap.json\n```\n\n### Quick Server Assessment\n\n```bash\n# Single server PQC readiness check\npython scripts\u002Fagent.py --action scan_tls --target server.example.com:443\n```\n\n## Validation Checklist\n\n- [ ] Cryptographic inventory covers all TLS endpoints, certificates, and key stores\n- [ ] All quantum-vulnerable algorithms (RSA, ECDH, ECDSA, DH, DSA) are identified\n- [ ] Crypto-agility assessment documents library versions and upgrade paths\n- [ ] Hybrid TLS (X25519MLKEM768) tested on representative server configurations\n- [ ] ML-KEM key encapsulation validated at target security level (768 recommended)\n- [ ] ML-DSA signature verification validated for certificate chain use\n- [ ] SLH-DSA (FIPS 205) evaluated as backup signature algorithm\n- [ ] Migration roadmap prioritizes by data sensitivity and compliance timeline\n- [ ] OpenSSL version and oqs-provider compatibility confirmed\n- [ ] Key size increases accounted for in network and storage capacity planning\n- [ ] HSM\u002FKMS compatibility with PQC algorithms verified\n- [ ] Performance impact of PQC algorithms benchmarked under production load\n- [ ] \"Harvest now, decrypt later\" risk assessed for sensitive data channels\n- [ ] Certificate Authority PQC readiness confirmed for certificate issuance\n\n## References\n\n- NIST PQC Standards: https:\u002F\u002Fcsrc.nist.gov\u002Fprojects\u002Fpost-quantum-cryptography\n- FIPS 203 (ML-KEM): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F203\u002Ffinal\n- FIPS 204 (ML-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F204\u002Ffinal\n- FIPS 205 (SLH-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F205\u002Ffinal\n- NIST SP 1800-38 Migration Guide: https:\u002F\u002Fwww.nccoe.nist.gov\u002Fcrypto-agility-considerations-migrating-post-quantum-cryptographic-algorithms\n- NIST IR 8547 Transition Timeline: https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fir\u002F8547\u002Fipd\n- Open Quantum Safe Project: https:\u002F\u002Fopenquantumsafe.org\u002F\n- oqs-provider for OpenSSL: https:\u002F\u002Fgithub.com\u002Fopen-quantum-safe\u002Foqs-provider\n- OQS TLS Integration: https:\u002F\u002Fopenquantumsafe.org\u002Fapplications\u002Ftls.html\n- CISA PQC Migration Strategy: https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002F2024-09\u002FStrategy-for-Migrating-to-Automated-PQC-Discovery-and-Inventory-Tools.pdf\n- IETF Hybrid Key Exchange Draft: https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fdraft-ietf-tls-hybrid-design\u002F\n- CycloneDX Crypto BOM: https:\u002F\u002Fcyclonedx.org\u002Fuse-cases\u002Fcryptographic-key\u002F\n","# Performing Post-Quantum Cryptography Migration\n\n## When to Use\n\n- When assessing organizational readiness for the NIST post-quantum cryptography transition\n- When building a cryptographic inventory to identify quantum-vulnerable algorithms across infrastructure\n- When evaluating hybrid TLS 1.3 configurations using X25519MLKEM768 key exchange\n- When testing CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) algorithm support\n- When implementing crypto-agility to support both classical and post-quantum algorithms\n- When preparing migration roadmaps aligned with NIST IR 8547 deprecation timelines\n- When configuring oqs-provider with OpenSSL 3.x for post-quantum algorithm support\n\n## Prerequisites\n\n- Python 3.8+ with `cryptography`, `requests`, `pyOpenSSL` libraries\n- OpenSSL 3.0+ (3.5+ recommended for native ML-KEM\u002FML-DSA support)\n- oqs-provider for OpenSSL (for hybrid TLS testing with older OpenSSL)\n- Network access to target servers for TLS assessment\n- Administrative access for infrastructure scanning\n- Familiarity with PKI, TLS, and cryptographic protocols\n\n## Core Concepts\n\n### NIST Post-Quantum Cryptography Standards\n\nNIST published three finalized PQC standards on August 13, 2024:\n\n| Standard | Algorithm | Renamed To | Purpose | Based On |\n|----------|-----------|------------|---------|----------|\n| FIPS 203 | CRYSTALS-Kyber | ML-KEM | Key Encapsulation Mechanism | Module lattice |\n| FIPS 204 | CRYSTALS-Dilithium | ML-DSA | Digital Signatures | Module lattice |\n| FIPS 205 | SPHINCS+ | SLH-DSA | Digital Signatures (backup) | Stateless hash |\n\n**ML-KEM (FIPS 203)** -- Primary standard for key exchange and encryption. Replaces\nRSA and ECDH for key establishment. Three security levels: ML-KEM-512, ML-KEM-768,\nML-KEM-1024.\n\n**ML-DSA (FIPS 204)** -- Primary standard for digital signatures. Replaces RSA and\nECDSA for signing. Three security levels: ML-DSA-44, ML-DSA-65, ML-DSA-87.\n\n**SLH-DSA (FIPS 205)** -- Backup signature standard using hash-based approach. Intended\nas fallback if lattice-based ML-DSA is found vulnerable. Larger signatures but\nconservative security assumptions.\n\n### Quantum-Vulnerable Algorithms\n\nThese classical algorithms are vulnerable to quantum attack via Shor's algorithm:\n\n| Algorithm | Usage | Quantum Threat | Migration Priority |\n|-----------|-------|---------------|-------------------|\n| RSA-2048\u002F4096 | Key exchange, signatures, encryption | Shor's algorithm breaks factoring | Critical |\n| ECDH (P-256, P-384) | TLS key exchange | Shor's algorithm breaks ECDLP | Critical |\n| ECDSA | Code signing, TLS certificates | Shor's algorithm breaks ECDLP | Critical |\n| DSA | Legacy signatures | Shor's algorithm breaks DLP | Critical |\n| DH (Diffie-Hellman) | Key exchange | Shor's algorithm breaks DLP | Critical |\n| AES-128 | Symmetric encryption | Grover's halves key strength | Medium (upgrade to AES-256) |\n| SHA-256 | Hashing | Grover's reduces to 128-bit | Low (still adequate) |\n\n### NIST Migration Timeline (IR 8547)\n\n- **2024**: Standards published, migration planning should begin\n- **2030**: Deprecation of quantum-vulnerable algorithms for most federal systems\n- **2035**: Complete removal of quantum-vulnerable algorithms from NIST standards\n- **Now**: \"Harvest now, decrypt later\" attacks make early migration essential for\n  long-lived secrets and data requiring long-term confidentiality\n\n### Hybrid TLS Key Exchange\n\nDuring the transition period, hybrid key exchange combines a classical algorithm with\na post-quantum algorithm. If either algorithm is secure, the connection remains protected.\n\n```\nHybrid Key Exchange: X25519MLKEM768\n  = X25519 (classical ECDH) + ML-KEM-768 (post-quantum)\n\nClient Hello:\n  supported_groups: X25519MLKEM768, X25519, secp256r1\n  key_share: X25519MLKEM768\n\nServer Hello:\n  selected_group: X25519MLKEM768\n  key_share: X25519MLKEM768\n\nShared Secret = KDF(X25519_shared || MLKEM768_shared)\n```\n\n## Instructions\n\n### Phase 1: Cryptographic Inventory Scanning\n\nThe first step in PQC migration is discovering all cryptographic algorithm usage\nacross the enterprise. This includes TLS configurations, certificates, code libraries,\nkey stores, and protocol configurations.\n\n```python\n# Scan TLS endpoints for quantum-vulnerable algorithms\npython scripts\u002Fagent.py --action scan_tls \\\n    --targets targets.txt \\\n    --output tls_inventory.json\n```\n\nThe scanner identifies:\n- TLS protocol versions in use\n- Key exchange algorithms (RSA, ECDH, DH -- all quantum-vulnerable)\n- Certificate signature algorithms (RSA, ECDSA)\n- Cipher suite configurations\n- Certificate key sizes and expiration dates\n\n### Phase 2: Crypto-Agility Assessment\n\nEvaluate the organization's ability to swap cryptographic algorithms without\nmajor infrastructure changes:\n\n```python\n# Assess crypto-agility readiness\npython scripts\u002Fagent.py --action assess_agility \\\n    --scan-results tls_inventory.json \\\n    --output agility_report.json\n```\n\nKey assessment areas:\n1. **Protocol flexibility**: Can TLS configurations be updated without downtime?\n2. **Library versions**: Do deployed crypto libraries support PQC algorithms?\n3. **Certificate infrastructure**: Can CA issue PQC certificates?\n4. **Key management**: Can KMS handle larger PQC key sizes?\n5. **Hardware constraints**: Can HSMs support PQC operations?\n\n### Phase 3: Hybrid TLS Readiness Testing\n\nTest whether infrastructure supports hybrid key exchange with X25519MLKEM768:\n\n```python\n# Test hybrid TLS support on target servers\npython scripts\u002Fagent.py --action test_hybrid_tls \\\n    --target server.example.com:443 \\\n    --output hybrid_tls_report.json\n```\n\n**OpenSSL 3.5+ (native ML-KEM support):**\n```bash\n# Test with native PQC support\nopenssl s_client -connect server.example.com:443 \\\n    -groups X25519MLKEM768\n```\n\n**OpenSSL 3.0-3.4 with oqs-provider:**\n```bash\n# Configure oqs-provider\n# \u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf\n[openssl_init]\nproviders = provider_sect\n\n[provider_sect]\ndefault = default_sect\noqsprovider = oqsprovider_sect\n\n[default_sect]\nactivate = 1\n\n[oqsprovider_sect]\nactivate = 1\nmodule = \u002Fusr\u002Flib\u002Foqs-provider\u002Foqsprovider.so\n\n# Test hybrid TLS\nOPENSSL_CONF=\u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf \\\nopenssl s_client -connect server.example.com:443 \\\n    -groups x25519_mlkem768\n```\n\n**Web Server Configuration for Hybrid TLS:**\n\nApache httpd:\n```apache\nSSLEngine on\nSSLCertificateFile \u002Fetc\u002Fssl\u002Fcerts\u002Fserver.crt\nSSLCertificateKeyFile \u002Fetc\u002Fssl\u002Fprivate\u002Fserver.key\nSSLOpenSSLConfCmd Curves X25519MLKEM768:X25519:prime256v1\nSSLProtocol -all +TLSv1.2 +TLSv1.3\n```\n\nNGINX:\n```nginx\nssl_ecdh_curve X25519MLKEM768:X25519:prime256v1;\nssl_protocols TLSv1.2 TLSv1.3;\nssl_prefer_server_ciphers on;\n```\n\n### Phase 4: ML-KEM Key Encapsulation Validation\n\nValidate that ML-KEM (CRYSTALS-Kyber) key encapsulation works correctly in your\nenvironment:\n\n```python\n# Test ML-KEM key encapsulation at all security levels\npython scripts\u002Fagent.py --action test_mlkem \\\n    --output mlkem_validation.json\n```\n\nML-KEM parameter comparison:\n\n| Parameter | ML-KEM-512 | ML-KEM-768 | ML-KEM-1024 |\n|-----------|-----------|-----------|------------|\n| Security Level | NIST Level 1 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 800 bytes | 1,184 bytes | 1,568 bytes |\n| Ciphertext Size | 768 bytes | 1,088 bytes | 1,568 bytes |\n| Shared Secret | 32 bytes | 32 bytes | 32 bytes |\n| Comparable To | AES-128 | AES-192 | AES-256 |\n\n### Phase 5: ML-DSA Digital Signature Validation\n\nValidate ML-DSA (CRYSTALS-Dilithium) signature operations:\n\n```python\n# Test ML-DSA digital signatures\npython scripts\u002Fagent.py --action test_mldsa \\\n    --output mldsa_validation.json\n```\n\nML-DSA parameter comparison:\n\n| Parameter | ML-DSA-44 | ML-DSA-65 | ML-DSA-87 |\n|-----------|----------|----------|----------|\n| Security Level | NIST Level 2 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 1,312 bytes | 1,952 bytes | 2,592 bytes |\n| Signature Size | 2,420 bytes | 3,293 bytes | 4,595 bytes |\n| Secret Key Size | 2,560 bytes | 4,032 bytes | 4,896 bytes |\n\n### Phase 6: Migration Roadmap Generation\n\nGenerate a prioritized migration roadmap based on inventory and assessment results:\n\n```python\n# Generate complete migration roadmap\npython scripts\u002Fagent.py --action roadmap \\\n    --scan-results tls_inventory.json \\\n    --agility-results agility_report.json \\\n    --output migration_roadmap.json\n```\n\nThe roadmap prioritizes systems by:\n1. **Data sensitivity**: Systems handling long-lived secrets migrate first\n2. **Exposure level**: Internet-facing services before internal\n3. **Crypto-agility**: Systems that can easily swap algorithms first\n4. **Compliance requirements**: Federal\u002Fregulated systems per NIST IR 8547 timeline\n5. **Dependency chains**: Libraries and frameworks before applications\n\n## Examples\n\n### Full Assessment Pipeline\n\n```bash\n# Step 1: Scan all TLS endpoints\npython scripts\u002Fagent.py --action scan_tls --targets hosts.txt --output scan.json\n\n# Step 2: Assess crypto-agility\npython scripts\u002Fagent.py --action assess_agility --scan-results scan.json --output agility.json\n\n# Step 3: Test hybrid TLS on critical servers\npython scripts\u002Fagent.py --action test_hybrid_tls --target critical.example.com:443\n\n# Step 4: Validate ML-KEM support\npython scripts\u002Fagent.py --action test_mlkem --output mlkem.json\n\n# Step 5: Validate ML-DSA support\npython scripts\u002Fagent.py --action test_mldsa --output mldsa.json\n\n# Step 6: Generate migration roadmap\npython scripts\u002Fagent.py --action roadmap --scan-results scan.json --agility-results agility.json --output roadmap.json\n```\n\n### Quick Server Assessment\n\n```bash\n# Single server PQC readiness check\npython scripts\u002Fagent.py --action scan_tls --target server.example.com:443\n```\n\n## Validation Checklist\n\n- [ ] Cryptographic inventory covers all TLS endpoints, certificates, and key stores\n- [ ] All quantum-vulnerable algorithms (RSA, ECDH, ECDSA, DH, DSA) are identified\n- [ ] Crypto-agility assessment documents library versions and upgrade paths\n- [ ] Hybrid TLS (X25519MLKEM768) tested on representative server configurations\n- [ ] ML-KEM key encapsulation validated at target security level (768 recommended)\n- [ ] ML-DSA signature verification validated for certificate chain use\n- [ ] SLH-DSA (FIPS 205) evaluated as backup signature algorithm\n- [ ] Migration roadmap prioritizes by data sensitivity and compliance timeline\n- [ ] OpenSSL version and oqs-provider compatibility confirmed\n- [ ] Key size increases accounted for in network and storage capacity planning\n- [ ] HSM\u002FKMS compatibility with PQC algorithms verified\n- [ ] Performance impact of PQC algorithms benchmarked under production load\n- [ ] \"Harvest now, decrypt later\" risk assessed for sensitive data channels\n- [ ] Certificate Authority PQC readiness confirmed for certificate issuance\n\n## References\n\n- NIST PQC Standards: https:\u002F\u002Fcsrc.nist.gov\u002Fprojects\u002Fpost-quantum-cryptography\n- FIPS 203 (ML-KEM): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F203\u002Ffinal\n- FIPS 204 (ML-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F204\u002Ffinal\n- FIPS 205 (SLH-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F205\u002Ffinal\n- NIST SP 1800-38 Migration Guide: https:\u002F\u002Fwww.nccoe.nist.gov\u002Fcrypto-agility-considerations-migrating-post-quantum-cryptographic-algorithms\n- NIST IR 8547 Transition Timeline: https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fir\u002F8547\u002Fipd\n- Open Quantum Safe Project: https:\u002F\u002Fopenquantumsafe.org\u002F\n- oqs-provider for OpenSSL: https:\u002F\u002Fgithub.com\u002Fopen-quantum-safe\u002Foqs-provider\n- OQS TLS Integration: https:\u002F\u002Fopenquantumsafe.org\u002Fapplications\u002Ftls.html\n- CISA PQC Migration Strategy: https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002F2024-09\u002FStrategy-for-Migrating-to-Automated-PQC-Discovery-and-Inventory-Tools.pdf\n- IETF Hybrid Key Exchange Draft: https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fdraft-ietf-tls-hybrid-design\u002F\n- CycloneDX Crypto BOM: https:\u002F\u002Fcyclonedx.org\u002Fuse-cases\u002Fcryptographic-key\u002F\n",{"name":5,"tags":24,"author":34,"domain":35,"license":14,"version":36,"nist_csf":37,"subdomain":41,"description":42,"mitre_attack":43},[25,26,27,28,29,30,31,32,33],"post-quantum","PQC","CRYSTALS-Kyber","ML-KEM","ML-DSA","FIPS-203","FIPS-204","hybrid-TLS","crypto-agility","mukul975","cybersecurity","1.0",[38,39,40],"PR.DS-01","PR.DS-02","PR.DS-10","cryptography","Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203\u002F204\u002F205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use when planning or executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure.\n",[44,45,46,47],"T1600","T1573","T1553","T1040","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-post-quantum-cryptography-migration","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill performing-post-quantum-cryptography-migration",{"tool":60,"command":61},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill performing-post-quantum-cryptography-migration",{"tool":63,"command":64},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill performing-post-quantum-cryptography-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-post-quantum-cryptography-migration\u002FSKILL.md",true,[68,72,78],{"path":69,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fapi-reference.md","REFERENCE","参考文档",8824,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-post-quantum-cryptography-migration\u002Freferences\u002Fapi-reference.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fagent.py","SCRIPT","脚本",56599,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-post-quantum-cryptography-migration\u002Fscripts\u002Fagent.py",[85,93,100,107,114,121],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]