[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASFHS9RCD4FQXD806VWNZJ":3,"skill-same:01M7ASFHS9RCD4FQXD806VWNZJ":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},"01M7ASFHS9RCD4FQXD806VWNZJ","tor-censorship-circumvention-and-bridges",null,"Use when reasoning about Tor under censorship — bridges, pluggable transports (obfs4, Snowflake, WebTunnel, meek, Conjure), how bridges are distributed, and how blocking actually works — or when reading a blocking-event report. Includes the 2026 Snowflake DTLS fingerprinting campaign and Iran's 2025 stealth blackout as worked cases. Covers §10. Companion to the other Tor and onion-network skills.","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\u002Ftor-and-onion-networks\u002Fskills\u002Ftor-censorship-circumvention-and-bridges\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tor-censorship-circumvention-and-bridges\ndescription: \"Use when reasoning about Tor under censorship — bridges, pluggable transports (obfs4, Snowflake, WebTunnel, meek, Conjure), how bridges are distributed, and how blocking actually works — or when reading a blocking-event report. Includes the 2026 Snowflake DTLS fingerprinting campaign and Iran's 2025 stealth blackout as worked cases. Covers §10. Companion to the other Tor and onion-network skills.\"\n---\n\n# Tor Under Censorship: Bridges, Pluggable Transports, and the Fingerprint Arms Race\n\n> **Part 4 of 8** of the *Tor and Onion Networks* reference (plugin `tor-and-onion-networks`),\n> covering §10. Sibling skills:\n> `tor-protocol-circuits-and-cell-cryptography` (§1–§5),\n> `tor-network-consensus-guards-and-paths` (§6–§7),\n> `tor-onion-services-and-hardening` (§8–§9),\n> `tor-attack-literature-and-threat-model` (§11),\n> `tor-ecosystem-alternatives-and-governance` (§12, §14–§16),\n> `tor-building-on-tor-software-patterns` (§13.1–§13.4, handbook §1),\n> `tor-running-relays-bridges-and-hardware` (§13.5, handbook §2–§6).\n> Section numbers are shared across the set; a reference written as §N → `skill` points into\n> that sibling skill.\n>\n> **⚠️ Currency: this is the fastest-rotting section of the whole reference.** Compiled\n> 16 September 2026. Transport *architecture* is stable; **which transport currently works in\n> which country is a weekly-moving target.** Check\n> [net4people\u002Fbbs](https:\u002F\u002Fgithub.com\u002Fnet4people\u002Fbbs) and the\n> [Tor forum](https:\u002F\u002Fforum.torproject.org\u002F) before advising anyone operationally.\n\n> **⚠️ Tor hides your destination by default. Hiding the *fact that you use Tor* is a\n> separate, opt-in, and permanently contested problem.**\n>\n> **⚠️ GOTCHA** boxes mark where the mental model people carry is wrong in ways that get\n> users blocked or exposed.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ TWO DISTINCT PROBLEMS: FINGERPRINTING AND ENUMERATION** (§10.1, §10.2). **A censor\n>    can block you by recognizing your *traffic* (fingerprinting) or by discovering your\n>    *bridges* (enumeration). Transports fight the first; distribution channels fight the\n>    second. A transport that solves one and not the other fails.**\n> 2. **⚠️ \"RANDOM-LOOKING\" IS NOW A FINGERPRINT** (§10.1). **obfs4's design goal — bytes\n>    with no structure — is itself detectable in an allowlist environment where everything\n>    legitimate has recognizable structure. This is why the frontier moved to *mimicry*\n>    (WebTunnel, Conjure) rather than *obfuscation*.**\n> 3. **⚠️ THE ARMS RACE IS NOW AT THE HANDSHAKE LAYER** (§10.3). **The 2026 Snowflake\n>    campaign blocked on a DTLS ClientHello signature, not on IPs. This is JA3\u002FJA4\n>    cat-and-mouse applied to circumvention, and it means library-level TLS\u002FDTLS fingerprints\n>    are a security property of your tooling.**\n\n---\n\n## §10. Censorship circumvention: bridges and pluggable transports\n\nTor's front-line war in 2025–2026 is fingerprinting and enumeration, and this is the area\nwhere \"current state\" rots fastest.\n\n**Architecture first:** **pluggable transports (PTs)** are out-of-process proxies that\nmasquerade Tor traffic as something else. The client tor talks to a local PT shim\n(`ClientTransportPlugin`), which carries an obfuscated stream to a **bridge** — an unlisted\nentry node that does not appear in the public consensus (§6.1 →\n`tor-network-consensus-guards-and-paths`). Snowflake adds volunteer proxies in front of the\nbridge.\n\n### §10.1 The transports\n\n| Transport | Camouflage | Status (Sept 2026) |\n|---|---|---|\n| **obfs4** | Random-looking encrypted bytes; passive content + active-probing resistance (bridge secret required) | Workhorse, default in Tor Browser. **Degrading** vs. China's GFW (behavioral classification, probing-driven enumeration) and vs. protocol-allowlist environments, which block \"random-looking\" by default. |\n| **Snowflake** | WebRTC (DTLS) to ephemeral volunteer proxies; rendezvous via broker over domain-front\u002FAMP-cache | Most-used transport in Iran and Russia; see §10.3 for the 2026 DTLS fingerprint war. |\n| **WebTunnel** | Genuine HTTPS\u002FWebSocket-like upgrade, co-resident with a real website on the bridge host | Deployed 2024-on; key transport for Russia; but **June 2025** saw mass bridge enumeration + blocking there — distribution moved to the Telegram bridge bot. Integrated into Tor VPN beta ≥ 1.4.0. |\n| **meek** | Domain fronting through CDN | Effectively vestigial since the 2018–2019 CDN fronting shutdowns (Google\u002FAWS\u002FAzure); fronting survives only inside Snowflake's broker rendezvous. |\n| **Conjure** | Refraction networking: connect to *unused* ISP address space, partner routers detour you | In staging\u002Fpre-rollout integration with Tor as of the Dec 2025 anti-censorship roadmap post; new DNS\u002FAMP-cache registration paths. |\n\n### §10.2 Bridge distribution channels\n\nBridgeDB (HTTPS + email), the in-browser **moat** API (fronted, inside Tor Browser's\nconnection assist), and since 2024–2025 the **Telegram distribution bot**, which became\ncrucial when Russia enumerated WebTunnel bridges in June 2025.\n\n> **⚠️ GOTCHA:** bridge *secrecy* is the resource under attack, not bridge *capacity*. A\n> distribution channel that hands out bridges efficiently to real users also hands them out\n> efficiently to a censor who enrolls as a user. Every distribution design is a rate-limiting\n> and identity-cost trade, which is why they keep changing.\n\n### §10.3 Case study: the Snowflake DTLS war (Dec 2025 – Apr 2026)\n\nRussia's TSPU began **fingerprint-based blocking of Snowflake on 30 March 2026** — detecting\nthe `pion\u002Fdtls` ClientHello by JA3\u002FJA4 signature after a short delay, rather than blocking IPs.\nConnection success collapsed overnight; broker domains stayed reachable.\n\nMitigations: the **covert-dtls** library (randomized\u002Fmimicked ClientHellos) shipped by default\nin standalone snowflake-proxy v2.13.1; browser-extension proxies on DTLS 1.3 survived; and\nwork continued to push covert-dtls into IPtProxy (the transport stack used by Orbot). By late\nApril 2026 censors were expanding fingerprint coverage (adding a Firefox-DTLS-1.2-mimic\nsignature) — an explicit arms race in *handshake fingerprinting*, paralleling the web's\nJA3\u002FJA4 cat-and-mouse.\n\n*(Sources: net4people\u002Fbbs #603; Tor Forum Snowflake Daily Operations threads, March & July\n2026.)*\n\n### §10.4 Case study: Iran's \"stealth blackout\" (June 2025)\n\nDuring the June 13–25, 2025 Iran–Israel war, Iran ran a DPI\u002FDNS-poisoning\u002Fprotocol-allowlist\nshutdown **without fully withdrawing BGP**. Direct Tor died June 13; **bridge usage surged**;\nSnowflake proxies were overwhelmed and users shifted to obfs4; during the total-blackout days\n(June 18–21) nearly nothing worked. Usage rebounded *above* pre-war levels after June 25.\n\nLessons absorbed: keep multiple transports warm, expect TCP-kill\u002FUDP-pass asymmetry, and\nexpect proxy-pool exhaustion — Snowflake's volunteer pool is now a scaling priority\n(Manifest-V3 extension update, NAT-check improvements, staging stress-test infrastructure). A\nfurther multi-day Iranian shutdown began **28 Feb 2026** per the Tor Metrics events feed.\n\n---\n\n## Where to go next\n\n- Bridges as network actors, and how they differ from listed relays: §6.1 →\n  `tor-network-consensus-guards-and-paths`.\n- Website fingerprinting — the *other* fingerprinting problem, at the guard rather than the\n  censor: §11.2 → `tor-attack-literature-and-threat-model`.\n- Running a bridge, and the `ClientTransportPlugin` configuration: §13.5 →\n  `tor-running-relays-bridges-and-hardware`.\n- Tor VPN, Orbot and the transports' place in the 2026 client stack: §12.2 →\n  `tor-ecosystem-alternatives-and-governance`.\n","# Tor Under Censorship: Bridges, Pluggable Transports, and the Fingerprint Arms Race\n\n> **Part 4 of 8** of the *Tor and Onion Networks* reference (plugin `tor-and-onion-networks`),\n> covering §10. Sibling skills:\n> `tor-protocol-circuits-and-cell-cryptography` (§1–§5),\n> `tor-network-consensus-guards-and-paths` (§6–§7),\n> `tor-onion-services-and-hardening` (§8–§9),\n> `tor-attack-literature-and-threat-model` (§11),\n> `tor-ecosystem-alternatives-and-governance` (§12, §14–§16),\n> `tor-building-on-tor-software-patterns` (§13.1–§13.4, handbook §1),\n> `tor-running-relays-bridges-and-hardware` (§13.5, handbook §2–§6).\n> Section numbers are shared across the set; a reference written as §N → `skill` points into\n> that sibling skill.\n>\n> **⚠️ Currency: this is the fastest-rotting section of the whole reference.** Compiled\n> 16 September 2026. Transport *architecture* is stable; **which transport currently works in\n> which country is a weekly-moving target.** Check\n> [net4people\u002Fbbs](https:\u002F\u002Fgithub.com\u002Fnet4people\u002Fbbs) and the\n> [Tor forum](https:\u002F\u002Fforum.torproject.org\u002F) before advising anyone operationally.\n\n> **⚠️ Tor hides your destination by default. Hiding the *fact that you use Tor* is a\n> separate, opt-in, and permanently contested problem.**\n>\n> **⚠️ GOTCHA** boxes mark where the mental model people carry is wrong in ways that get\n> users blocked or exposed.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ TWO DISTINCT PROBLEMS: FINGERPRINTING AND ENUMERATION** (§10.1, §10.2). **A censor\n>    can block you by recognizing your *traffic* (fingerprinting) or by discovering your\n>    *bridges* (enumeration). Transports fight the first; distribution channels fight the\n>    second. A transport that solves one and not the other fails.**\n> 2. **⚠️ \"RANDOM-LOOKING\" IS NOW A FINGERPRINT** (§10.1). **obfs4's design goal — bytes\n>    with no structure — is itself detectable in an allowlist environment where everything\n>    legitimate has recognizable structure. This is why the frontier moved to *mimicry*\n>    (WebTunnel, Conjure) rather than *obfuscation*.**\n> 3. **⚠️ THE ARMS RACE IS NOW AT THE HANDSHAKE LAYER** (§10.3). **The 2026 Snowflake\n>    campaign blocked on a DTLS ClientHello signature, not on IPs. This is JA3\u002FJA4\n>    cat-and-mouse applied to circumvention, and it means library-level TLS\u002FDTLS fingerprints\n>    are a security property of your tooling.**\n\n---\n\n## §10. Censorship circumvention: bridges and pluggable transports\n\nTor's front-line war in 2025–2026 is fingerprinting and enumeration, and this is the area\nwhere \"current state\" rots fastest.\n\n**Architecture first:** **pluggable transports (PTs)** are out-of-process proxies that\nmasquerade Tor traffic as something else. The client tor talks to a local PT shim\n(`ClientTransportPlugin`), which carries an obfuscated stream to a **bridge** — an unlisted\nentry node that does not appear in the public consensus (§6.1 →\n`tor-network-consensus-guards-and-paths`). Snowflake adds volunteer proxies in front of the\nbridge.\n\n### §10.1 The transports\n\n| Transport | Camouflage | Status (Sept 2026) |\n|---|---|---|\n| **obfs4** | Random-looking encrypted bytes; passive content + active-probing resistance (bridge secret required) | Workhorse, default in Tor Browser. **Degrading** vs. China's GFW (behavioral classification, probing-driven enumeration) and vs. protocol-allowlist environments, which block \"random-looking\" by default. |\n| **Snowflake** | WebRTC (DTLS) to ephemeral volunteer proxies; rendezvous via broker over domain-front\u002FAMP-cache | Most-used transport in Iran and Russia; see §10.3 for the 2026 DTLS fingerprint war. |\n| **WebTunnel** | Genuine HTTPS\u002FWebSocket-like upgrade, co-resident with a real website on the bridge host | Deployed 2024-on; key transport for Russia; but **June 2025** saw mass bridge enumeration + blocking there — distribution moved to the Telegram bridge bot. Integrated into Tor VPN beta ≥ 1.4.0. |\n| **meek** | Domain fronting through CDN | Effectively vestigial since the 2018–2019 CDN fronting shutdowns (Google\u002FAWS\u002FAzure); fronting survives only inside Snowflake's broker rendezvous. |\n| **Conjure** | Refraction networking: connect to *unused* ISP address space, partner routers detour you | In staging\u002Fpre-rollout integration with Tor as of the Dec 2025 anti-censorship roadmap post; new DNS\u002FAMP-cache registration paths. |\n\n### §10.2 Bridge distribution channels\n\nBridgeDB (HTTPS + email), the in-browser **moat** API (fronted, inside Tor Browser's\nconnection assist), and since 2024–2025 the **Telegram distribution bot**, which became\ncrucial when Russia enumerated WebTunnel bridges in June 2025.\n\n> **⚠️ GOTCHA:** bridge *secrecy* is the resource under attack, not bridge *capacity*. A\n> distribution channel that hands out bridges efficiently to real users also hands them out\n> efficiently to a censor who enrolls as a user. Every distribution design is a rate-limiting\n> and identity-cost trade, which is why they keep changing.\n\n### §10.3 Case study: the Snowflake DTLS war (Dec 2025 – Apr 2026)\n\nRussia's TSPU began **fingerprint-based blocking of Snowflake on 30 March 2026** — detecting\nthe `pion\u002Fdtls` ClientHello by JA3\u002FJA4 signature after a short delay, rather than blocking IPs.\nConnection success collapsed overnight; broker domains stayed reachable.\n\nMitigations: the **covert-dtls** library (randomized\u002Fmimicked ClientHellos) shipped by default\nin standalone snowflake-proxy v2.13.1; browser-extension proxies on DTLS 1.3 survived; and\nwork continued to push covert-dtls into IPtProxy (the transport stack used by Orbot). By late\nApril 2026 censors were expanding fingerprint coverage (adding a Firefox-DTLS-1.2-mimic\nsignature) — an explicit arms race in *handshake fingerprinting*, paralleling the web's\nJA3\u002FJA4 cat-and-mouse.\n\n*(Sources: net4people\u002Fbbs #603; Tor Forum Snowflake Daily Operations threads, March & July\n2026.)*\n\n### §10.4 Case study: Iran's \"stealth blackout\" (June 2025)\n\nDuring the June 13–25, 2025 Iran–Israel war, Iran ran a DPI\u002FDNS-poisoning\u002Fprotocol-allowlist\nshutdown **without fully withdrawing BGP**. Direct Tor died June 13; **bridge usage surged**;\nSnowflake proxies were overwhelmed and users shifted to obfs4; during the total-blackout days\n(June 18–21) nearly nothing worked. Usage rebounded *above* pre-war levels after June 25.\n\nLessons absorbed: keep multiple transports warm, expect TCP-kill\u002FUDP-pass asymmetry, and\nexpect proxy-pool exhaustion — Snowflake's volunteer pool is now a scaling priority\n(Manifest-V3 extension update, NAT-check improvements, staging stress-test infrastructure). A\nfurther multi-day Iranian shutdown began **28 Feb 2026** per the Tor Metrics events feed.\n\n---\n\n## Where to go next\n\n- Bridges as network actors, and how they differ from listed relays: §6.1 →\n  `tor-network-consensus-guards-and-paths`.\n- Website fingerprinting — the *other* fingerprinting problem, at the guard rather than the\n  censor: §11.2 → `tor-attack-literature-and-threat-model`.\n- Running a bridge, and the `ClientTransportPlugin` configuration: §13.5 →\n  `tor-running-relays-bridges-and-hardware`.\n- Tor VPN, Orbot and the transports' place in the 2026 client stack: §12.2 →\n  `tor-ecosystem-alternatives-and-governance`.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Ftor-and-onion-networks\u002Fskills\u002Ftor-censorship-circumvention-and-bridges",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 tor-censorship-circumvention-and-bridges",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill tor-censorship-circumvention-and-bridges",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill tor-censorship-circumvention-and-bridges","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Ftor-and-onion-networks\u002Fskills\u002Ftor-censorship-circumvention-and-bridges\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",[],[]]