[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARHAK7GV3KPQWRK91AS55B":3,"skill-same:01M7ARHAK7GV3KPQWRK91AS55B":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ARHAK7GV3KPQWRK91AS55B","qcrypto-official-position-qrng-quantum-threat-and-choosing",null,"Use when making an actual decision: the official position of the national security agencies on QKD and why they recommend against it for most purposes, quantum random number generation and where it genuinely helps, the quantum computing threat to existing cryptography and realistic timelines, and a direct guide to choosing between QKD, QRNG and post-quantum cryptography for a given problem.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fquantum-cryptography-and-quantum-internet\u002Fskills\u002Fqcrypto-official-position-qrng-quantum-threat-and-choosing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: qcrypto-official-position-qrng-quantum-threat-and-choosing\ndescription: \"Use when making an actual decision: the official position of the national security agencies on QKD and why they recommend against it for most purposes, quantum random number generation and where it genuinely helps, the quantum computing threat to existing cryptography and realistic timelines, and a direct guide to choosing between QKD, QRNG and post-quantum cryptography for a given problem.\"\n---\n\n# Quantum Cryptography: The Official Position, Quantum Random Number Generation, the Quantum Computing Threat, and Choosing\n\n> **Part 5 of 6** of the *Quantum Cryptography, Quantum Encryption and the Quantum Internet* reference (plugin `quantum-cryptography-and-quantum-internet`), covering §20–§23. Sibling skills: `qcrypto-two-different-things-qubits-no-cloning-and-entanglement` (§0–§5), `qcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation` (§6–§9), `qcrypto-security-claims-attacks-and-trusted-nodes` (§10–§13), `qcrypto-repeaters-memory-entanglement-distribution-and-satellite` (§14–§19), `qcrypto-reference` (§24–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The protocols date to the 1980s and 90s. Two areas moved recently. See §24 → `qcrypto-reference` for quantum repeater demonstrations, and the government position on QKD.\n\n> **⚠️ FIRST, THE TERMINOLOGY DISASTER — because almost every popular article gets this\n> wrong and the two things are nearly opposites** (§1 → `qcrypto-two-different-things-qubits-no-cloning-and-entanglement`).\n> ⚠️ **POST-QUANTUM CRYPTOGRAPHY is classical mathematics running on ordinary computers,\n> designed to resist quantum attack. It is what is actually being deployed** (see a\n> cryptography reference).\n> ⚠️ **QUANTUM CRYPTOGRAPHY \u002F QKD uses quantum physics and special hardware to distribute\n> keys. It is a niche technology that several major security agencies actively recommend\n> AGAINST** (§20).\n> **⚠️ \"Quantum-safe\" and \"quantum-secure\" are marketing terms that get applied to both.\n> When someone uses them, ask which they mean.**\n>\n> **Companion to a cryptography reference, which covers the classical primitives, the\n> protocols in production, and the PQC migration.**\n>\n> **⚠️ GOTCHA** boxes mark where physics claims and engineering reality diverge.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ QKD's security is real physics and its threat model is narrower than advertised**\n>    (§10 → `qcrypto-security-claims-attacks-and-trusted-nodes`). **It secures a key exchange against an eavesdropper on the channel. It does not\n>    authenticate, does not protect endpoints, and cannot bootstrap trust from nothing.**\n> 2. **⚠️ THE THEORY-IMPLEMENTATION GAP is the whole story** (§11 → `qcrypto-security-claims-attacks-and-trusted-nodes`). **Every deployed QKD\n>    system that has been attacked was attacked through its hardware, not its protocol —\n>    the security proofs assume devices the engineers cannot actually build.**\n> 3. **⚠️ QUANTUM REPEATERS ARE THE BOTTLENECK** (§14 → `qcrypto-repeaters-memory-entanglement-distribution-and-satellite`, §24.1 → `qcrypto-reference`). **Without them, quantum\n>    networks are point-to-point links chained through trusted nodes, which reintroduces\n>    exactly the trust QKD was supposed to eliminate.**\n\n---\n\n## §20. ⚠️ The Official Position\n\n> **⚠️ The most important section for anyone evaluating a QKD procurement, and it is\n> strikingly consistent across the anglophone agencies while Europe diverges** (§24.2 → `qcrypto-reference`).\n**⚠️ The NSA's published position** identifies five limitations and concludes it does not\nrecommend QKD for national security systems.\n```\n⚠️ THE FIVE NSA LIMITATIONS, in substance\n   ⚠️ 1. ⚠️ PARTIAL SOLUTION — QKD supplies keying material for\n      confidentiality but ⚠️ CANNOT AUTHENTICATE ITS OWN\n      TRANSMISSION SOURCE, so authentication requires asymmetric\n      cryptography or pre-placed keys anyway (§10)\n   ⚠️ 2. SPECIAL-PURPOSE EQUIPMENT — dedicated fibre or managed\n      free-space transmitters; cannot be a software upgrade\n   ⚠️ 3. Significant infrastructure and maintenance cost\n   ⚠️ 4. ⚠️ IMPLEMENTATION SECURITY — the theory-device gap (§11)\n   ⚠️ 5. ⚠️ DENIAL OF SERVICE — the quantum channel is trivially\n      disruptable, and detecting an \"eavesdropper\" means REFUSING\n      TO PRODUCE KEY, so an attacker who cannot read can still\n      stop you communicating\n```\n**⚠️ The UK NCSC is equally direct**: ⚠️ **it \"will not support the use of QKD for\ngovernment or military applications,\" endorses PQC as the best mitigation, and makes the\nstructural point plainly — QKD does not provide authentication, nor do any other quantum\ntechniques, so it must be combined with other cryptographic services and \"should not be\nrelied on as a mechanism that provides substantial security value.\"** ⚠️ **For other\nsectors it recommends QKD should not be solely relied upon.**\n**⚠️ France's ANSSI** concludes QKD is usable \"only in some niche use cases,\" is \"not yet\nsufficiently mature from a security perspective,\" and that the clear priorities should be\nmigration to PQC and\u002For adoption of symmetric keying. ⚠️ **Germany's BSI has published in\nsimilar terms, with cost cited as a primary barrier.**\n**⚠️ In the US this has hardened into policy**: ⚠️ **CNSA 2.0 explicitly rejects QKD for\nnational security systems, NSA advises agencies not to invest in or deploy QKD without\ndirect consultation, and reporting indicates a DoD PQC migration memorandum explicitly\nBANNED QKD in DoD systems.**\n> **⚠️ GOTCHA — read this as a genuine technical disagreement, not a settled fact, because\n> the QKD community has responded substantively.** ⚠️ **A published rebuttal by Swiss\n> researchers argues some NSA objections don't hold and others are expected to be resolved\n> as cheaper optics and quantum repeaters arrive — explicitly framing the assessment as\n> depending on which technological epoch you assume.**\n> ⚠️ **And the NCSC's non-endorsement is reportedly not framed as permanent, with quantum\n> repeaters cited as the development that would most change the assessment** (§14 → `qcrypto-repeaters-memory-entanglement-distribution-and-satellite`, §24.1 → `qcrypto-reference`).\n> **⚠️ Verify current wording against the source documents rather than any paraphrase —\n> including mine.**\n\n---\n\n## §21. Quantum Random Number Generation\n\n**⚠️ The quantum security technology that is uncontroversially useful, and it deserves\nseparating from QKD.**\n⚠️ **Measurement outcomes on a quantum superposition are fundamentally, not merely\npractically, unpredictable — which makes a genuine entropy source.**\n**⚠️ Implementations**: **photon path splitting, vacuum fluctuation measurement, phase\nnoise in lasers.**\n**⚠️ The sober framing**: ⚠️ **NSA's position is that any RNG certified by appropriate\nstandards is acceptable if correctly implemented — so QRNG is fine, and is not\ncategorically required.** **⚠️ In practice a well-implemented OS CSPRNG seeded properly\n(see a cryptography reference) is sufficient for almost all purposes, and QRNG's real value\nis as a high-quality entropy source for seeding, and where certification demands it.**\n⚠️ **Note that a QRNG still needs post-processing and health testing — a raw quantum source\nwith a device bias is just a biased source.**\n\n---\n\n## §22. The Quantum Computing Threat\n\n**⚠️ Brief, because a cryptography reference covers the migration.**\n⚠️ **SHOR'S ALGORITHM breaks RSA, Diffie-Hellman and elliptic curve cryptography — the\npublic-key foundations.** ⚠️ **GROVER'S ALGORITHM gives a quadratic speedup on brute-force\nsearch, which effectively halves symmetric key strength and is why AES-256 remains\nadequate.**\n**⚠️ Requires a CRYPTOGRAPHICALLY RELEVANT quantum computer** — ⚠️ **millions of\nhigh-quality error-corrected logical qubits, which is far beyond current hardware.**\n**⚠️ Timeline estimates vary enormously and should be treated with suspicion in both\ndirections** — ⚠️ **vendors and national programmes both have incentives.**\n**⚠️ HARVEST NOW, DECRYPT LATER is why the timeline is less important than people think**:\n⚠️ **recorded traffic is a stored liability, so the relevant question is secrecy lifetime\nplus migration time.**\n\n---\n\n## §23. ⚠️ Choosing\n\n```\n⚠️ FOR ESSENTIALLY EVERY ORGANIZATION: ⚠️ PQC\n   ⚠️ Software upgrade · works end to end at any distance ·\n   provides authentication · standardized · endorsed by every\n   major agency · no new physical infrastructure\n⚠️ QKD MIGHT MAKE SENSE WHEN, ALL AT ONCE\n   ⚠️ You control dedicated fibre between two fixed points\n   ⚠️ The distance is short, or you accept trusted nodes (§13)\n   ⚠️ You already have pre-shared symmetric keys for\n      authentication (§10)\n   ⚠️ The cost is acceptable for a small number of links\n   ⚠️ You want defence in depth rather than a replacement\n   ⚠️ Or you have a sovereignty\u002Fstrategic reason distinct from\n      the technical case\n⚠️ THE DEFENSIBLE HYBRID POSITION  ⚠️ QKD-derived key XORed or\n   combined with a PQC-derived key, so security holds if EITHER\n   holds. ⚠️ This is the architecture serious QKD deployments use,\n   and it is an honest answer to §20's objections\n⚠️ ALSO GENUINELY AVAILABLE  ⚠️ pre-shared symmetric keys with\n   AES-256. ⚠️ Unglamorous, quantum-resistant, and adequate for\n   the fixed-point-to-point case QKD targets\n```\n**⚠️ The question to ask any QKD vendor**: ⚠️ **\"how do you authenticate the classical\nchannel, and how many trusted nodes are in this path?\"** ⚠️ **The answers locate the actual\ntrust boundary.**\n","# Quantum Cryptography: The Official Position, Quantum Random Number Generation, the Quantum Computing Threat, and Choosing\n\n> **Part 5 of 6** of the *Quantum Cryptography, Quantum Encryption and the Quantum Internet* reference (plugin `quantum-cryptography-and-quantum-internet`), covering §20–§23. Sibling skills: `qcrypto-two-different-things-qubits-no-cloning-and-entanglement` (§0–§5), `qcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation` (§6–§9), `qcrypto-security-claims-attacks-and-trusted-nodes` (§10–§13), `qcrypto-repeaters-memory-entanglement-distribution-and-satellite` (§14–§19), `qcrypto-reference` (§24–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The protocols date to the 1980s and 90s. Two areas moved recently. See §24 → `qcrypto-reference` for quantum repeater demonstrations, and the government position on QKD.\n\n> **⚠️ FIRST, THE TERMINOLOGY DISASTER — because almost every popular article gets this\n> wrong and the two things are nearly opposites** (§1 → `qcrypto-two-different-things-qubits-no-cloning-and-entanglement`).\n> ⚠️ **POST-QUANTUM CRYPTOGRAPHY is classical mathematics running on ordinary computers,\n> designed to resist quantum attack. It is what is actually being deployed** (see a\n> cryptography reference).\n> ⚠️ **QUANTUM CRYPTOGRAPHY \u002F QKD uses quantum physics and special hardware to distribute\n> keys. It is a niche technology that several major security agencies actively recommend\n> AGAINST** (§20).\n> **⚠️ \"Quantum-safe\" and \"quantum-secure\" are marketing terms that get applied to both.\n> When someone uses them, ask which they mean.**\n>\n> **Companion to a cryptography reference, which covers the classical primitives, the\n> protocols in production, and the PQC migration.**\n>\n> **⚠️ GOTCHA** boxes mark where physics claims and engineering reality diverge.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ QKD's security is real physics and its threat model is narrower than advertised**\n>    (§10 → `qcrypto-security-claims-attacks-and-trusted-nodes`). **It secures a key exchange against an eavesdropper on the channel. It does not\n>    authenticate, does not protect endpoints, and cannot bootstrap trust from nothing.**\n> 2. **⚠️ THE THEORY-IMPLEMENTATION GAP is the whole story** (§11 → `qcrypto-security-claims-attacks-and-trusted-nodes`). **Every deployed QKD\n>    system that has been attacked was attacked through its hardware, not its protocol —\n>    the security proofs assume devices the engineers cannot actually build.**\n> 3. **⚠️ QUANTUM REPEATERS ARE THE BOTTLENECK** (§14 → `qcrypto-repeaters-memory-entanglement-distribution-and-satellite`, §24.1 → `qcrypto-reference`). **Without them, quantum\n>    networks are point-to-point links chained through trusted nodes, which reintroduces\n>    exactly the trust QKD was supposed to eliminate.**\n\n---\n\n## §20. ⚠️ The Official Position\n\n> **⚠️ The most important section for anyone evaluating a QKD procurement, and it is\n> strikingly consistent across the anglophone agencies while Europe diverges** (§24.2 → `qcrypto-reference`).\n**⚠️ The NSA's published position** identifies five limitations and concludes it does not\nrecommend QKD for national security systems.\n```\n⚠️ THE FIVE NSA LIMITATIONS, in substance\n   ⚠️ 1. ⚠️ PARTIAL SOLUTION — QKD supplies keying material for\n      confidentiality but ⚠️ CANNOT AUTHENTICATE ITS OWN\n      TRANSMISSION SOURCE, so authentication requires asymmetric\n      cryptography or pre-placed keys anyway (§10)\n   ⚠️ 2. SPECIAL-PURPOSE EQUIPMENT — dedicated fibre or managed\n      free-space transmitters; cannot be a software upgrade\n   ⚠️ 3. Significant infrastructure and maintenance cost\n   ⚠️ 4. ⚠️ IMPLEMENTATION SECURITY — the theory-device gap (§11)\n   ⚠️ 5. ⚠️ DENIAL OF SERVICE — the quantum channel is trivially\n      disruptable, and detecting an \"eavesdropper\" means REFUSING\n      TO PRODUCE KEY, so an attacker who cannot read can still\n      stop you communicating\n```\n**⚠️ The UK NCSC is equally direct**: ⚠️ **it \"will not support the use of QKD for\ngovernment or military applications,\" endorses PQC as the best mitigation, and makes the\nstructural point plainly — QKD does not provide authentication, nor do any other quantum\ntechniques, so it must be combined with other cryptographic services and \"should not be\nrelied on as a mechanism that provides substantial security value.\"** ⚠️ **For other\nsectors it recommends QKD should not be solely relied upon.**\n**⚠️ France's ANSSI** concludes QKD is usable \"only in some niche use cases,\" is \"not yet\nsufficiently mature from a security perspective,\" and that the clear priorities should be\nmigration to PQC and\u002For adoption of symmetric keying. ⚠️ **Germany's BSI has published in\nsimilar terms, with cost cited as a primary barrier.**\n**⚠️ In the US this has hardened into policy**: ⚠️ **CNSA 2.0 explicitly rejects QKD for\nnational security systems, NSA advises agencies not to invest in or deploy QKD without\ndirect consultation, and reporting indicates a DoD PQC migration memorandum explicitly\nBANNED QKD in DoD systems.**\n> **⚠️ GOTCHA — read this as a genuine technical disagreement, not a settled fact, because\n> the QKD community has responded substantively.** ⚠️ **A published rebuttal by Swiss\n> researchers argues some NSA objections don't hold and others are expected to be resolved\n> as cheaper optics and quantum repeaters arrive — explicitly framing the assessment as\n> depending on which technological epoch you assume.**\n> ⚠️ **And the NCSC's non-endorsement is reportedly not framed as permanent, with quantum\n> repeaters cited as the development that would most change the assessment** (§14 → `qcrypto-repeaters-memory-entanglement-distribution-and-satellite`, §24.1 → `qcrypto-reference`).\n> **⚠️ Verify current wording against the source documents rather than any paraphrase —\n> including mine.**\n\n---\n\n## §21. Quantum Random Number Generation\n\n**⚠️ The quantum security technology that is uncontroversially useful, and it deserves\nseparating from QKD.**\n⚠️ **Measurement outcomes on a quantum superposition are fundamentally, not merely\npractically, unpredictable — which makes a genuine entropy source.**\n**⚠️ Implementations**: **photon path splitting, vacuum fluctuation measurement, phase\nnoise in lasers.**\n**⚠️ The sober framing**: ⚠️ **NSA's position is that any RNG certified by appropriate\nstandards is acceptable if correctly implemented — so QRNG is fine, and is not\ncategorically required.** **⚠️ In practice a well-implemented OS CSPRNG seeded properly\n(see a cryptography reference) is sufficient for almost all purposes, and QRNG's real value\nis as a high-quality entropy source for seeding, and where certification demands it.**\n⚠️ **Note that a QRNG still needs post-processing and health testing — a raw quantum source\nwith a device bias is just a biased source.**\n\n---\n\n## §22. The Quantum Computing Threat\n\n**⚠️ Brief, because a cryptography reference covers the migration.**\n⚠️ **SHOR'S ALGORITHM breaks RSA, Diffie-Hellman and elliptic curve cryptography — the\npublic-key foundations.** ⚠️ **GROVER'S ALGORITHM gives a quadratic speedup on brute-force\nsearch, which effectively halves symmetric key strength and is why AES-256 remains\nadequate.**\n**⚠️ Requires a CRYPTOGRAPHICALLY RELEVANT quantum computer** — ⚠️ **millions of\nhigh-quality error-corrected logical qubits, which is far beyond current hardware.**\n**⚠️ Timeline estimates vary enormously and should be treated with suspicion in both\ndirections** — ⚠️ **vendors and national programmes both have incentives.**\n**⚠️ HARVEST NOW, DECRYPT LATER is why the timeline is less important than people think**:\n⚠️ **recorded traffic is a stored liability, so the relevant question is secrecy lifetime\nplus migration time.**\n\n---\n\n## §23. ⚠️ Choosing\n\n```\n⚠️ FOR ESSENTIALLY EVERY ORGANIZATION: ⚠️ PQC\n   ⚠️ Software upgrade · works end to end at any distance ·\n   provides authentication · standardized · endorsed by every\n   major agency · no new physical infrastructure\n⚠️ QKD MIGHT MAKE SENSE WHEN, ALL AT ONCE\n   ⚠️ You control dedicated fibre between two fixed points\n   ⚠️ The distance is short, or you accept trusted nodes (§13)\n   ⚠️ You already have pre-shared symmetric keys for\n      authentication (§10)\n   ⚠️ The cost is acceptable for a small number of links\n   ⚠️ You want defence in depth rather than a replacement\n   ⚠️ Or you have a sovereignty\u002Fstrategic reason distinct from\n      the technical case\n⚠️ THE DEFENSIBLE HYBRID POSITION  ⚠️ QKD-derived key XORed or\n   combined with a PQC-derived key, so security holds if EITHER\n   holds. ⚠️ This is the architecture serious QKD deployments use,\n   and it is an honest answer to §20's objections\n⚠️ ALSO GENUINELY AVAILABLE  ⚠️ pre-shared symmetric keys with\n   AES-256. ⚠️ Unglamorous, quantum-resistant, and adequate for\n   the fixed-point-to-point case QKD targets\n```\n**⚠️ The question to ask any QKD vendor**: ⚠️ **\"how do you authenticate the classical\nchannel, and how many trusted nodes are in this path?\"** ⚠️ **The answers locate the actual\ntrust boundary.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fquantum-cryptography-and-quantum-internet\u002Fskills\u002Fqcrypto-official-position-qrng-quantum-threat-and-choosing",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill qcrypto-official-position-qrng-quantum-threat-and-choosing",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill qcrypto-official-position-qrng-quantum-threat-and-choosing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill qcrypto-official-position-qrng-quantum-threat-and-choosing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fquantum-cryptography-and-quantum-internet\u002Fskills\u002Fqcrypto-official-position-qrng-quantum-threat-and-choosing\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"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":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]