AGENT SKILL

social-media-analytics-privacy-and-presence

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/B 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.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 5
Forks
3

01 前言 Front Matter

name
social-media-analytics-privacy-and-presence
description
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/B 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.

03 SKILL.md 正文

Social Media Engineering: Media Handling, Analytics, Privacy, and Your Own Presence

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.

Currency: Verified August 2026. See §16 → social-reference for the currency snapshot and what goes stale first.

How to read this. The title spans two things and this document covers both, weighted 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; §13 is about your own presence as a developer. Skip to §13 if that's what you came for.

Three markers:

  • [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.
  • [VERSIONED] — platform terms, pricing, protocols, regulation. ⚠️ Verify all of it; this is the fastest-moving material in the collection after AI.
  • [CONTESTED] — genuine disagreement.

⚠️ GOTCHA boxes mark what breaks, gets you banned, or gets you fined.

The three framings that organize everything below:

  1. ⚠️ Building on a platform API is building on rented land, and the rent changed. The 2023–2026 period established that platforms will reprice or withdraw access with weeks of notice and no obligation. Architect for that from day one (§1 → social-platform-apis-and-open-protocols).
  2. The hard problems are social, not technical. Fan-out and ranking are solved engineering; moderation, abuse, and incentive design are not, and they scale worse than your database does (§7 → social-moderation-abuse-and-regulation, §8 → social-moderation-abuse-and-regulation).
  3. ⚠️ Compliance is now an architecture input, not a legal afterthought. Age assurance, transparency reporting, and appeals mechanisms have to be designed in — and regulators have started saying explicitly that self-declaration is not sufficient (§9 → social-moderation-abuse-and-regulation).

§10. Media Handling

[DURABLE] Uploads are an attack surface as much as a feature. Validate server-side, always — ⚠️ never trust the client's content type or extension; sniff the actual bytes. Transcode rather than serve originals (⚠️ which also strips a large class of embedded exploits), strip EXIF (⚠️ GPS coordinates in uploaded photos are a real and recurring privacy incident), generate multiple sizes, serve via CDN with signed URLs where privacy matters, and run hash-matching against known violating content before publication (§7 → social-moderation-abuse-and-regulation).

⚠️ The specific hazards: decompression bombs (a small file that expands to gigabytes — cap dimensions and pixel count before decoding), SVG containing script (⚠️ never serve user SVG from your own origin), polyglot files valid as two types, and video that's expensive to transcode — rate-limit by cost, not by file count.

For everything downstream of that — codecs, packaging, delivery — see a media-engineering reference.


§11. Analytics and Experimentation

Metrics that matter: DAU/MAU and the ratio (⚠️ stickiness), retention curves by cohort, time-to-value for new users, creation rate versus consumption rate (⚠️ the creator-to-lurker ratio determines whether the network survives), and network density — which predicts retention better than raw user count.

⚠️ The metric trap that defines this industry: engagement is easy to measure and easy to increase in ways that make the product worse. Time-spent and session count reward compulsion; counter-metrics — reported content rate, user-reported satisfaction, churn after high-engagement sessions — are the honest correction, and they're harder to get funded.

Experimentation: A/B testing with proper sequential-analysis or fixed-horizon discipline, ⚠️ network effects break the independence assumption that A/B testing rests on (a treated user affects control users — cluster or ego-network randomization is the mitigation), and long-run holdouts for effects that don't show up in a two-week test.


§12. Privacy and Data

[DURABLE] Data minimization (⚠️ the data you didn't collect can't leak, be subpoenaed, or be repriced by a regulator), purpose limitation, retention limits with actual enforcement, and ⚠️ deletion that genuinely propagates — through timelines that were fanned out (§3 → social-feed-graph-ranking-and-notifications), caches, CDNs, search indexes, backups, and analytics warehouses. Most "deleted" content in social systems is not deleted everywhere, and that is both a legal and an ethical problem.

Rights infrastructure you'll need: data export (GDPR portability), deletion requests, access requests, and ⚠️ the "what about content others created that mentions you" question, which has no clean answer.

And the specific social-media hazards: ⚠️ inference risk — the social graph reveals things users never disclosed (a person's connections can reveal orientation, health status, or political affiliation they never stated); location leakage via EXIF (§10), check-ins, and timing; and cross-platform correlation by third parties.


§13. Your Own Presence as a Developer

[DURABLE, and deliberately short, because most advice here is self-serving.]

⚠️ The honest framing first: you do not need a social media presence to be a good or successful engineer, and a lot of "personal brand" advice is written by people whose business is personal branding. What a presence genuinely buys you: serendipity. People who know what you work on will send you opportunities. That's the mechanism, and it's real — but it's a slow, compounding effect, not a growth hack.

What actually works, as far as anything does:

  • ⚠️ Write things down where they're findable. A blog post you own beats a thread on a platform that may reprice, restrict, or disappear (§1 → social-platform-apis-and-open-protocols). Post on your own site, then syndicate.
  • Be useful about a narrow thing. Depth attracts the people you want; breadth attracts nobody in particular.
  • Show work in progress, not just polished results.
  • Answer questions in public — the answer helps one person and is found by hundreds.
  • ⚠️ Consistency beats volume. Occasional and sustained beats a burst and silence.

⚠️ The costs, which the advice usually omits:

  • The engagement mechanics that maximize reach are the ones that degrade discourse, and optimizing for them changes what you write and eventually how you think.
  • Visibility attracts harassment, and it is not evenly distributed — ⚠️ the cost is far higher for women, people of colour, and anyone from a marginalized group, and advice that ignores this is advice from someone who hasn't paid it.
  • It is a genuine time sink with poorly-attributable returns.
  • ⚠️ Employer social media policies exist, opinions get read as employer positions, and a bad hour can outlive a good decade.

Practical hygiene: separate professional and personal accounts if you want either to be honest; assume everything is permanent and public, including deleted posts; turn off notifications (⚠️ the single highest-value change most people can make); block and mute liberally and without guilt; and know that platform choice is now partly a values question — which is why §2 → social-platform-apis-and-open-protocols exists.

[DURABLE] The genuinely underrated alternative: contributing to open source, writing documentation, answering on Stack Overflow, speaking at a local meetup, and mentoring produce most of the same serendipity with none of §13's costs. They are slower and they don't feel like marketing, which is probably why they're underrated.

04 同仓库更多 Skills

the-vibey-project
the-vibey-project/vibey

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.

★ 5
the-vibey-project
the-vibey-project/vibey

prose-technical-mechanics

Use when editing or writing prose at a technical/mechanical 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.

★ 5
the-vibey-project
the-vibey-project/vibey

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/Jamesian, 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.

★ 5
the-vibey-project
the-vibey-project/vibey

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/pitch/presentation" request.

★ 5
the-vibey-project
the-vibey-project/vibey

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/neurodivergent 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.

★ 5
the-vibey-project
the-vibey-project/vibey

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/paper.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.

★ 5