[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARH3VRRA46D2A6ZCHT2HGF":3,"skill-same:01M7ARH3VRRA46D2A6ZCHT2HGF":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},"01M7ARH3VRRA46D2A6ZCHT2HGF","qcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation",null,"Use for the protocols themselves: BB84 step by step, entanglement-based QKD, continuous-variable QKD and how it differs in hardware and reach, and the post-processing that turns raw detections into a usable key — sifting, error correction and privacy amplification, which is where most of the practical difficulty lives.","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-bb84-entanglement-based-cv-qkd-and-key-distillation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: qcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation\ndescription: \"Use for the protocols themselves: BB84 step by step, entanglement-based QKD, continuous-variable QKD and how it differs in hardware and reach, and the post-processing that turns raw detections into a usable key — sifting, error correction and privacy amplification, which is where most of the practical difficulty lives.\"\n---\n\n# Quantum Cryptography: BB84, Entanglement-Based QKD, Continuous-Variable QKD, and From Raw Detections to a Usable Key\n\n> **Part 2 of 6** of the *Quantum Cryptography, Quantum Encryption and the Quantum Internet* reference (plugin `quantum-cryptography-and-quantum-internet`), covering §6–§9. Sibling skills: `qcrypto-two-different-things-qubits-no-cloning-and-entanglement` (§0–§5), `qcrypto-security-claims-attacks-and-trusted-nodes` (§10–§13), `qcrypto-repeaters-memory-entanglement-distribution-and-satellite` (§14–§19), `qcrypto-official-position-qrng-quantum-threat-and-choosing` (§20–§23), `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 → `qcrypto-official-position-qrng-quantum-threat-and-choosing`).\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## §6. BB84\n\n**⚠️ Bennett and Brassard, 1984 — still the reference protocol.**\n```\n⚠️ THE PROTOCOL\n   1. Alice sends photons, each encoded in a RANDOMLY chosen basis\n      with a RANDOMLY chosen bit value\n   2. Bob measures each in a RANDOMLY chosen basis\n   3. ⚠️ SIFTING — over a public classical channel they compare\n      BASES ONLY (never values) and discard where they differ.\n      ⚠️ About half survive\n   4. They sacrifice a sample of the remaining bits to estimate\n      the ERROR RATE\n   ⚠️ 5. IF THE ERROR RATE IS TOO HIGH, THEY ABORT — an eavesdropper\n      measuring in the wrong basis (§2) injects errors\n   6. Error correction and privacy amplification (§9)\n⚠️ THE SECURITY INTUITION  ⚠️ eavesdropping is not PREVENTED,\n   it is DETECTED. ⚠️ QKD does not stop interception; it stops you\n   USING a key that was intercepted\n```\n**⚠️ Variants**: **B92 (simpler, two states), SARG04, and six-state protocols.**\n> **⚠️ GOTCHA — real systems don't have single-photon sources, and this created a real\n> attack.** ⚠️ **Attenuated lasers emit a Poissonian number of photons, so some pulses\n> contain two or more — and an eavesdropper can split off the extra photon and keep it,\n> learning the bit without disturbing what Bob receives.** **That is the PHOTON NUMBER\n> SPLITTING attack.**\n> ⚠️ **The fix — DECOY STATES, where the sender randomly varies pulse intensity so that\n> splitting produces detectable statistical anomalies — is now standard and essentially\n> mandatory. A QKD system without decoy states is not secure with realistic sources.**\n\n---\n\n## §7. Entanglement-Based QKD\n\n**⚠️ E91 (Ekert, 1991)** uses entangled pairs: ⚠️ **a source distributes one photon to each\nparty, and correlated measurements produce the key.** **⚠️ Security comes from BELL\nINEQUALITY VIOLATION — if the correlations are strong enough to violate Bell, monogamy\n(§4 → `qcrypto-two-different-things-qubits-no-cloning-and-entanglement`) bounds what any eavesdropper can know.**\n**⚠️ BBM92** is the practical entangled-source variant.\n**⚠️ Advantages**: ⚠️ **the source can sit in the middle and need not be trusted in some\nformulations; and no key exists anywhere until measurement, so there is nothing to steal\nin advance.**\n**⚠️ Disadvantages**: ⚠️ **entangled sources are harder, and rates are lower.**\n\n---\n\n## §8. Continuous-Variable QKD\n\n**⚠️ Encodes in the quadratures of the light field rather than in discrete photon states**\n— ⚠️ **and uses HOMODYNE DETECTION, which works with standard telecom photodiodes rather\nthan single-photon detectors.**\n**⚠️ Advantages**: ⚠️ **cheaper, room-temperature detectors, better compatibility with\nexisting telecom equipment and wavelength multiplexing.**\n**⚠️ Disadvantages**: ⚠️ **shorter range, more demanding error correction at low\nsignal-to-noise, and security proofs that historically lagged discrete-variable ones.**\n\n---\n\n## §9. ⚠️ From Raw Detections to a Usable Key\n\n> **⚠️ The part popular accounts skip entirely, and it is where most of the actual\n> engineering lives.**\n```\n⚠️ 1. SIFTING  discard basis mismatches (§6)\n⚠️ 2. PARAMETER ESTIMATION  measure the QBER (quantum bit error\n   rate). ⚠️ ALL errors must be attributed to the eavesdropper,\n   because you cannot distinguish an attacker from a noisy fibre\n⚠️ 3. ERROR RECONCILIATION  ⚠️ classical error correction over the\n   public channel (Cascade, LDPC). ⚠️ This LEAKS information, and\n   the leak must be accounted for in step 4\n⚠️ 4. ⚠️ PRIVACY AMPLIFICATION  compress the corrected key with a\n   universal hash so that the eavesdropper's partial knowledge is\n   reduced to negligible. ⚠️ You throw away bits to buy secrecy\n⚠️ 5. ⚠️ AUTHENTICATION of the classical channel — ⚠️ SEE §10\n⚠️ THE RESULT  ⚠️ the final secret key is much shorter than the raw\n   detections. ⚠️ Quoted \"key rates\" should always be SECRET key\n   rate after all of this, and marketing sometimes quotes raw\n```\n**⚠️ Finite-key effects matter**: ⚠️ **asymptotic security proofs assume infinitely long\nkeys; real finite blocks require a stricter analysis and yield less key.** ⚠️ **A system\nquoting asymptotic rates is quoting an upper bound it never achieves.**\n","# Quantum Cryptography: BB84, Entanglement-Based QKD, Continuous-Variable QKD, and From Raw Detections to a Usable Key\n\n> **Part 2 of 6** of the *Quantum Cryptography, Quantum Encryption and the Quantum Internet* reference (plugin `quantum-cryptography-and-quantum-internet`), covering §6–§9. Sibling skills: `qcrypto-two-different-things-qubits-no-cloning-and-entanglement` (§0–§5), `qcrypto-security-claims-attacks-and-trusted-nodes` (§10–§13), `qcrypto-repeaters-memory-entanglement-distribution-and-satellite` (§14–§19), `qcrypto-official-position-qrng-quantum-threat-and-choosing` (§20–§23), `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 → `qcrypto-official-position-qrng-quantum-threat-and-choosing`).\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## §6. BB84\n\n**⚠️ Bennett and Brassard, 1984 — still the reference protocol.**\n```\n⚠️ THE PROTOCOL\n   1. Alice sends photons, each encoded in a RANDOMLY chosen basis\n      with a RANDOMLY chosen bit value\n   2. Bob measures each in a RANDOMLY chosen basis\n   3. ⚠️ SIFTING — over a public classical channel they compare\n      BASES ONLY (never values) and discard where they differ.\n      ⚠️ About half survive\n   4. They sacrifice a sample of the remaining bits to estimate\n      the ERROR RATE\n   ⚠️ 5. IF THE ERROR RATE IS TOO HIGH, THEY ABORT — an eavesdropper\n      measuring in the wrong basis (§2) injects errors\n   6. Error correction and privacy amplification (§9)\n⚠️ THE SECURITY INTUITION  ⚠️ eavesdropping is not PREVENTED,\n   it is DETECTED. ⚠️ QKD does not stop interception; it stops you\n   USING a key that was intercepted\n```\n**⚠️ Variants**: **B92 (simpler, two states), SARG04, and six-state protocols.**\n> **⚠️ GOTCHA — real systems don't have single-photon sources, and this created a real\n> attack.** ⚠️ **Attenuated lasers emit a Poissonian number of photons, so some pulses\n> contain two or more — and an eavesdropper can split off the extra photon and keep it,\n> learning the bit without disturbing what Bob receives.** **That is the PHOTON NUMBER\n> SPLITTING attack.**\n> ⚠️ **The fix — DECOY STATES, where the sender randomly varies pulse intensity so that\n> splitting produces detectable statistical anomalies — is now standard and essentially\n> mandatory. A QKD system without decoy states is not secure with realistic sources.**\n\n---\n\n## §7. Entanglement-Based QKD\n\n**⚠️ E91 (Ekert, 1991)** uses entangled pairs: ⚠️ **a source distributes one photon to each\nparty, and correlated measurements produce the key.** **⚠️ Security comes from BELL\nINEQUALITY VIOLATION — if the correlations are strong enough to violate Bell, monogamy\n(§4 → `qcrypto-two-different-things-qubits-no-cloning-and-entanglement`) bounds what any eavesdropper can know.**\n**⚠️ BBM92** is the practical entangled-source variant.\n**⚠️ Advantages**: ⚠️ **the source can sit in the middle and need not be trusted in some\nformulations; and no key exists anywhere until measurement, so there is nothing to steal\nin advance.**\n**⚠️ Disadvantages**: ⚠️ **entangled sources are harder, and rates are lower.**\n\n---\n\n## §8. Continuous-Variable QKD\n\n**⚠️ Encodes in the quadratures of the light field rather than in discrete photon states**\n— ⚠️ **and uses HOMODYNE DETECTION, which works with standard telecom photodiodes rather\nthan single-photon detectors.**\n**⚠️ Advantages**: ⚠️ **cheaper, room-temperature detectors, better compatibility with\nexisting telecom equipment and wavelength multiplexing.**\n**⚠️ Disadvantages**: ⚠️ **shorter range, more demanding error correction at low\nsignal-to-noise, and security proofs that historically lagged discrete-variable ones.**\n\n---\n\n## §9. ⚠️ From Raw Detections to a Usable Key\n\n> **⚠️ The part popular accounts skip entirely, and it is where most of the actual\n> engineering lives.**\n```\n⚠️ 1. SIFTING  discard basis mismatches (§6)\n⚠️ 2. PARAMETER ESTIMATION  measure the QBER (quantum bit error\n   rate). ⚠️ ALL errors must be attributed to the eavesdropper,\n   because you cannot distinguish an attacker from a noisy fibre\n⚠️ 3. ERROR RECONCILIATION  ⚠️ classical error correction over the\n   public channel (Cascade, LDPC). ⚠️ This LEAKS information, and\n   the leak must be accounted for in step 4\n⚠️ 4. ⚠️ PRIVACY AMPLIFICATION  compress the corrected key with a\n   universal hash so that the eavesdropper's partial knowledge is\n   reduced to negligible. ⚠️ You throw away bits to buy secrecy\n⚠️ 5. ⚠️ AUTHENTICATION of the classical channel — ⚠️ SEE §10\n⚠️ THE RESULT  ⚠️ the final secret key is much shorter than the raw\n   detections. ⚠️ Quoted \"key rates\" should always be SECRET key\n   rate after all of this, and marketing sometimes quotes raw\n```\n**⚠️ Finite-key effects matter**: ⚠️ **asymptotic security proofs assume infinitely long\nkeys; real finite blocks require a stricter analysis and yield less key.** ⚠️ **A system\nquoting asymptotic rates is quoting an upper bound it never achieves.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fquantum-cryptography-and-quantum-internet\u002Fskills\u002Fqcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation",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-bb84-entanglement-based-cv-qkd-and-key-distillation",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill qcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill qcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fquantum-cryptography-and-quantum-internet\u002Fskills\u002Fqcrypto-bb84-entanglement-based-cv-qkd-and-key-distillation\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",[],[]]