[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS7PH534AMSJ2BG964JEDY":3,"skill-same:01M7AS7PH534AMSJ2BG964JEDY":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},"01M7AS7PH534AMSJ2BG964JEDY","social-media-analytics-privacy-and-presence",null,"Use when handling uploads, measurement, personal data, or your own developer presence: media handling (upload pipelines, transcoding, thumbnails, CDN delivery), analytics and experimentation including A\u002FB testing and metric design, privacy and data (retention, deletion, export, and the regulatory obligations), and the practical question of a developer's own social presence and how to sustain it without it eating your life.","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\u002Fsocial-media-engineering\u002Fskills\u002Fsocial-media-analytics-privacy-and-presence\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: social-media-analytics-privacy-and-presence\ndescription: \"Use when handling uploads, measurement, personal data, or your own developer presence: media handling (upload pipelines, transcoding, thumbnails, CDN delivery), analytics and experimentation including A\u002FB testing and metric design, privacy and data (retention, deletion, export, and the regulatory obligations), and the practical question of a developer's own social presence and how to sustain it without it eating your life.\"\n---\n\n# Social Media Engineering: Media Handling, Analytics, Privacy, and Your Own Presence\n\n> **Part 4 of 5** of the *Social Media Engineering* reference (plugin `social-media-engineering`), covering §10–§13. Sibling skills: `social-platform-apis-and-open-protocols` (§0–§2), `social-feed-graph-ranking-and-notifications` (§3–§6), `social-moderation-abuse-and-regulation` (§7–§9), `social-reference` (§14–§19). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §16 → `social-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** The title spans two things and this document covers both, weighted\n> toward the first: **§1–§12 → `social-platform-apis-and-open-protocols`, `social-feed-graph-ranking-and-notifications`, `social-moderation-abuse-and-regulation` are about building and integrating with social systems;\n> §13 is about your own presence as a developer.** Skip to §13 if that's what you came for.\n>\n> Three markers:\n> - **[DURABLE]** — architecture, ranking, moderation, and abuse dynamics. Most of §2–§10 → `social-platform-apis-and-open-protocols`, `social-feed-graph-ranking-and-notifications`, `social-moderation-abuse-and-regulation`.\n> - **[VERSIONED]** — platform terms, pricing, protocols, regulation. ⚠️ **Verify all of\n>   it; this is the fastest-moving material in the collection after AI.**\n> - **[CONTESTED]** — genuine disagreement.\n>\n> **⚠️ GOTCHA** boxes mark what breaks, gets you banned, or gets you fined.\n>\n> **The three framings that organize everything below:**\n> 1. **⚠️ Building on a platform API is building on rented land, and the rent changed.**\n>    The 2023–2026 period established that platforms will reprice or withdraw access with\n>    weeks of notice and no obligation. **Architect for that from day one** (§1 → `social-platform-apis-and-open-protocols`).\n> 2. **The hard problems are social, not technical.** Fan-out and ranking are solved\n>    engineering; **moderation, abuse, and incentive design are not, and they scale\n>    worse than your database does** (§7 → `social-moderation-abuse-and-regulation`, §8 → `social-moderation-abuse-and-regulation`).\n> 3. **⚠️ Compliance is now an architecture input, not a legal afterthought.** Age\n>    assurance, transparency reporting, and appeals mechanisms have to be designed in —\n>    **and regulators have started saying explicitly that self-declaration is not\n>    sufficient** (§9 → `social-moderation-abuse-and-regulation`).\n\n---\n\n## §10. Media Handling\n\n**[DURABLE] Uploads are an attack surface as much as a feature.**\n**Validate server-side, always** — ⚠️ **never trust the client's content type or extension;\nsniff the actual bytes.** **Transcode rather than serve originals** (⚠️ **which also\nstrips a large class of embedded exploits**), **strip EXIF** (⚠️ **GPS coordinates in\nuploaded photos are a real and recurring privacy incident**), generate multiple sizes,\nserve via CDN with signed URLs where privacy matters, and **run hash-matching against known\nviolating content before publication** (§7 → `social-moderation-abuse-and-regulation`).\n\n**⚠️ The specific hazards**: **decompression bombs** (a small file that expands to\ngigabytes — cap dimensions and pixel count before decoding), **SVG containing script**\n(⚠️ **never serve user SVG from your own origin**), **polyglot files** valid as two types,\n**and video that's expensive to transcode** — rate-limit by cost, not by file count.\n\nFor everything downstream of that — codecs, packaging, delivery — see a media-engineering\nreference.\n\n---\n\n## §11. Analytics and Experimentation\n\n**Metrics that matter**: DAU\u002FMAU and the ratio (⚠️ **stickiness**), retention curves by\ncohort, time-to-value for new users, creation rate versus consumption rate\n(⚠️ **the creator-to-lurker ratio determines whether the network survives**), and\n**network density** — which predicts retention better than raw user count.\n\n**⚠️ The metric trap that defines this industry**: **engagement is easy to measure and easy\nto increase in ways that make the product worse.** Time-spent and session count reward\ncompulsion; **counter-metrics — reported content rate, user-reported satisfaction, churn\nafter high-engagement sessions — are the honest correction, and they're harder to get\nfunded.**\n\n**Experimentation**: A\u002FB testing with proper sequential-analysis or fixed-horizon\ndiscipline, ⚠️ **network effects break the independence assumption that A\u002FB testing rests\non** (a treated user affects control users — **cluster or ego-network randomization is the\nmitigation**), and **long-run holdouts** for effects that don't show up in a two-week test.\n\n---\n\n## §12. Privacy and Data\n\n**[DURABLE]** **Data minimization** (⚠️ **the data you didn't collect can't leak, be\nsubpoenaed, or be repriced by a regulator**), **purpose limitation**, **retention limits\nwith actual enforcement**, and **⚠️ deletion that genuinely propagates** — through\ntimelines that were fanned out (§3 → `social-feed-graph-ranking-and-notifications`), caches, CDNs, search indexes, backups, and analytics\nwarehouses. **Most \"deleted\" content in social systems is not deleted everywhere, and that\nis both a legal and an ethical problem.**\n\n**Rights infrastructure you'll need**: **data export** (GDPR portability), **deletion\nrequests**, **access requests**, and **⚠️ the \"what about content others created that\nmentions you\" question**, which has no clean answer.\n\n**And the specific social-media hazards**: **⚠️ inference risk** — the social graph reveals\nthings users never disclosed (a person's connections can reveal orientation, health status,\nor political affiliation they never stated); **location leakage** via EXIF (§10),\ncheck-ins, and timing; **and cross-platform correlation** by third parties.\n\n---\n\n## §13. Your Own Presence as a Developer\n\n**[DURABLE, and deliberately short, because most advice here is self-serving.]**\n\n**⚠️ The honest framing first: you do not need a social media presence to be a good or\nsuccessful engineer**, and a lot of \"personal brand\" advice is written by people whose\nbusiness is personal branding. **What a presence genuinely buys you: serendipity.** People\nwho know what you work on will send you opportunities. That's the mechanism, and it's\nreal — but it's a slow, compounding effect, not a growth hack.\n\n**What actually works, as far as anything does:**\n- **⚠️ Write things down where they're findable.** A blog post you own beats a thread on a\n  platform that may reprice, restrict, or disappear (§1 → `social-platform-apis-and-open-protocols`). **Post on your own site, then\n  syndicate.**\n- **Be useful about a narrow thing.** Depth attracts the people you want; breadth attracts\n  nobody in particular.\n- **Show work in progress**, not just polished results.\n- **Answer questions in public** — the answer helps one person and is found by hundreds.\n- **⚠️ Consistency beats volume.** Occasional and sustained beats a burst and silence.\n\n**⚠️ The costs, which the advice usually omits:**\n- **The engagement mechanics that maximize reach are the ones that degrade discourse**, and\n  optimizing for them changes what you write and eventually how you think.\n- **Visibility attracts harassment**, and it is not evenly distributed — ⚠️ **the cost is\n  far higher for women, people of colour, and anyone from a marginalized group**, and\n  advice that ignores this is advice from someone who hasn't paid it.\n- **It is a genuine time sink** with poorly-attributable returns.\n- **⚠️ Employer social media policies exist**, opinions get read as employer positions, and\n  a bad hour can outlive a good decade.\n\n**Practical hygiene**: **separate professional and personal accounts** if you want either\nto be honest; **assume everything is permanent and public**, including deleted posts;\n**turn off notifications** (⚠️ **the single highest-value change most people can make**);\n**block and mute liberally and without guilt**; **and know that platform choice is now\npartly a values question** — which is why §2 → `social-platform-apis-and-open-protocols` exists.\n\n**[DURABLE] The genuinely underrated alternative**: **contributing to open source, writing\ndocumentation, answering on Stack Overflow, speaking at a local meetup, and mentoring\nproduce most of the same serendipity with none of §13's costs.** They are slower and they\ndon't feel like marketing, which is probably why they're underrated.\n","# Social Media Engineering: Media Handling, Analytics, Privacy, and Your Own Presence\n\n> **Part 4 of 5** of the *Social Media Engineering* reference (plugin `social-media-engineering`), covering §10–§13. Sibling skills: `social-platform-apis-and-open-protocols` (§0–§2), `social-feed-graph-ranking-and-notifications` (§3–§6), `social-moderation-abuse-and-regulation` (§7–§9), `social-reference` (§14–§19). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §16 → `social-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** The title spans two things and this document covers both, weighted\n> toward the first: **§1–§12 → `social-platform-apis-and-open-protocols`, `social-feed-graph-ranking-and-notifications`, `social-moderation-abuse-and-regulation` are about building and integrating with social systems;\n> §13 is about your own presence as a developer.** Skip to §13 if that's what you came for.\n>\n> Three markers:\n> - **[DURABLE]** — architecture, ranking, moderation, and abuse dynamics. Most of §2–§10 → `social-platform-apis-and-open-protocols`, `social-feed-graph-ranking-and-notifications`, `social-moderation-abuse-and-regulation`.\n> - **[VERSIONED]** — platform terms, pricing, protocols, regulation. ⚠️ **Verify all of\n>   it; this is the fastest-moving material in the collection after AI.**\n> - **[CONTESTED]** — genuine disagreement.\n>\n> **⚠️ GOTCHA** boxes mark what breaks, gets you banned, or gets you fined.\n>\n> **The three framings that organize everything below:**\n> 1. **⚠️ Building on a platform API is building on rented land, and the rent changed.**\n>    The 2023–2026 period established that platforms will reprice or withdraw access with\n>    weeks of notice and no obligation. **Architect for that from day one** (§1 → `social-platform-apis-and-open-protocols`).\n> 2. **The hard problems are social, not technical.** Fan-out and ranking are solved\n>    engineering; **moderation, abuse, and incentive design are not, and they scale\n>    worse than your database does** (§7 → `social-moderation-abuse-and-regulation`, §8 → `social-moderation-abuse-and-regulation`).\n> 3. **⚠️ Compliance is now an architecture input, not a legal afterthought.** Age\n>    assurance, transparency reporting, and appeals mechanisms have to be designed in —\n>    **and regulators have started saying explicitly that self-declaration is not\n>    sufficient** (§9 → `social-moderation-abuse-and-regulation`).\n\n---\n\n## §10. Media Handling\n\n**[DURABLE] Uploads are an attack surface as much as a feature.**\n**Validate server-side, always** — ⚠️ **never trust the client's content type or extension;\nsniff the actual bytes.** **Transcode rather than serve originals** (⚠️ **which also\nstrips a large class of embedded exploits**), **strip EXIF** (⚠️ **GPS coordinates in\nuploaded photos are a real and recurring privacy incident**), generate multiple sizes,\nserve via CDN with signed URLs where privacy matters, and **run hash-matching against known\nviolating content before publication** (§7 → `social-moderation-abuse-and-regulation`).\n\n**⚠️ The specific hazards**: **decompression bombs** (a small file that expands to\ngigabytes — cap dimensions and pixel count before decoding), **SVG containing script**\n(⚠️ **never serve user SVG from your own origin**), **polyglot files** valid as two types,\n**and video that's expensive to transcode** — rate-limit by cost, not by file count.\n\nFor everything downstream of that — codecs, packaging, delivery — see a media-engineering\nreference.\n\n---\n\n## §11. Analytics and Experimentation\n\n**Metrics that matter**: DAU\u002FMAU and the ratio (⚠️ **stickiness**), retention curves by\ncohort, time-to-value for new users, creation rate versus consumption rate\n(⚠️ **the creator-to-lurker ratio determines whether the network survives**), and\n**network density** — which predicts retention better than raw user count.\n\n**⚠️ The metric trap that defines this industry**: **engagement is easy to measure and easy\nto increase in ways that make the product worse.** Time-spent and session count reward\ncompulsion; **counter-metrics — reported content rate, user-reported satisfaction, churn\nafter high-engagement sessions — are the honest correction, and they're harder to get\nfunded.**\n\n**Experimentation**: A\u002FB testing with proper sequential-analysis or fixed-horizon\ndiscipline, ⚠️ **network effects break the independence assumption that A\u002FB testing rests\non** (a treated user affects control users — **cluster or ego-network randomization is the\nmitigation**), and **long-run holdouts** for effects that don't show up in a two-week test.\n\n---\n\n## §12. Privacy and Data\n\n**[DURABLE]** **Data minimization** (⚠️ **the data you didn't collect can't leak, be\nsubpoenaed, or be repriced by a regulator**), **purpose limitation**, **retention limits\nwith actual enforcement**, and **⚠️ deletion that genuinely propagates** — through\ntimelines that were fanned out (§3 → `social-feed-graph-ranking-and-notifications`), caches, CDNs, search indexes, backups, and analytics\nwarehouses. **Most \"deleted\" content in social systems is not deleted everywhere, and that\nis both a legal and an ethical problem.**\n\n**Rights infrastructure you'll need**: **data export** (GDPR portability), **deletion\nrequests**, **access requests**, and **⚠️ the \"what about content others created that\nmentions you\" question**, which has no clean answer.\n\n**And the specific social-media hazards**: **⚠️ inference risk** — the social graph reveals\nthings users never disclosed (a person's connections can reveal orientation, health status,\nor political affiliation they never stated); **location leakage** via EXIF (§10),\ncheck-ins, and timing; **and cross-platform correlation** by third parties.\n\n---\n\n## §13. Your Own Presence as a Developer\n\n**[DURABLE, and deliberately short, because most advice here is self-serving.]**\n\n**⚠️ The honest framing first: you do not need a social media presence to be a good or\nsuccessful engineer**, and a lot of \"personal brand\" advice is written by people whose\nbusiness is personal branding. **What a presence genuinely buys you: serendipity.** People\nwho know what you work on will send you opportunities. That's the mechanism, and it's\nreal — but it's a slow, compounding effect, not a growth hack.\n\n**What actually works, as far as anything does:**\n- **⚠️ Write things down where they're findable.** A blog post you own beats a thread on a\n  platform that may reprice, restrict, or disappear (§1 → `social-platform-apis-and-open-protocols`). **Post on your own site, then\n  syndicate.**\n- **Be useful about a narrow thing.** Depth attracts the people you want; breadth attracts\n  nobody in particular.\n- **Show work in progress**, not just polished results.\n- **Answer questions in public** — the answer helps one person and is found by hundreds.\n- **⚠️ Consistency beats volume.** Occasional and sustained beats a burst and silence.\n\n**⚠️ The costs, which the advice usually omits:**\n- **The engagement mechanics that maximize reach are the ones that degrade discourse**, and\n  optimizing for them changes what you write and eventually how you think.\n- **Visibility attracts harassment**, and it is not evenly distributed — ⚠️ **the cost is\n  far higher for women, people of colour, and anyone from a marginalized group**, and\n  advice that ignores this is advice from someone who hasn't paid it.\n- **It is a genuine time sink** with poorly-attributable returns.\n- **⚠️ Employer social media policies exist**, opinions get read as employer positions, and\n  a bad hour can outlive a good decade.\n\n**Practical hygiene**: **separate professional and personal accounts** if you want either\nto be honest; **assume everything is permanent and public**, including deleted posts;\n**turn off notifications** (⚠️ **the single highest-value change most people can make**);\n**block and mute liberally and without guilt**; **and know that platform choice is now\npartly a values question** — which is why §2 → `social-platform-apis-and-open-protocols` exists.\n\n**[DURABLE] The genuinely underrated alternative**: **contributing to open source, writing\ndocumentation, answering on Stack Overflow, speaking at a local meetup, and mentoring\nproduce most of the same serendipity with none of §13's costs.** They are slower and they\ndon't feel like marketing, which is probably why they're underrated.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fsocial-media-engineering\u002Fskills\u002Fsocial-media-analytics-privacy-and-presence",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 social-media-analytics-privacy-and-presence",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill social-media-analytics-privacy-and-presence",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill social-media-analytics-privacy-and-presence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fsocial-media-engineering\u002Fskills\u002Fsocial-media-analytics-privacy-and-presence\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",[],[]]