[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMADBG02AQ2QKF2APR3K8T":3,"skill-same:01M7AMADBG02AQ2QKF2APR3K8T":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},"01M7AMADBG02AQ2QKF2APR3K8T","comms-telephony-pstn-ss7-voip-and-caller-id",null,"Use for voice: the PSTN and circuit switching, SS7 and the signalling trust model that makes location tracking and SMS interception possible, VoIP and SIP with NAT traversal and codecs, VoLTE and VoNR carrying voice over IP in mobile networks, and caller ID, spoofing, robocalls and the STIR\u002FSHAKEN attestation scheme with its real limits.","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-telephony-pstn-ss7-voip-and-caller-id\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: comms-telephony-pstn-ss7-voip-and-caller-id\ndescription: \"Use for voice: the PSTN and circuit switching, SS7 and the signalling trust model that makes location tracking and SMS interception possible, VoIP and SIP with NAT traversal and codecs, VoLTE and VoNR carrying voice over IP in mobile networks, and caller ID, spoofing, robocalls and the STIR\u002FSHAKEN attestation scheme with its real limits.\"\n---\n\n# Communication Technologies: The PSTN, SS7 and Its Security Problem, VoIP and SIP, VoLTE and VoNR, and Caller ID, Spoofing and Robocalls\n\n> **Part 2 of 6** of the *Communication Technologies* reference (plugin `communication-technologies`), covering §8–§12. Sibling skills: `comms-email-smtp-authentication-and-deliverability` (§0–§7), `comms-sms-rcs-signal-protocol-and-messaging-apps` (§13–§18), `comms-webrtc-video-conferencing-team-platforms-and-push` (§19–§22), `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## §8. The PSTN\n\n**⚠️ Circuit switching** dedicated a path for the call's duration — ⚠️ **which guaranteed\nquality and wasted capacity, and is the opposite of packet switching's trade.**\n**⚠️ The hierarchy**: ⚠️ **local loop, central office\u002Fexchange, tandem and toll switches,\nwith E.164 numbering as the global address space.**\n**⚠️ Digital voice**: ⚠️ **8 kHz sampling, 8-bit companded (μ-law\u002FA-law) = 64 kbit\u002Fs, which\nis the DS0 that the whole T1\u002FE1 hierarchy is built from.** ⚠️ **This is why traditional\nphone audio sounds the way it does — 300–3400 Hz, a deliberate 1930s bandwidth choice.**\n**⚠️ Signalling**: ⚠️ **in-band originally (⚠️ which is what phone phreaking exploited),\nthen out-of-band via SS7** (§9).\n**⚠️ The PSTN is being switched off** — ⚠️ **copper retirement and all-IP migration are\nunderway in most developed markets, with real consequences for alarms, lifts, medical\npendants and payment terminals that assumed a powered analogue line.**\n\n---\n\n## §9. ⚠️ SS7 and Its Security Problem\n\n```\n⚠️ WHAT IT IS  ⚠️ the out-of-band signalling network that sets up\n   calls, routes SMS, handles roaming and queries subscriber\n   location. ⚠️ Designed in the 1970s-80s\n⚠️ ⚠️ THE DESIGN ASSUMPTION WAS A CLOSED CLUB OF TRUSTED STATE\n   MONOPOLY CARRIERS. ⚠️ There is essentially NO AUTHENTICATION\n   between network elements\n⚠️ ⚠️ WHEN DEREGULATION AND ROAMING OPENED IT UP, that\n   assumption failed — ⚠️ and access can be obtained through\n   small carriers, leased connections or compromised equipment\n⚠️ ⚠️ WHAT SS7 ACCESS PERMITS  ⚠️ locating a subscriber ·\n   ⚠️ INTERCEPTING SMS (⚠️ which defeats SMS-based two-factor\n   authentication, §13) · intercepting or redirecting calls ·\n   denial of service\n⚠️ ⚠️ THIS IS NOT THEORETICAL. ⚠️ It has been demonstrated\n   publicly, documented by regulators, and used in the wild\n⚠️ DIAMETER  ⚠️ the LTE-era successor, with better authentication\n   in principle and ⚠️ comparable classes of vulnerability in\n   practice, partly because interworking with SS7 is required\n⚠️ MITIGATIONS  ⚠️ SS7 firewalls, home routing, filtering — but\n   ⚠️ THE STRUCTURAL PROBLEM PERSISTS because the network must\n   interoperate globally with participants of varying integrity\n   (§1's federated trade, in its most consequential form)\n```\n\n---\n\n## §10. VoIP and SIP\n\n**⚠️ The separation that defines it**: ⚠️ **SIP handles signalling — establishing, modifying\nand terminating sessions — while RTP carries the actual media, on different ports and often\na different path.**\n**⚠️ SDP** negotiates codecs and addresses; ⚠️ **SRTP encrypts media; SIP over TLS protects\nsignalling.**\n**⚠️ Codecs**: ⚠️ **G.711 (uncompressed PSTN quality), G.722 and Opus for wideband —\n⚠️ and Opus is the modern default because it adapts across a huge bitrate range and handles\nloss gracefully.**\n**⚠️ NAT traversal is the perennial engineering pain**: ⚠️ **STUN discovers your public\naddress, TURN relays when direct connection fails, and ICE tries candidates in order**\n(§19 → `comms-webrtc-video-conferencing-team-platforms-and-push`).\n**⚠️ Quality metrics**: ⚠️ **latency (⚠️ interactivity degrades noticeably above roughly\n150 ms one-way), JITTER (⚠️ absorbed by a jitter buffer, which trades latency for\nsmoothness), and packet loss — ⚠️ and concealment algorithms mask modest loss surprisingly\nwell.**\n**⚠️ SIP trunking** replaced ISDN for business telephony, ⚠️ **and toll fraud on\nmisconfigured PBXs remains a live and expensive problem.**\n\n---\n\n## §11. VoLTE and VoNR\n\n**⚠️ Voice over LTE** carries voice as IP packets over the data network with QoS bearers,\n⚠️ **rather than falling back to a circuit-switched network.**\n**⚠️ The IMS core** is the architecture underneath, ⚠️ **and it is what makes voice a\nservice on the data network rather than a separate system.**\n**⚠️ The user-visible benefits**: ⚠️ **HD voice via wideband codecs (AMR-WB and EVS),\nmuch faster call setup, and simultaneous voice and data.**\n**⚠️ 2G and 3G shutdown** makes VoLTE mandatory rather than optional — ⚠️ **and this has\nstranded older handsets and, importantly, a great deal of embedded telemetry** (see a\nwireless reference §13).\n**⚠️ VoWiFi** uses the same IMS core over any internet connection, ⚠️ **which is why calls\nwork over hotel Wi-Fi with no coverage, and why emergency location becomes harder** (§27 → `comms-encryption-metadata-interoperability-and-policy`).\n\n---\n\n## §12. ⚠️ Caller ID, Spoofing and Robocalls\n\n**⚠️ Caller ID was never authenticated** — ⚠️ **the calling number is asserted by the\noriginating network and, with SIP trunking, is trivially set by the caller.**\n**⚠️ NEIGHBOUR SPOOFING** — ⚠️ **forging a number matching the recipient's prefix — exploits\nthis, and it is why answer rates for unknown numbers collapsed.**\n**⚠️ STIR\u002FSHAKEN** is the response: ⚠️ **the originating carrier cryptographically signs the\ncalling number with an attestation level (A: we know the caller and their right to the\nnumber; B: we know the customer but not the number; C: we just passed it on), and the\nterminating carrier verifies** (see a cryptography reference on certificate chains).\n> **⚠️ GOTCHA — STIR\u002FSHAKEN authenticates the CARRIER'S ASSERTION, not the caller's\n> honesty.** ⚠️ **An A-level attestation means a carrier vouched for the number, not that the\n> call is legitimate.** **⚠️ It also only works on IP-connected legs, so calls transiting\n> older segments lose the signature — which is exactly §1 → `comms-email-smtp-authentication-and-deliverability`'s weakest-participant problem.**\n\n**⚠️ It has helped and not solved**: ⚠️ **enforcement, traceback and gateway-provider\nobligations do more of the work than the cryptography does.**\n**⚠️ Branded calling** and RCS-verified sender identity (§15 → `comms-sms-rcs-signal-protocol-and-messaging-apps`) are the commercial responses to\nthe trust collapse.\n\n---\n\n# PART III — MESSAGING\n","# Communication Technologies: The PSTN, SS7 and Its Security Problem, VoIP and SIP, VoLTE and VoNR, and Caller ID, Spoofing and Robocalls\n\n> **Part 2 of 6** of the *Communication Technologies* reference (plugin `communication-technologies`), covering §8–§12. Sibling skills: `comms-email-smtp-authentication-and-deliverability` (§0–§7), `comms-sms-rcs-signal-protocol-and-messaging-apps` (§13–§18), `comms-webrtc-video-conferencing-team-platforms-and-push` (§19–§22), `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## §8. The PSTN\n\n**⚠️ Circuit switching** dedicated a path for the call's duration — ⚠️ **which guaranteed\nquality and wasted capacity, and is the opposite of packet switching's trade.**\n**⚠️ The hierarchy**: ⚠️ **local loop, central office\u002Fexchange, tandem and toll switches,\nwith E.164 numbering as the global address space.**\n**⚠️ Digital voice**: ⚠️ **8 kHz sampling, 8-bit companded (μ-law\u002FA-law) = 64 kbit\u002Fs, which\nis the DS0 that the whole T1\u002FE1 hierarchy is built from.** ⚠️ **This is why traditional\nphone audio sounds the way it does — 300–3400 Hz, a deliberate 1930s bandwidth choice.**\n**⚠️ Signalling**: ⚠️ **in-band originally (⚠️ which is what phone phreaking exploited),\nthen out-of-band via SS7** (§9).\n**⚠️ The PSTN is being switched off** — ⚠️ **copper retirement and all-IP migration are\nunderway in most developed markets, with real consequences for alarms, lifts, medical\npendants and payment terminals that assumed a powered analogue line.**\n\n---\n\n## §9. ⚠️ SS7 and Its Security Problem\n\n```\n⚠️ WHAT IT IS  ⚠️ the out-of-band signalling network that sets up\n   calls, routes SMS, handles roaming and queries subscriber\n   location. ⚠️ Designed in the 1970s-80s\n⚠️ ⚠️ THE DESIGN ASSUMPTION WAS A CLOSED CLUB OF TRUSTED STATE\n   MONOPOLY CARRIERS. ⚠️ There is essentially NO AUTHENTICATION\n   between network elements\n⚠️ ⚠️ WHEN DEREGULATION AND ROAMING OPENED IT UP, that\n   assumption failed — ⚠️ and access can be obtained through\n   small carriers, leased connections or compromised equipment\n⚠️ ⚠️ WHAT SS7 ACCESS PERMITS  ⚠️ locating a subscriber ·\n   ⚠️ INTERCEPTING SMS (⚠️ which defeats SMS-based two-factor\n   authentication, §13) · intercepting or redirecting calls ·\n   denial of service\n⚠️ ⚠️ THIS IS NOT THEORETICAL. ⚠️ It has been demonstrated\n   publicly, documented by regulators, and used in the wild\n⚠️ DIAMETER  ⚠️ the LTE-era successor, with better authentication\n   in principle and ⚠️ comparable classes of vulnerability in\n   practice, partly because interworking with SS7 is required\n⚠️ MITIGATIONS  ⚠️ SS7 firewalls, home routing, filtering — but\n   ⚠️ THE STRUCTURAL PROBLEM PERSISTS because the network must\n   interoperate globally with participants of varying integrity\n   (§1's federated trade, in its most consequential form)\n```\n\n---\n\n## §10. VoIP and SIP\n\n**⚠️ The separation that defines it**: ⚠️ **SIP handles signalling — establishing, modifying\nand terminating sessions — while RTP carries the actual media, on different ports and often\na different path.**\n**⚠️ SDP** negotiates codecs and addresses; ⚠️ **SRTP encrypts media; SIP over TLS protects\nsignalling.**\n**⚠️ Codecs**: ⚠️ **G.711 (uncompressed PSTN quality), G.722 and Opus for wideband —\n⚠️ and Opus is the modern default because it adapts across a huge bitrate range and handles\nloss gracefully.**\n**⚠️ NAT traversal is the perennial engineering pain**: ⚠️ **STUN discovers your public\naddress, TURN relays when direct connection fails, and ICE tries candidates in order**\n(§19 → `comms-webrtc-video-conferencing-team-platforms-and-push`).\n**⚠️ Quality metrics**: ⚠️ **latency (⚠️ interactivity degrades noticeably above roughly\n150 ms one-way), JITTER (⚠️ absorbed by a jitter buffer, which trades latency for\nsmoothness), and packet loss — ⚠️ and concealment algorithms mask modest loss surprisingly\nwell.**\n**⚠️ SIP trunking** replaced ISDN for business telephony, ⚠️ **and toll fraud on\nmisconfigured PBXs remains a live and expensive problem.**\n\n---\n\n## §11. VoLTE and VoNR\n\n**⚠️ Voice over LTE** carries voice as IP packets over the data network with QoS bearers,\n⚠️ **rather than falling back to a circuit-switched network.**\n**⚠️ The IMS core** is the architecture underneath, ⚠️ **and it is what makes voice a\nservice on the data network rather than a separate system.**\n**⚠️ The user-visible benefits**: ⚠️ **HD voice via wideband codecs (AMR-WB and EVS),\nmuch faster call setup, and simultaneous voice and data.**\n**⚠️ 2G and 3G shutdown** makes VoLTE mandatory rather than optional — ⚠️ **and this has\nstranded older handsets and, importantly, a great deal of embedded telemetry** (see a\nwireless reference §13).\n**⚠️ VoWiFi** uses the same IMS core over any internet connection, ⚠️ **which is why calls\nwork over hotel Wi-Fi with no coverage, and why emergency location becomes harder** (§27 → `comms-encryption-metadata-interoperability-and-policy`).\n\n---\n\n## §12. ⚠️ Caller ID, Spoofing and Robocalls\n\n**⚠️ Caller ID was never authenticated** — ⚠️ **the calling number is asserted by the\noriginating network and, with SIP trunking, is trivially set by the caller.**\n**⚠️ NEIGHBOUR SPOOFING** — ⚠️ **forging a number matching the recipient's prefix — exploits\nthis, and it is why answer rates for unknown numbers collapsed.**\n**⚠️ STIR\u002FSHAKEN** is the response: ⚠️ **the originating carrier cryptographically signs the\ncalling number with an attestation level (A: we know the caller and their right to the\nnumber; B: we know the customer but not the number; C: we just passed it on), and the\nterminating carrier verifies** (see a cryptography reference on certificate chains).\n> **⚠️ GOTCHA — STIR\u002FSHAKEN authenticates the CARRIER'S ASSERTION, not the caller's\n> honesty.** ⚠️ **An A-level attestation means a carrier vouched for the number, not that the\n> call is legitimate.** **⚠️ It also only works on IP-connected legs, so calls transiting\n> older segments lose the signature — which is exactly §1 → `comms-email-smtp-authentication-and-deliverability`'s weakest-participant problem.**\n\n**⚠️ It has helped and not solved**: ⚠️ **enforcement, traceback and gateway-provider\nobligations do more of the work than the cryptography does.**\n**⚠️ Branded calling** and RCS-verified sender identity (§15 → `comms-sms-rcs-signal-protocol-and-messaging-apps`) are the commercial responses to\nthe trust collapse.\n\n---\n\n# PART III — MESSAGING\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcommunication-technologies\u002Fskills\u002Fcomms-telephony-pstn-ss7-voip-and-caller-id",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-telephony-pstn-ss7-voip-and-caller-id",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill comms-telephony-pstn-ss7-voip-and-caller-id",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill comms-telephony-pstn-ss7-voip-and-caller-id","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcommunication-technologies\u002Fskills\u002Fcomms-telephony-pstn-ss7-voip-and-caller-id\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",[],[]]