[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AM9SC6DN5EZ73YHB7Q78NX":3,"skill-same:01M7AM9SC6DN5EZ73YHB7Q78NX":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},"01M7AM9SC6DN5EZ73YHB7Q78NX","comms-encryption-metadata-interoperability-and-policy",null,"Use when the question is about privacy, policy or reliability: what end-to-end encryption actually protects and the backup, endpoint and multi-device gaps it does not close, metadata and why it is often more revealing than content, interoperability and regulation including the DMA messaging mandates, the encryption policy debate over client-side scanning and lawful access, and emergency calling and network reliability obligations.","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\u002Fcommunication-technologies\u002Fskills\u002Fcomms-encryption-metadata-interoperability-and-policy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: comms-encryption-metadata-interoperability-and-policy\ndescription: \"Use when the question is about privacy, policy or reliability: what end-to-end encryption actually protects and the backup, endpoint and multi-device gaps it does not close, metadata and why it is often more revealing than content, interoperability and regulation including the DMA messaging mandates, the encryption policy debate over client-side scanning and lawful access, and emergency calling and network reliability obligations.\"\n---\n\n# Communication Technologies: What End-to-End Encryption Actually Protects, Metadata, Interoperability and Regulation, the Encryption Policy Debate, and Emergency Calling\n\n> **Part 5 of 6** of the *Communication Technologies* reference (plugin `communication-technologies`), covering §23–§27. Sibling skills: `comms-email-smtp-authentication-and-deliverability` (§0–§7), `comms-telephony-pstn-ss7-voip-and-caller-id` (§8–§12), `comms-sms-rcs-signal-protocol-and-messaging-apps` (§13–§18), `comms-webrtc-video-conferencing-team-platforms-and-push` (§19–§22), `comms-reference` (§28–§33). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The protocols are old and stable. Two things moved. See §28 → `comms-reference` for cross-platform encrypted RCS, and the legal status of message scanning.\n\n> **⚠️ The most-used software category on earth, built on protocols mostly designed before\n> the threats they now face existed.**\n>\n> **Builds on a cryptography reference (key exchange, forward secrecy, authentication), a\n> wireless reference (cellular and Bluetooth layers), and a computer-hardware reference\n> (networking). Complements a speaking-and-influence reference for the human side.**\n>\n> **⚠️ GOTCHA** boxes mark where the security or reliability property people assume is not\n> the one the system actually provides.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ FEDERATED VERSUS PROPRIETARY IS THE DEEPEST DIVIDE** (§1 → `comms-email-smtp-authentication-and-deliverability`). **Email, SMS and the\n>    phone network are federated — anyone can join, anyone can reach anyone, and nobody can\n>    fix them unilaterally. Signal, iMessage and Slack are proprietary — coherent, secure,\n>    improvable, and walled. Almost every frustration in this domain traces to that trade.**\n> 2. **⚠️ \"ENCRYPTED\" IS FOUR DIFFERENT CLAIMS** (§23). **Transport encryption,\n>    encryption at rest, end-to-end encryption, and end-to-end encryption with verified\n>    keys are wildly different guarantees, and marketing conflates them constantly.**\n> 3. **⚠️ METADATA IS USUALLY THE POINT** (§24). **Who talked to whom, when, how often and\n>    from where survives content encryption — and for most surveillance purposes it is more\n>    valuable than content. A system can be perfectly end-to-end encrypted and still\n>    surveillable.**\n\n---\n\n## §23. ⚠️ What End-to-End Encryption Actually Protects\n\n```\n⚠️ ⚠️ FOUR DIFFERENT CLAIMS, routinely conflated\n   ⚠️ 1. TRANSPORT ENCRYPTION (TLS)  ⚠️ protects the wire.\n      ⚠️ THE PROVIDER READS EVERYTHING\n   ⚠️ 2. ENCRYPTION AT REST  ⚠️ protects stolen disks.\n      ⚠️ The provider holds the keys\n   ⚠️ 3. ⚠️ END-TO-END ENCRYPTION  ⚠️ only the endpoints can\n      read it. ⚠️ The provider cannot\n   ⚠️ 4. ⚠️ E2EE WITH VERIFIED KEYS  ⚠️ plus assurance you are\n      talking to who you think\n⚠️ ⚠️ WHAT E2EE DOES NOT PROTECT — and this list is the point\n   ⚠️ METADATA (§24) — usually the most valuable part\n   ⚠️ ⚠️ THE ENDPOINTS. ⚠️ A compromised phone defeats it\n      completely, which is what commercial spyware targets —\n      ⚠️ and it is why endpoint compromise is the actual\n      state-actor answer to encryption, not cryptanalysis\n   ⚠️ ⚠️ BACKUPS. ⚠️ Cloud backups are frequently NOT E2EE by\n      default, so an encrypted conversation sits in plaintext\n      in someone's backup (§18)\n   ⚠️ ⚠️ THE OTHER PARTY. ⚠️ They can screenshot, forward, or\n      simply be untrustworthy. ⚠️ Encryption is not confidence\n   ⚠️ ⚠️ KEY DISTRIBUTION. ⚠️ If the provider supplies the\n      public keys, they could in principle substitute one —\n      which is what key transparency and verification address,\n      and what almost nobody checks\n   ⚠️ CLIENT-SIDE SCANNING, which inspects BEFORE encryption\n      and is therefore not defeated by it at all (§26, §28.2)\n⚠️ ⚠️ THE PRACTICAL TEST FOR ANY CLAIM: ⚠️ CAN THE PROVIDER\n   SHOW YOU YOUR OLD MESSAGES ON A NEW DEVICE WITH ONLY A\n   PASSWORD? ⚠️ If yes, it is not end-to-end encrypted, or the\n   backup isn't\n```\n\n---\n\n## §24. ⚠️ Metadata\n\n**⚠️ What survives content encryption**: ⚠️ **who, whom, when, how often, how long,\nmessage sizes, from where, on what device, and the shape of your social graph.**\n**⚠️ Why it is often more valuable than content**: ⚠️ **it is structured, machine-analyzable\nat scale, and does not require reading anything — and the frequently-quoted intelligence\nformulation that metadata alone is sufficient for consequential decisions reflects a real\noperational view.**\n**⚠️ What can be inferred**: ⚠️ **relationships and their strength, sleep and work patterns,\nlocation history, health and legal circumstances (⚠️ from who you called), religious and\npolitical affiliation, and change points in a life.**\n**⚠️ What reduces it**: ⚠️ **Signal's sealed sender and private contact discovery, minimal\nretention policies, onion routing, and — most effectively — not having the data.**\n**⚠️ The legal asymmetry is the important part**: ⚠️ **in many jurisdictions metadata\nreceives markedly weaker protection than content, requiring a lower standard to obtain —\nwhich means the most revealing category is often the least protected.**\n\n---\n\n## §25. Interoperability and Regulation\n\n**⚠️ The EU Digital Markets Act** requires designated gatekeepers to make number-independent\nmessaging interoperable on request — ⚠️ **one-to-one first, groups and calls later.**\n**⚠️ The hard problem is doing it without destroying E2EE**: ⚠️ **bridging two protocols\ngenerally means decrypting at the boundary, and the alternative is agreeing on a shared\nprotocol — which is exactly what MLS was designed for** (§16 → `comms-sms-rcs-signal-protocol-and-messaging-apps`, §28.1 → `comms-reference`).\n**⚠️ The security community's concern** is genuine: ⚠️ **interoperability can mean the\nweakest participant sets the security level, and it complicates abuse handling, spam control\nand key verification across trust domains** (§1 → `comms-email-smtp-authentication-and-deliverability`).\n**⚠️ Meta has published proposals** for third-party chats in WhatsApp; ⚠️ **uptake has been\nlimited, and the honest observation is that a mandated interface nobody uses satisfies the\nregulation without changing anything.**\n**⚠️ The counterexample worth noting**: ⚠️ **RCS achieved cross-platform encrypted messaging\nthrough standardization rather than mandate** (§28.1 → `comms-reference`).\n\n---\n\n## §26. ⚠️ The Encryption Policy Debate\n\n```\n⚠️ THE COMPETING CLAIMS, stated fairly\n   ⚠️ LAW ENFORCEMENT  ⚠️ \"going dark\" — serious crime,\n      particularly child exploitation and terrorism, is\n      investigated using communications, and E2EE removes a\n      capability that lawful process previously reached\n   ⚠️ ⚠️ TECHNICAL AND SECURITY COMMUNITY  ⚠️ there is no\n      mechanism that gives access to authorized parties only.\n      ⚠️ An exceptional access capability is an additional\n      attack surface, and it will be targeted by everyone\n⚠️ THE PROPOSED MECHANISMS AND THEIR PROBLEMS\n   ⚠️ KEY ESCROW  ⚠️ the Clipper Chip era; ⚠️ concentrates\n      catastrophic risk in one database\n   ⚠️ GHOST PROTOCOL  ⚠️ silently add a participant — which\n      requires defeating exactly the key verification that\n      makes E2EE meaningful (§23)\n   ⚠️ ⚠️ CLIENT-SIDE SCANNING  ⚠️ the current proposal.\n      ⚠️ Inspect content ON THE DEVICE BEFORE encryption.\n      ⚠️ NOTE THE PRECISE TECHNICAL POINT: this does not BREAK\n      encryption, it CIRCUMVENTS it — the envelope stays sealed\n      and the contents are read before it is closed\n⚠️ ⚠️ THE TECHNICAL OBJECTIONS TO CSS, which are concrete\n   ⚠️ BASE RATE  ⚠️ at population scale, even a very accurate\n      classifier generates overwhelming false positives\n   ⚠️ ⚠️ SCOPE CREEP  ⚠️ once the infrastructure exists,\n      changing what it matches is a POLICY change, not a\n      technical one — and this argument does not depend on\n      distrusting current governments\n   ⚠️ Adversarial evasion, and adversarial false-positive\n      generation against innocent users\n   ⚠️ ⚠️ THE PRECEDENT PROBLEM  ⚠️ democracies establishing the\n      capability legitimizes it for states with fewer\n      constraints\n⚠️ ⚠️ APPLE'S 2021 CSAM SCANNING PLAN was announced, technically\n   sophisticated, and ABANDONED after sustained criticism —\n   ⚠️ the most concrete evidence available on whether this can\n   be deployed acceptably\n⚠️ ⚠️ AND THE OBSERVED PROVIDER RESPONSE (§28.2)  ⚠️ Signal has\n   said it would leave markets rather than comply, and major\n   providers have withdrawn FEATURES from jurisdictions rather\n   than weaken them globally\n```\n\n---\n\n## §27. Emergency Calling and Reliability\n\n**⚠️ Emergency calling carries obligations that ordinary services do not**: ⚠️ **location\ndelivery (E911 Phase II, AML on mobile), priority routing, and — historically — a\nguarantee of service without payment or SIM.**\n**⚠️ VoIP and VoWiFi break the location assumption** (§11 → `comms-telephony-pstn-ss7-voip-and-caller-id`) — ⚠️ **a nomadic IP endpoint has\nno fixed address, which is why registered-address requirements and dynamic location\nmechanisms exist, and why they fail in edge cases.**\n**⚠️ The power problem** is the underrated one: ⚠️ **the copper PSTN powered the handset from\nthe exchange, so phones worked in a blackout.** ⚠️ **All-IP does not, which is a genuine\nresilience regression that copper retirement (§8 → `comms-telephony-pstn-ss7-voip-and-caller-id`) has to plan around.**\n**⚠️ Text-to-emergency and RTT** matter for accessibility (see a speaking reference §23).\n**⚠️ Public warning systems** (cell broadcast) reach every handset in an area without\nknowing who they are, ⚠️ **which is a nice property — and false alerts have real\nconsequences.**\n","# Communication Technologies: What End-to-End Encryption Actually Protects, Metadata, Interoperability and Regulation, the Encryption Policy Debate, and Emergency Calling\n\n> **Part 5 of 6** of the *Communication Technologies* reference (plugin `communication-technologies`), covering §23–§27. Sibling skills: `comms-email-smtp-authentication-and-deliverability` (§0–§7), `comms-telephony-pstn-ss7-voip-and-caller-id` (§8–§12), `comms-sms-rcs-signal-protocol-and-messaging-apps` (§13–§18), `comms-webrtc-video-conferencing-team-platforms-and-push` (§19–§22), `comms-reference` (§28–§33). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The protocols are old and stable. Two things moved. See §28 → `comms-reference` for cross-platform encrypted RCS, and the legal status of message scanning.\n\n> **⚠️ The most-used software category on earth, built on protocols mostly designed before\n> the threats they now face existed.**\n>\n> **Builds on a cryptography reference (key exchange, forward secrecy, authentication), a\n> wireless reference (cellular and Bluetooth layers), and a computer-hardware reference\n> (networking). Complements a speaking-and-influence reference for the human side.**\n>\n> **⚠️ GOTCHA** boxes mark where the security or reliability property people assume is not\n> the one the system actually provides.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ FEDERATED VERSUS PROPRIETARY IS THE DEEPEST DIVIDE** (§1 → `comms-email-smtp-authentication-and-deliverability`). **Email, SMS and the\n>    phone network are federated — anyone can join, anyone can reach anyone, and nobody can\n>    fix them unilaterally. Signal, iMessage and Slack are proprietary — coherent, secure,\n>    improvable, and walled. Almost every frustration in this domain traces to that trade.**\n> 2. **⚠️ \"ENCRYPTED\" IS FOUR DIFFERENT CLAIMS** (§23). **Transport encryption,\n>    encryption at rest, end-to-end encryption, and end-to-end encryption with verified\n>    keys are wildly different guarantees, and marketing conflates them constantly.**\n> 3. **⚠️ METADATA IS USUALLY THE POINT** (§24). **Who talked to whom, when, how often and\n>    from where survives content encryption — and for most surveillance purposes it is more\n>    valuable than content. A system can be perfectly end-to-end encrypted and still\n>    surveillable.**\n\n---\n\n## §23. ⚠️ What End-to-End Encryption Actually Protects\n\n```\n⚠️ ⚠️ FOUR DIFFERENT CLAIMS, routinely conflated\n   ⚠️ 1. TRANSPORT ENCRYPTION (TLS)  ⚠️ protects the wire.\n      ⚠️ THE PROVIDER READS EVERYTHING\n   ⚠️ 2. ENCRYPTION AT REST  ⚠️ protects stolen disks.\n      ⚠️ The provider holds the keys\n   ⚠️ 3. ⚠️ END-TO-END ENCRYPTION  ⚠️ only the endpoints can\n      read it. ⚠️ The provider cannot\n   ⚠️ 4. ⚠️ E2EE WITH VERIFIED KEYS  ⚠️ plus assurance you are\n      talking to who you think\n⚠️ ⚠️ WHAT E2EE DOES NOT PROTECT — and this list is the point\n   ⚠️ METADATA (§24) — usually the most valuable part\n   ⚠️ ⚠️ THE ENDPOINTS. ⚠️ A compromised phone defeats it\n      completely, which is what commercial spyware targets —\n      ⚠️ and it is why endpoint compromise is the actual\n      state-actor answer to encryption, not cryptanalysis\n   ⚠️ ⚠️ BACKUPS. ⚠️ Cloud backups are frequently NOT E2EE by\n      default, so an encrypted conversation sits in plaintext\n      in someone's backup (§18)\n   ⚠️ ⚠️ THE OTHER PARTY. ⚠️ They can screenshot, forward, or\n      simply be untrustworthy. ⚠️ Encryption is not confidence\n   ⚠️ ⚠️ KEY DISTRIBUTION. ⚠️ If the provider supplies the\n      public keys, they could in principle substitute one —\n      which is what key transparency and verification address,\n      and what almost nobody checks\n   ⚠️ CLIENT-SIDE SCANNING, which inspects BEFORE encryption\n      and is therefore not defeated by it at all (§26, §28.2)\n⚠️ ⚠️ THE PRACTICAL TEST FOR ANY CLAIM: ⚠️ CAN THE PROVIDER\n   SHOW YOU YOUR OLD MESSAGES ON A NEW DEVICE WITH ONLY A\n   PASSWORD? ⚠️ If yes, it is not end-to-end encrypted, or the\n   backup isn't\n```\n\n---\n\n## §24. ⚠️ Metadata\n\n**⚠️ What survives content encryption**: ⚠️ **who, whom, when, how often, how long,\nmessage sizes, from where, on what device, and the shape of your social graph.**\n**⚠️ Why it is often more valuable than content**: ⚠️ **it is structured, machine-analyzable\nat scale, and does not require reading anything — and the frequently-quoted intelligence\nformulation that metadata alone is sufficient for consequential decisions reflects a real\noperational view.**\n**⚠️ What can be inferred**: ⚠️ **relationships and their strength, sleep and work patterns,\nlocation history, health and legal circumstances (⚠️ from who you called), religious and\npolitical affiliation, and change points in a life.**\n**⚠️ What reduces it**: ⚠️ **Signal's sealed sender and private contact discovery, minimal\nretention policies, onion routing, and — most effectively — not having the data.**\n**⚠️ The legal asymmetry is the important part**: ⚠️ **in many jurisdictions metadata\nreceives markedly weaker protection than content, requiring a lower standard to obtain —\nwhich means the most revealing category is often the least protected.**\n\n---\n\n## §25. Interoperability and Regulation\n\n**⚠️ The EU Digital Markets Act** requires designated gatekeepers to make number-independent\nmessaging interoperable on request — ⚠️ **one-to-one first, groups and calls later.**\n**⚠️ The hard problem is doing it without destroying E2EE**: ⚠️ **bridging two protocols\ngenerally means decrypting at the boundary, and the alternative is agreeing on a shared\nprotocol — which is exactly what MLS was designed for** (§16 → `comms-sms-rcs-signal-protocol-and-messaging-apps`, §28.1 → `comms-reference`).\n**⚠️ The security community's concern** is genuine: ⚠️ **interoperability can mean the\nweakest participant sets the security level, and it complicates abuse handling, spam control\nand key verification across trust domains** (§1 → `comms-email-smtp-authentication-and-deliverability`).\n**⚠️ Meta has published proposals** for third-party chats in WhatsApp; ⚠️ **uptake has been\nlimited, and the honest observation is that a mandated interface nobody uses satisfies the\nregulation without changing anything.**\n**⚠️ The counterexample worth noting**: ⚠️ **RCS achieved cross-platform encrypted messaging\nthrough standardization rather than mandate** (§28.1 → `comms-reference`).\n\n---\n\n## §26. ⚠️ The Encryption Policy Debate\n\n```\n⚠️ THE COMPETING CLAIMS, stated fairly\n   ⚠️ LAW ENFORCEMENT  ⚠️ \"going dark\" — serious crime,\n      particularly child exploitation and terrorism, is\n      investigated using communications, and E2EE removes a\n      capability that lawful process previously reached\n   ⚠️ ⚠️ TECHNICAL AND SECURITY COMMUNITY  ⚠️ there is no\n      mechanism that gives access to authorized parties only.\n      ⚠️ An exceptional access capability is an additional\n      attack surface, and it will be targeted by everyone\n⚠️ THE PROPOSED MECHANISMS AND THEIR PROBLEMS\n   ⚠️ KEY ESCROW  ⚠️ the Clipper Chip era; ⚠️ concentrates\n      catastrophic risk in one database\n   ⚠️ GHOST PROTOCOL  ⚠️ silently add a participant — which\n      requires defeating exactly the key verification that\n      makes E2EE meaningful (§23)\n   ⚠️ ⚠️ CLIENT-SIDE SCANNING  ⚠️ the current proposal.\n      ⚠️ Inspect content ON THE DEVICE BEFORE encryption.\n      ⚠️ NOTE THE PRECISE TECHNICAL POINT: this does not BREAK\n      encryption, it CIRCUMVENTS it — the envelope stays sealed\n      and the contents are read before it is closed\n⚠️ ⚠️ THE TECHNICAL OBJECTIONS TO CSS, which are concrete\n   ⚠️ BASE RATE  ⚠️ at population scale, even a very accurate\n      classifier generates overwhelming false positives\n   ⚠️ ⚠️ SCOPE CREEP  ⚠️ once the infrastructure exists,\n      changing what it matches is a POLICY change, not a\n      technical one — and this argument does not depend on\n      distrusting current governments\n   ⚠️ Adversarial evasion, and adversarial false-positive\n      generation against innocent users\n   ⚠️ ⚠️ THE PRECEDENT PROBLEM  ⚠️ democracies establishing the\n      capability legitimizes it for states with fewer\n      constraints\n⚠️ ⚠️ APPLE'S 2021 CSAM SCANNING PLAN was announced, technically\n   sophisticated, and ABANDONED after sustained criticism —\n   ⚠️ the most concrete evidence available on whether this can\n   be deployed acceptably\n⚠️ ⚠️ AND THE OBSERVED PROVIDER RESPONSE (§28.2)  ⚠️ Signal has\n   said it would leave markets rather than comply, and major\n   providers have withdrawn FEATURES from jurisdictions rather\n   than weaken them globally\n```\n\n---\n\n## §27. Emergency Calling and Reliability\n\n**⚠️ Emergency calling carries obligations that ordinary services do not**: ⚠️ **location\ndelivery (E911 Phase II, AML on mobile), priority routing, and — historically — a\nguarantee of service without payment or SIM.**\n**⚠️ VoIP and VoWiFi break the location assumption** (§11 → `comms-telephony-pstn-ss7-voip-and-caller-id`) — ⚠️ **a nomadic IP endpoint has\nno fixed address, which is why registered-address requirements and dynamic location\nmechanisms exist, and why they fail in edge cases.**\n**⚠️ The power problem** is the underrated one: ⚠️ **the copper PSTN powered the handset from\nthe exchange, so phones worked in a blackout.** ⚠️ **All-IP does not, which is a genuine\nresilience regression that copper retirement (§8 → `comms-telephony-pstn-ss7-voip-and-caller-id`) has to plan around.**\n**⚠️ Text-to-emergency and RTT** matter for accessibility (see a speaking reference §23).\n**⚠️ Public warning systems** (cell broadcast) reach every handset in an area without\nknowing who they are, ⚠️ **which is a nice property — and false alerts have real\nconsequences.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcommunication-technologies\u002Fskills\u002Fcomms-encryption-metadata-interoperability-and-policy",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 comms-encryption-metadata-interoperability-and-policy",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill comms-encryption-metadata-interoperability-and-policy",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill comms-encryption-metadata-interoperability-and-policy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcommunication-technologies\u002Fskills\u002Fcomms-encryption-metadata-interoperability-and-policy\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",[],[]]