[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CWDJ355J3FVGFNFB2CF3B":3,"skill-same:01M71CWDJ355J3FVGFNFB2CF3B":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M71CWDJ355J3FVGFNFB2CF3B","crypto-postquantum-post",null,"Crypto Postquantum Post.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcrypto-postquantum-post\u002FSKILL.md",[],[19,20,21,22],"crypto","post","crypto postquantum post","cybersecurity","2026-11-10 10:12:30",false,"---\nname: crypto-postquantum-post\ndescription: \"Crypto Postquantum Post.\"\ndomain: cybersecurity\n---\n\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","-|\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,"domain":22,"description":7},"main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcrypto-postquantum-post","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill crypto-postquantum-post",{"tool":41,"command":42},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill crypto-postquantum-post",{"tool":44,"command":45},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill crypto-postquantum-post","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcrypto-postquantum-post\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"index.json","REFERENCE","参考文档",492,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcrypto-postquantum-post\u002Findex.json",[56,81,104,126,148,164],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":23},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,22,80],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":23},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[88,63,89,66,90,91,92,22,93,94,95,96,97,98,68,99,100,101,102,103],"exploit","services wmi exec exploit","exec","remote","traffic","Bash","analysis","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":23},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[111,112,113,114,115,116,22,93,117,94,118,119,68,101,120,121,122,123,124,125],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper","sonnet",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":23},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[64,133,134,135,136,137,138,69,139,22,80,140,141,142,143,144,145,146,147,68],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":23},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[155,156,64,157,135,137,158,69,159,139,22,80,94,160,161,162,163,147,68,70],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":23},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[171,64,135,172,158,69,173,174,22,80,175,176,177,178,179,180,68,70,181,182],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]