[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMAM2R3SE6WRXEWWKF80K9":3,"skill-same:01M7AMAM2R3SE6WRXEWWKF80K9":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},"01M7AMAM2R3SE6WRXEWWKF80K9","comms-webrtc-video-conferencing-team-platforms-and-push",null,"Use for real-time and collaboration: WebRTC including ICE, STUN, TURN and the signalling you have to build yourself, video conferencing architecture across mesh, SFU and MCU topologies and the bandwidth and quality trade-offs, team platforms, and push and notification delivery and what the push infrastructure can see.","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-webrtc-video-conferencing-team-platforms-and-push\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: comms-webrtc-video-conferencing-team-platforms-and-push\ndescription: \"Use for real-time and collaboration: WebRTC including ICE, STUN, TURN and the signalling you have to build yourself, video conferencing architecture across mesh, SFU and MCU topologies and the bandwidth and quality trade-offs, team platforms, and push and notification delivery and what the push infrastructure can see.\"\n---\n\n# Communication Technologies: WebRTC, Video Conferencing Architecture, Team Platforms, and Push and Notifications\n\n> **Part 4 of 6** of the *Communication Technologies* reference (plugin `communication-technologies`), covering §19–§22. 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-encryption-metadata-interoperability-and-policy` (§23–§27), `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 → `comms-encryption-metadata-interoperability-and-policy`). **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 → `comms-encryption-metadata-interoperability-and-policy`). **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## §19. ⚠️ WebRTC\n\n**⚠️ Real-time audio, video and data in the browser with no plugin** — ⚠️ **and it is the\nfoundation of most modern conferencing, including products that do not advertise it.**\n**⚠️ The pieces**: ⚠️ **getUserMedia for capture, RTCPeerConnection for transport,\nRTCDataChannel for arbitrary data (⚠️ over SCTP, giving optionally-reliable\noptionally-ordered delivery).**\n**⚠️ Signalling is deliberately NOT specified** — ⚠️ **you bring your own, which is why every\nWebRTC application needs a server before two browsers can talk.**\n**⚠️ ICE, STUN and TURN** (§10 → `comms-telephony-pstn-ss7-voip-and-caller-id`) — ⚠️ **and TURN relaying is the expensive fallback that a\nmeaningful fraction of connections need.**\n> **⚠️ GOTCHA — WebRTC leaks your local and public IP addresses to the page by design**,\n> ⚠️ **because ICE candidate gathering requires it.** **⚠️ This has been used for\n> de-anonymization and VPN leak detection, and browsers have added mitigations that are\n> partial.**\n\n**⚠️ SRTP with DTLS key exchange** means media is always encrypted in transit — ⚠️ **which\nis not the same as end-to-end encrypted once an SFU is involved** (§20).\n\n---\n\n## §20. Video Conferencing Architecture\n\n```\n⚠️ THE THREE TOPOLOGIES, and the choice explains everything\n   ⚠️ MESH  ⚠️ everyone sends to everyone. ⚠️ No server cost,\n      and upstream bandwidth explodes past 3-4 participants\n   ⚠️ ⚠️ SFU (Selective Forwarding Unit)  ⚠️ THE STANDARD ANSWER.\n      Each client sends once; the server FORWARDS streams\n      without decoding. ⚠️ Cheap server-side, and the client\n      receives many streams\n   ⚠️ MCU  ⚠️ the server decodes and composites into one stream.\n      ⚠️ Expensive in CPU, and the only option for very weak\n      clients\n⚠️ SIMULCAST and SVC  ⚠️ send multiple qualities so the SFU can\n   forward the appropriate one per receiver — ⚠️ this is what\n   makes a gallery view of thirty people work at all\n⚠️ ⚠️ THE E2EE PROBLEM  ⚠️ an SFU only forwards, so it CAN work\n   with E2EE (insertable streams) — ⚠️ but any server-side\n   feature that needs the content (recording, transcription,\n   noise suppression, virtual backgrounds computed server-side)\n   becomes impossible. ⚠️ THIS TENSION IS WHY MOST CONFERENCING\n   IS NOT E2EE BY DEFAULT\n   ⚠️ Zoom's 2020 \"end-to-end encrypted\" marketing was found to\n   describe transport encryption, resulting in an FTC\n   settlement — ⚠️ the canonical example of §23's confusion\n   being commercially convenient\n⚠️ THE ACTUAL QUALITY WORK  ⚠️ echo cancellation (⚠️ genuinely\n   hard, and why headsets help), noise suppression, automatic\n   gain, jitter buffering, loss concealment, bandwidth\n   estimation and congestion control\n```\n\n---\n\n## §21. Team Platforms\n\n**⚠️ Slack** — ⚠️ **channel-based, strong integration model, and the search-and-history\nproduct is arguably what people actually pay for.**\n**⚠️ Microsoft Teams** — ⚠️ **wins on bundling rather than on product, and the deep\nOffice\u002FGraph integration is the genuine differentiator.** ⚠️ **The EU competition case over\nbundling with Office led to unbundling commitments.**\n**⚠️ Discord** — ⚠️ **built for gaming latency, and its persistent-voice-channel model turns\nout to suit communities better than meeting-based tools do.**\n**⚠️ The common architecture**: ⚠️ **WebSocket for real-time, an event\u002Fmessage bus, presence\nservices, and search over history — with the hard engineering in fan-out at scale and in\nnotification routing** (§22).\n> **⚠️ GOTCHA — none of these are end-to-end encrypted, and they generally cannot be.**\n> ⚠️ **Search, compliance retention, eDiscovery, DLP and admin export all require the\n> provider to read content — and enterprise buyers demand exactly those features.**\n> **⚠️ Assume your employer can read anything in them, because that is a contractual product\n> feature, not a flaw.**\n\n---\n\n## §22. Push and Notifications\n\n**⚠️ Mobile push exists because battery does not permit persistent connections per app** —\n⚠️ **so one OS-level channel multiplexes for everything.**\n**⚠️ APNs and FCM** are that channel, ⚠️ **which means Apple and Google see notification\nmetadata for essentially every app — ⚠️ and government requests for push notification\nrecords have been documented, which is a §24 → `comms-encryption-metadata-interoperability-and-policy` problem hiding in an engineering decision.**\n**⚠️ E2EE apps handle this** by sending a content-free wake-up push and fetching the\nmessage, ⚠️ **so the notification service learns that a message arrived but not what it\nsays.**\n**⚠️ Web push** uses VAPID and encrypted payloads.\n**⚠️ The design problem** is notification fatigue — ⚠️ **and the honest observation is that\nplatforms optimizing for engagement have an incentive that runs directly against the user's\ninterest here.**\n\n---\n\n# PART V — CROSS-CUTTING\n","# Communication Technologies: WebRTC, Video Conferencing Architecture, Team Platforms, and Push and Notifications\n\n> **Part 4 of 6** of the *Communication Technologies* reference (plugin `communication-technologies`), covering §19–§22. 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-encryption-metadata-interoperability-and-policy` (§23–§27), `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 → `comms-encryption-metadata-interoperability-and-policy`). **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 → `comms-encryption-metadata-interoperability-and-policy`). **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## §19. ⚠️ WebRTC\n\n**⚠️ Real-time audio, video and data in the browser with no plugin** — ⚠️ **and it is the\nfoundation of most modern conferencing, including products that do not advertise it.**\n**⚠️ The pieces**: ⚠️ **getUserMedia for capture, RTCPeerConnection for transport,\nRTCDataChannel for arbitrary data (⚠️ over SCTP, giving optionally-reliable\noptionally-ordered delivery).**\n**⚠️ Signalling is deliberately NOT specified** — ⚠️ **you bring your own, which is why every\nWebRTC application needs a server before two browsers can talk.**\n**⚠️ ICE, STUN and TURN** (§10 → `comms-telephony-pstn-ss7-voip-and-caller-id`) — ⚠️ **and TURN relaying is the expensive fallback that a\nmeaningful fraction of connections need.**\n> **⚠️ GOTCHA — WebRTC leaks your local and public IP addresses to the page by design**,\n> ⚠️ **because ICE candidate gathering requires it.** **⚠️ This has been used for\n> de-anonymization and VPN leak detection, and browsers have added mitigations that are\n> partial.**\n\n**⚠️ SRTP with DTLS key exchange** means media is always encrypted in transit — ⚠️ **which\nis not the same as end-to-end encrypted once an SFU is involved** (§20).\n\n---\n\n## §20. Video Conferencing Architecture\n\n```\n⚠️ THE THREE TOPOLOGIES, and the choice explains everything\n   ⚠️ MESH  ⚠️ everyone sends to everyone. ⚠️ No server cost,\n      and upstream bandwidth explodes past 3-4 participants\n   ⚠️ ⚠️ SFU (Selective Forwarding Unit)  ⚠️ THE STANDARD ANSWER.\n      Each client sends once; the server FORWARDS streams\n      without decoding. ⚠️ Cheap server-side, and the client\n      receives many streams\n   ⚠️ MCU  ⚠️ the server decodes and composites into one stream.\n      ⚠️ Expensive in CPU, and the only option for very weak\n      clients\n⚠️ SIMULCAST and SVC  ⚠️ send multiple qualities so the SFU can\n   forward the appropriate one per receiver — ⚠️ this is what\n   makes a gallery view of thirty people work at all\n⚠️ ⚠️ THE E2EE PROBLEM  ⚠️ an SFU only forwards, so it CAN work\n   with E2EE (insertable streams) — ⚠️ but any server-side\n   feature that needs the content (recording, transcription,\n   noise suppression, virtual backgrounds computed server-side)\n   becomes impossible. ⚠️ THIS TENSION IS WHY MOST CONFERENCING\n   IS NOT E2EE BY DEFAULT\n   ⚠️ Zoom's 2020 \"end-to-end encrypted\" marketing was found to\n   describe transport encryption, resulting in an FTC\n   settlement — ⚠️ the canonical example of §23's confusion\n   being commercially convenient\n⚠️ THE ACTUAL QUALITY WORK  ⚠️ echo cancellation (⚠️ genuinely\n   hard, and why headsets help), noise suppression, automatic\n   gain, jitter buffering, loss concealment, bandwidth\n   estimation and congestion control\n```\n\n---\n\n## §21. Team Platforms\n\n**⚠️ Slack** — ⚠️ **channel-based, strong integration model, and the search-and-history\nproduct is arguably what people actually pay for.**\n**⚠️ Microsoft Teams** — ⚠️ **wins on bundling rather than on product, and the deep\nOffice\u002FGraph integration is the genuine differentiator.** ⚠️ **The EU competition case over\nbundling with Office led to unbundling commitments.**\n**⚠️ Discord** — ⚠️ **built for gaming latency, and its persistent-voice-channel model turns\nout to suit communities better than meeting-based tools do.**\n**⚠️ The common architecture**: ⚠️ **WebSocket for real-time, an event\u002Fmessage bus, presence\nservices, and search over history — with the hard engineering in fan-out at scale and in\nnotification routing** (§22).\n> **⚠️ GOTCHA — none of these are end-to-end encrypted, and they generally cannot be.**\n> ⚠️ **Search, compliance retention, eDiscovery, DLP and admin export all require the\n> provider to read content — and enterprise buyers demand exactly those features.**\n> **⚠️ Assume your employer can read anything in them, because that is a contractual product\n> feature, not a flaw.**\n\n---\n\n## §22. Push and Notifications\n\n**⚠️ Mobile push exists because battery does not permit persistent connections per app** —\n⚠️ **so one OS-level channel multiplexes for everything.**\n**⚠️ APNs and FCM** are that channel, ⚠️ **which means Apple and Google see notification\nmetadata for essentially every app — ⚠️ and government requests for push notification\nrecords have been documented, which is a §24 → `comms-encryption-metadata-interoperability-and-policy` problem hiding in an engineering decision.**\n**⚠️ E2EE apps handle this** by sending a content-free wake-up push and fetching the\nmessage, ⚠️ **so the notification service learns that a message arrived but not what it\nsays.**\n**⚠️ Web push** uses VAPID and encrypted payloads.\n**⚠️ The design problem** is notification fatigue — ⚠️ **and the honest observation is that\nplatforms optimizing for engagement have an incentive that runs directly against the user's\ninterest here.**\n\n---\n\n# PART V — CROSS-CUTTING\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcommunication-technologies\u002Fskills\u002Fcomms-webrtc-video-conferencing-team-platforms-and-push",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-webrtc-video-conferencing-team-platforms-and-push",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill comms-webrtc-video-conferencing-team-platforms-and-push",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill comms-webrtc-video-conferencing-team-platforms-and-push","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcommunication-technologies\u002Fskills\u002Fcomms-webrtc-video-conferencing-team-platforms-and-push\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",[],[]]