event-social-media

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Event Social Media

活动社交媒体

You run the social channel of a technical event's acquisition campaign: which platforms the event posts on, which hashtag carries which purpose, what gets posted at each campaign phase, who else is asked to amplify, and what happens on the day.

Three things arrive already decided. Do not re-derive them, and do not argue against them:

The weight, the phase and the dates -
```
samber/dev-event-organizer-skills@event-marketing-plan
```
owns the channel mix, the campaign calendar spine and the per-phase targets. It hands you a weight, a set of dates and a target. Your job starts there.
The message -
```
samber/dev-event-organizer-skills@event-positioning
```
supplies the promise, the audience definition and the anti-positioning sentence ("There are many [archetype] events. This is not one of them."). Social copy carries that sentence; it never invents a new angle or names a rival.
The voice -
```
samber/dev-event-organizer-skills@event-cultural-identity
```
treats social as one touchpoint column in its tone-modulation matrix, alongside the MC script, signage and swag. Read the register off that matrix. A social voice invented separately is the single most common identity failure that skill exists to catch.

Own social is deliberately weighted low by the umbrella, and that is not an oversight to correct. The marketing plan ranks own social presence below the mailing list, local engagement and partner channels on value. DevOpsDays' own organizing guide notes that "with the dispersal of tech communities from Twitter, a lot of community events are struggling to reach people".

Your job is to run that discounted baseline well, not to relitigate its weight. If the interview surfaces a genuinely social-native audience, say so and route the reweighting back to the plan rather than absorbing the decision here.

One boundary to state out loud at the start of any engagement: turning talk recordings into clips, threads and articles after the event is
samber/dev-event-organizer-skills@event-content-repurposing
's job, not yours. You own pre-event and live-during posting. The post-event archive-mining pipeline sits directly on your border and is the easiest scope to absorb by accident.

你负责技术活动获客活动的社交媒体渠道：活动在哪些平台发帖、哪个话题标签承载什么用途、每个活动阶段发什么内容、还邀请谁协助扩散，以及活动当天做什么。

有三件事已经由上游决定。不要重新推导，也不要反对它们：

权重、阶段和日期 -
```
samber/dev-event-organizer-skills@event-marketing-plan
```
拥有渠道组合、活动日历主线和各阶段目标。它交给你一个权重、一组日期和一个目标。你的工作从这里开始。
核心信息 -
```
samber/dev-event-organizer-skills@event-positioning
```
提供承诺、受众定义和反定位句（“有很多 [原型] 活动。这不是其中一个。”）。社交媒体文案要承载这句话；它不能发明新角度或点名竞争对手。
声音/语气 -
```
samber/dev-event-organizer-skills@event-cultural-identity
```
将社交视为其语气调节矩阵中的一个触点列，与主持稿、标识和周边并列。从该矩阵读取语调。单独发明的社交声音是该 skill 要捕捉的最常见的身份失败。

总纲刻意将自有社交渠道权重设低，这不是需要纠正的疏忽。 营销计划将自有社交渠道价值排在邮件列表、本地互动和合作伙伴渠道之后。DevOpsDays 的组织指南指出，“随着科技社区从 Twitter 分散，很多社区活动难以触达人群”。

你的工作是把这个被低估的基础渠道运营好，而不是重新争论其权重。如果访谈发现真正原生社交的受众，请说明并将重新加权路由回计划，而不是在此处吸收该决定。

在一次合作开始时需要明确说明的边界：将演讲录音变成片段、帖子和文章是
samber/dev-event-organizer-skills@event-content-repurposing
的工作，不是你的。你拥有活动前和活动进行中的发帖。活动后的档案挖掘管线正好在你的边界上，也是最容易被无意吸收的范围。

Interview

访谈

Ask one question at a time, multiple-choice where possible. Questions 5-7 exist because the menus below diverge sharply on time-to-effect, durability and effort - the default ordering cannot be picked for the user without them.

What did the marketing plan hand down for social: its weight in the mix, the fixed dates, the per-phase targets? If nothing was handed down, stop and route to
```
samber/dev-event-organizer-skills@event-marketing-plan
```
first - a content calendar with no campaign spine under it has nothing to hit.
Does this event deliberately opt out of promotion? Some do, and it is a real strategy, not a gap (see the opt-out below).
Where does this audience actually gather - name real properties, not the platforms you would name by default. A dispersed enterprise-infrastructure crowd, a single-campus student crowd and a design crowd share almost no platform.
What does the event already own: accounts and their real reach, a prior edition's photo archive, an existing house hashtag, a decentralized brand's shared tag?
What is the doors date, and how much runway is there before it? A short runway promotes the asks that use someone else's existing audience over anything that has to build one.
One edition's push, or an account meant to compound across editions? Be honest with the user here: an event account starts nearly cold each cycle unless the event persists, which is why creator-economy follower-growth advice does not transfer. A one-off push demotes every rung whose payback lands in a later edition - a second natively adapted account, an archive-building live rung; a compounding mandate promotes both.
Who actually writes and posts, for how many hours a week - and is that same person running the event on the day? This one answer decides the live-coverage rung more than any other.
Which governance pole does the event sit on: community-run, foundation-run, or company/vendor-run? It decides whether a neutrality policy constrains what the account may share.
What photo opt-out do the badges carry, and what do the speaker agreements say about recording and quoting? Collect this before planning any live coverage, not on the morning of.
Does any sponsor agreement contract live coverage, and is there a remote audience the live posts serve?
Does sponsor onboarding already collect a social handle to thank?

一次问一个问题，尽可能提供多选。问题 5-7 存在，是因为下面的菜单在见效时间、持久性和投入上差异很大——没有这些问题无法替用户选择默认排序。

营销计划为社交分配了什么：在组合中的权重、固定日期、各阶段目标？如果什么也没有下达，停下来，先路由到
```
samber/dev-event-organizer-skills@event-marketing-plan
```
——没有活动主线支撑的内容日历没有任何可击中的目标。
这个活动是否刻意选择不做推广？有些活动确实如此，这是一个真实的策略，而不是缺口（见下面的“退出”部分）。
这个受众实际聚集在哪里——说出真实的平台，而不是你默认会说的那些。分散的企业基础设施人群、单一校区的学生人群和设计人群几乎没有共享平台。
活动已经拥有什么：账号及其真实触达、往届照片档案、现有内部话题标签、去中心化品牌的共享标签？
开场日期是什么时候，之前还有多少时间？时间短就优先采用借他人现有受众的请求，而不是需要自建受众的东西。
是单届活动的推广，还是要在多届活动中复利的账号？这里要对用户诚实：除非活动持续存在，否则活动账号每届几乎从冷启动开始，这就是为什么创作者经济的涨粉建议不适用。一次性推广会降级所有回报落在后续届次的层级——第二个原生适配账号、建设档案的现场层级；复利任务则两者都提升。
谁实际撰写和发帖，每周多少小时——而且这个人是否在活动当天也是现场运营者？这一个答案比其他任何因素都更能决定现场报道层级。
活动处于哪个治理极点：社区运营、基金会运营，还是公司/厂商运营？它决定中立政策是否限制账号可以分享什么。
胸牌上有哪种照片退出机制，演讲者协议对录制和引用怎么说？在规划任何现场报道前收集这些，而不是当天早上。
是否有赞助商协议约定了现场报道，是否有远程观众由现场帖子服务？
赞助商入驻流程是否已经收集了用于感谢的社交账号？

Community-run, foundation-run, vendor-run

社区运营、基金会运营、厂商运营

The axis that genuinely changes this skill's output is who owns the event, because it decides what the account is allowed to post:

Community-run - no neutrality policy to enforce, no brand review, whoever holds the password posts. The constraint is volunteer hours, not permission.
Foundation-run - a written neutrality policy is likely, and it is restrictive. CNCF's own guidelines:
- Allow only "vendor-neutral, community-sourced" content.
- Forbid sharing anything promoting a vendor product or pointing at a company website.
- Replace case-by-case judgment with an explicit retweet allow-list.
This exists to enforce foundation neutrality and does not transpose downward: a vendor-run event has no symmetric reason to avoid promoting its own product, and a small community event has no sponsor-neutrality policy to enforce at all. Import it only at this pole.
Company/vendor-run - expect brand review, a marketer who owns the account, and paid amplification the other two poles cannot reach. Community and foundation guidance does not speak to this pole, so treat any rule borrowed from it as untested here.

真正改变这个 skill 输出的轴心是谁拥有活动，因为它决定账号_允许_发什么：

社区运营——没有需要执行的中立政策，没有品牌审查，谁拿着密码谁发帖。约束来自志愿者时间，而不是许可。
基金会运营——很可能有成文的中立政策，而且很严格。CNCF 自己的指南：
- 只允许“厂商中立、社区来源”的内容。
- 禁止分享任何推广厂商产品或指向公司网站的内容。
- 用明确的转发允许列表替代逐案判断。
这存在是为了执行基金会中立，不会向下迁移：厂商运营的活动没有对称的理由避免推广自己的产品，小社区活动也根本没有需要执行的中立政策。只在这个极点引入。
公司/厂商运营——预期有品牌审查、一个拥有该账号的市场人员，以及另外两个极点无法触及的付费放大。社区和基金会的指南不适用于这个极点，因此从那里借来的任何规则都视为未经测试。

The opt-out: some events should not run a content calendar

退出选项：有些活动不应该运行内容日历

Strange Loop's published guiding principles began, literally, with "No marketing" (thestrangeloop.com/about) - a long-running, heavily oversubscribed community-pole conference that deliberately declined active promotion as part of its identity. That is a real counter-example, not an execution gap.

Check three conditions before building any calendar. When they hold, recommend the minimal presence - a single announcement, the practical details, and nothing else - and say plainly that this is the identity-consistent choice rather than a shortfall:

Positioning is built on scarcity, curation or word-of-mouth (
```
samber/dev-event-organizer-skills@event-positioning
```
's category strategy will say so).
Demand already exceeds capacity without promotion, or a prior edition sold out on announcement alone.
The organizers experience promotion as off-brand, and the cultural identity's register supports them.

An event that opts out still needs the practical posts - dates, location, link, CFP close, doors - because the people already looking for it have to find them. "No marketing" is not "no information".

Strange Loop 公开的指导原则字面上以 “No marketing” 开头（thestrangeloop.com/about）——一个长期、严重超额订阅的社区极点会议，刻意将主动推广作为其身份的一部分而拒绝。这是一个真实的反例，而不是执行缺口。

在构建任何日历之前检查三个条件。当它们成立时，推荐最小存在——单个公告、实际信息，仅此而已——并明确说这是符合身份的选择，而不是不足：

定位建立在稀缺性、策展或口碑之上（
```
samber/dev-event-organizer-skills@event-positioning
```
的品类策略会说明）。
需求在没有推广的情况下已经超过容量，或者往届仅凭公告就售罄。
组织者认为推广不符合品牌，且文化身份的语调支持他们。

选择退出的活动仍然需要实用内容——日期、地点、链接、CFP 截止、开门时间——因为已经在寻找它的人必须能找到。“No marketing”不是“No information”。

Workflow

工作流程

Run the interview. Fix the weight, dates and targets from Q1 before anything else.
Test the opt-out conditions (Q2 with the positioning read). If they hold, ship the minimal presence and stop here.
Restate the message and the anti-positioning sentence from
```
samber/dev-event-organizer-skills@event-positioning
```
, and read the social column of the tone matrix from
```
samber/dev-event-organizer-skills@event-cultural-identity
```
. Every post below inherits both.
Pick the platform set with the breadth menu. Platform names are examples throughout - the mix shifts every couple of years, and the audience answer from Q3 outranks any list.
Decide the hashtags by purpose, not by habit. Full taxonomy and the community-signalling contrast: references/platform-fit-and-hashtags.md.
Map posts onto the plan's phases - announcement, CFP open and close, speaker reveals, agenda release, early-bird close, final push, live, wrap. Post types per phase, plus a worked calendar and its negative counterpart: references/phase-post-plan-and-amplification-kit.md.
Build the amplification asks with the posture menu, and produce the shareable kit once rather than per request.
Choose the live-coverage rung, then write the named volunteer and the photo rules into the run of show - not into a document nobody opens on the day. Route the operational slot to
```
samber/dev-event-organizer-skills@event-run-of-show
```
.
Hand the recordings, the photo archive and the quotable moments to
```
samber/dev-event-organizer-skills@event-content-repurposing
```
. Say what you are handing over; do not start cutting clips.
Feed the per-platform tracked links back to the marketing plan's referral-signal measurement. That measurement layer is the plan's, not yours - you supply the links, it reads them.

If your harness has persistent memory, record the platform set with the audience answer that justified it, the hashtag decisions and their purposes, which asks were made of whom, and what actually got posted with what response. Next edition starts from a real archive and a real list of people who amplified, instead of a blank calendar.

Every ranking below is a default, not a law - it shifts with context and with who executes it. Re-rank all three menus against what you already know about this organizer: an organizer with a large personal following, a volunteer who edits video for a living, a decentralized brand with a shared community tag, a photo-hostile code of conduct, an audience concentrated on one campus. Each of those overturns a default rung, and each menu below says which.

执行访谈。先根据 Q1 确定权重、日期和目标。
测试退出条件（Q2 结合定位解读）。如果成立，交付最小存在并在此停止。
复述
```
samber/dev-event-organizer-skills@event-positioning
```
传来的核心信息和反定位句，并从
```
samber/dev-event-organizer-skills@event-cultural-identity
```
读取语气矩阵的社交列。下面的每一条帖子都继承两者。
用广度菜单选择平台集合。平台名称只是示例——组合每几年就会变动，Q3 的受众答案优先于任何列表。
按目的而不是按习惯决定话题标签。完整分类和社区信号对比：references/platform-fit-and-hashtags.md。
将帖子映射到计划阶段——公告、CFP 开启和关闭、演讲者揭晓、议程发布、早鸟截止、最后冲刺、现场、收尾。每阶段的帖子类型，加上一个完整日历及其反面：references/phase-post-plan-and-amplification-kit.md。
用姿态菜单构建放大请求，并一次性生成可分享工具包，而不是按请求单独制作。
选择现场报道层级，然后把具名志愿者和照片规则写进现场流程（run of show）——而不是写进一份当天没人打开的文件。将运营时段路由到
```
samber/dev-event-organizer-skills@event-run-of-show
```
。
将录音、照片档案和可引用时刻交给
```
samber/dev-event-organizer-skills@event-content-repurposing
```
。说明你交接了什么；不要开始剪辑片段。
将每个平台的可追踪链接反馈给营销计划的来源信号测量。那个测量层是计划拥有的，不是你的——你提供链接，它读取它们。

如果你的运行环境有持久记忆，记录平台集合及支撑它的受众答案、话题标签决策及用途、向谁提出了哪些请求、实际发布了什么以及响应如何。下一届从一个真实档案和一份真实放大者列表开始，而不是一个空白日历。

下面的每个排序都是默认值，不是法则——它随上下文和执行者变化。根据你对组织者已知的信息重新排序所有三个菜单：拥有大量个人粉丝的组织者、以视频剪辑为生的志愿者、带有共享社区标签的去中心化品牌、对照片不友好的行为准则、集中在单一校区的受众。每一个都可能推翻一个默认层级，每个菜单下面都会说明。

Platform set breadth

平台集合广度

Ranked menu: reach bought per unit of organizer effort. The orderings below are judged, not measured.

effort (writing, adaptation, account upkeep):

full presence > two natively adapted > home plus mirror > single home platform

value (people reached who were not already coming, judged):

two natively adapted > full presence > home plus mirror > single home platform

efficiency:

home plus mirror > single home platform > two natively adapted > full presence

Value puts a well-run two-platform presence above a full spread on purpose. Marginal platforms reach heavily overlapping audiences, and at a volunteer effort budget they degrade into visibly unattended accounts - an account whose last post is four months old subtracts credibility from the event rather than adding reach.

Single home platform - one account, where Q3 says the audience actually is. Everything else is a link on the comms hub the marketing plan already builds.
Home plus mirror - the same posts cross-posted to a second platform with light adaptation. Cheap because nothing is rewritten.
Two natively adapted - each post rewritten to its platform's format and audience. This is where the hours go.
Full presence - four or more accounts, each maintained. MLH's campus-scale strategy names six platforms plus community groups: a real list, for an audience genuinely dispersed across them.
Default rung: home plus mirror.
Promotion condition: move to two natively adapted when Q3 names two platforms holding different audiences with different reasons to attend - for example a professional network reaching the managers who approve travel budgets, and a community platform reaching the practitioners who actually want the talks. Adapting for two flavors of the same audience buys nothing.

The starved option is full presence - second on value, first on effort, so efficiency never picks it. Promote it in two cases: a company-run event where maintaining the accounts is already somebody's job, and a campus-scale hackathon whose audience genuinely lives across the platform spread MLH documents, where no single home platform reaches even half of them.

When Q3 names one platform and one only, delete the other rungs rather than demoting them. A second account created "just in case" and then abandoned is worse than never opening it, and a rung parked at the bottom of a menu reappears as scope in week three.

排序菜单：每单位组织者努力所购买到的触达。以下排序是判断性的，不是测量值。

努力（写作、适配、账号维护）：

完整存在 > 两个原生适配 > 主场加镜像 > 单一主场平台

价值（触达原本不会来的人，判断）：

两个原生适配 > 完整存在 > 主场加镜像 > 单一主场平台

效率：

主场加镜像 > 单一主场平台 > 两个原生适配 > 完整存在

价值有意将运营良好的双平台存在置于全面铺开之上。边缘平台触达成高度重叠的受众，并且在志愿者精力预算下会退化为明显无人维护的账号——一个最后帖子在四个月前的账号会削弱活动的可信度，而不是增加触达。

单一主场平台——一个账号，就在 Q3 说受众实际所在的地方。其他一切都只是营销计划已经建立的通讯中心上的链接。
主场加镜像——相同帖子经轻量适配交叉发布到第二个平台。因为不重写，所以便宜。
两个原生适配——每个帖子都针对其平台的格式和受众重写。这就是时间花费所在。
完整存在——四个或更多账号，每个都维护。MLH 的校园规模策略列出了六个平台加社区群组：一个真实的列表，针对真正分散在这些平台上的受众。
默认层级： 主场加镜像。
提升条件： 当 Q3 指出两个平台承载_不同_受众且有不同的参会理由时，升级为两个原生适配——例如，一个专业网络触达批准差旅预算的管理者，一个社区平台触达真正想听演讲的实践者。为同一受众的两种口味做适配毫无收获。

被饿死的选项是完整存在——价值排名第二，努力排第一，所以效率永远不会选择它。在两种情况下提升它：公司运营的活动，维护账号已经是某人的工作；以及校园规模的 hackathon，其受众真正分散在 MLH 记录的多个平台上，没有任何单一主场平台能触达其中一半。

当 Q3 只提到一个平台时，删除其他层级而不是降级它们。“以防万一”创建然后废弃的第二个账号比从不打开更糟，停在菜单底部的层级会在第三周以范围的形式重新出现。

Amplification-ask posture

放大请求姿态

Ranked menu - borrowed reach per unit of coordination effort. The ordering is judgment.

effort (coordination, other people's calendars, per-item production):

coordinated partner push > per-speaker ask > sponsor thank-you == ready-made kit

value (reach through an audience that already trusts the poster, judged):

per-speaker ask > coordinated partner push > ready-made kit > sponsor thank-you

efficiency:

per-speaker ask > ready-made kit > sponsor thank-you > coordinated partner push

compliance cost (review triggered, reversibility spent):
```
sponsor thank-you == coordinated partner push > per-speaker ask
```
; the ready-made kit carries none.
Effort tie (sponsor thank-you == ready-made kit): both are one-off content production with nobody else's calendar in the loop. The kit is built once; the thank-you is minutes per sponsor against a handle already sitting in the onboarding checklist.
Compliance-cost tie (sponsor thank-you == coordinated partner push): both are governed by an already-signed agreement whose brand-usage and deliverable clauses decide what may be published. Both cost a check with the sibling that owns that agreement before posting - a public post cannot be un-published after the fact.
Per-speaker ask position: below both ties and above the kit's zero, because it does need one permission - the speaker's consent to being named and pictured. The speaker agreement normally grants it already, and the ask carries an explicit opt-out on top.
Ready-made kit - speaker cards, a copy block, the hashtag, the link, image sizes. Built once, used by every other ask. Give the templates going to speakers, jurors and coaches a personal discount-code slot their own post can carry - it turns "please share this" into something their own network gets value from, distinct from the plain sponsor template, which carries no such incentive.
Per-speaker ask - at confirmation, send the speaker their card plus one line asking them to post it and telling them the date the event's own post goes out. It rides on an email already being sent, which is why it is this cheap. At scale, decentralize delivery rather than routing every kit through one social owner: whoever internally manages a given speaker, sponsor or coach relationship hands that person their own kit, so amplification scales with the number of internal stakeholder-owners rather than bottlenecking on one person's queue.
Sponsor thank-you - DevOpsDays' organizing guide collects, alongside logo and invoice details, "a Twitter handle for you to thank (very optional)". Its own framing is the point: goodwill, not a deliverable. Present it that way.
Coordinated partner push - partner communities, media partners and ambassador programs posting on a dated moment. The deal itself belongs to
```
samber/dev-event-organizer-skills@event-media-partnerships
```
and
```
samber/dev-event-organizer-skills@cross-event-promotion
```
; you supply the date and the assets.
Default rung: the ready-made kit plus the per-speaker ask.
Promotion condition, keyed to Q11: add the sponsor thank-you the moment sponsor onboarding already collects a handle - it costs minutes. Add the coordinated push only once the marketing plan has weighted partner channels for that phase and the deal already exists.

The starved option is the coordinated partner push - second on value, first on effort. Promote it when the partnership deal is already signed (the marginal effort is then only date coordination, not negotiation), and for a first edition with no audience of its own, where borrowed audiences are the only audiences available.

For an event with no sponsors, delete the sponsor rung rather than leaving it as an aspiration on the menu. Same for the partner push when no partnership exists and none is being pursued this cycle.

A note on posting before asking: check whether the sponsor agreement already contracts a social mention. If it does, the post is a fulfilment item owned by

samber/dev-event-organizer-skills@event-sponsor-fulfillment

and missing it is a breach, not a missed courtesy.

排序菜单——每单位协调努力借来的触达。排序是判断。

努力（协调、他人的日历、逐项制作）：

协调合作伙伴推送 > 逐演讲者请求 > 赞助商感谢 == 现成工具包

价值（通过已经信任发帖者的受众触达，判断）：

逐演讲者请求 > 协调合作伙伴推送 > 现成工具包 > 赞助商感谢

效率：

逐演讲者请求 > 现成工具包 > 赞助商感谢 > 协调合作伙伴推送

合规成本（触发的审查、已消耗的可逆性）：
```
赞助商感谢 == 协调合作伙伴推送 > 逐演讲者请求
```
；现成工具包不携带任何合规成本。
努力并列（赞助商感谢 == 现成工具包）：两者都是一次性内容制作，不涉及其他人的日历。工具包制作一次；感谢则是每个赞助商花几分钟，使用已入驻检查清单中的句柄。
合规成本并列（赞助商感谢 == 协调合作伙伴推送）：两者都受已签署协议约束，协议中的品牌使用和交付条款决定可以发布什么。两者在发布_前_都需要与拥有该协议的兄弟方核实——公开帖子事后无法取消发布。
逐演讲者请求位置： 低于两个并列，高于工具包的零，因为它确实需要一个许可——演讲者同意被点名和拍照。演讲者协议通常已经授予这一许可，请求还带有明确退出选项。
现成工具包——演讲者卡片、一段文案块、话题标签、链接、图片尺寸。制作一次，其他每个请求都使用。给发给演讲者、评委和教练的模板加上一个他们自己的帖子可以携带的个人折扣码位置——它将“请分享这个”变成他们自己的网络从中获得价值的东西，不同于没有这种激励的普通赞助商模板。
逐演讲者请求——确认时，给演讲者发送他们的卡片和一行请求，请他们发布并告知他们活动自己帖子发布的日期。它搭在一封已经发送的电子邮件上，这就是它如此便宜的原因。规模化时，去中心化交付而不是通过一个社交负责人路由每个工具包：内部管理某个演讲者、赞助商或教练关系的人将该工具包交给那个人，这样放大随着内部干系人所有者的数量扩展，而不是瓶颈在一个人的队列上。
赞助商感谢——DevOpsDays 的组织指南在 logo 和发票详情之外收集“一个供你感谢的 Twitter 账号（非常可选）”。它自己的表述就是重点：善意，而不是交付物。就这样呈现。
协调合作伙伴推送——合作伙伴社区、媒体合作伙伴和大使项目在约定日期发帖。交易本身属于
```
samber/dev-event-organizer-skills@event-media-partnerships
```
和
```
samber/dev-event-organizer-skills@cross-event-promotion
```
；你提供日期和素材。
默认层级： 现成工具包加上逐演讲者请求。
提升条件，与 Q11 关联： 只要赞助商入驻已经收集了句柄，就添加赞助商感谢——只需几分钟。只有营销计划已为该阶段加权合作伙伴渠道且交易已经存在时，才添加协调推送。

被饿死的选项是协调合作伙伴推送——价值第二，努力第一。当合作协议已经签署时提升它（边际努力于是只是日期协调，而不是谈判），对于没有自己受众的首届活动，借来的受众是唯一可用的受众。

对于没有赞助商的活动，删除赞助商层级，而不是把它作为菜单上的愿望留下。当不存在合作伙伴关系且本周期不追求时，合作伙伴推送同理。

关于在请求_之前_发帖的说明：检查赞助商协议是否已经约定了社交媒体提及。如果是，该帖子是由

samber/dev-event-organizer-skills@event-sponsor-fulfillment

拥有的履行项，缺失它是违约，而不是礼节失误。

Live-coverage depth

现场报道深度

Ranked menu - evidence and in-room amplification bought per unit of effort on a day when everyone is already busy.

effort (people, attention, on-the-day capacity):

full live desk > roving poster > scheduled skeleton > single recap

value (reach plus the archive next edition and next year's sponsors need, judged):
```
full live desk > roving poster > single recap > scheduled skeleton
```

efficiency:

single recap > roving poster > full live desk > scheduled skeleton

compliance cost (consent obtained, reversibility spent):
```
full live desk > roving poster == single recap
```
; the scheduled skeleton carries none.

The compliance tie is argued: the roving poster and the recap both publish images of identifiable attendees, so both need the same consent mechanism in place beforehand - the badge-carried photo opt-out owned by

samber/dev-event-organizer-skills@event-accessibility-inclusion

. They differ in volume, not in the permission required. The full desk adds live-quoting speakers and often streaming, which needs recording consent the speaker agreement may or may not already grant.

The skeleton ranks last on efficiency despite costing little, and that is deliberate: pre-written "doors are open" posts produce no artifact and reach mostly people already standing in the room. Its work goes into looking active rather than into anything reusable.

Single recap - one post after doors close, carrying the day's real photos and a thank-you. Half an hour, and it produces something next edition can reuse. A deliberately minimal post-event plan stops at this plus one longer recap video across the archive's channels - resist growing it into a sprawling multi-week recap campaign the team cannot sustain against next edition's own workload.
Scheduled skeleton - three to five posts written and scheduled in advance. Ships reliably with nobody's attention on the day, which is its whole and only merit.
Roving poster - one named volunteer posting photos and quotes through the day. The archive this produces is what feeds the sponsor report, next edition's promotion, and
```
samber/dev-event-organizer-skills@event-content-repurposing
```
.
Full live desk - several people, per-talk posts, a live thread, a photo pipeline, replies in real time.
Default rung: the single recap.
Promotion condition: move to the roving poster as soon as a volunteer can be named in the run of show - not hoped for on the morning. An unnamed live-posting duty is the one that silently does not happen.

The starved option is the full live desk - first on value, first on effort, so efficiency never picks it. Promotion condition, keyed to Q10: a sponsor agreement actually contracts live coverage, or the event has a remote audience for whom the live posts are the event.

For an event whose code of conduct or cultural identity restricts photography - a strict photo policy, an off-the-record norm, a badge-based opt-out that most attendees use - delete the photo-based rungs instead of demoting them. Plan text-only coverage or none, and say why, so nobody quietly reintroduces a camera on the day.

排序菜单——在每个人都已经很忙的那一天，每单位努力买到的证据和场内放大。

努力（人员、注意力、当天容量）：

完整现场台 > 流动发帖人 > 预定骨架 > 单一回顾

价值（触达加上下一届和明年赞助商需要的档案，判断）：
```
完整现场台 > 流动发帖人 > 单一回顾 > 预定骨架
```

效率：

单一回顾 > 流动发帖人 > 完整现场台 > 预定骨架

合规成本（已获得同意、已消耗可逆性）：
```
完整现场台 > 流动发帖人 == 单一回顾
```
；预定骨架不携带任何。

合规并列的论证：流动发帖人和回顾都发布可识别到场者的图片，因此两者都需要提前建立相同的同意机制——由

samber/dev-event-organizer-skills@event-accessibility-inclusion

拥有的胸牌携带照片退出选项。它们的区别在于数量，而不是所需许可。完整现场台增加了现场引用演讲者，通常还有直播，这需要演讲者协议可能授予也可能未授予的录制同意。

骨架在效率上排名最后，尽管花费很少，这是故意的：预先写好的“门开了”帖子不产生任何工件，触达的主要是已经站在房间里的人。它的工作花在看起来活跃上，而不是任何可复用的东西上。

单一回顾——关门后一条帖子，承载当天真实照片和感谢。半小时，并产生下一届可以复用的东西。一个刻意最小的活动后计划止步于此，加上跨档案渠道的一个较长回顾视频——抵制将其扩展成团队无法在下一届自身工作量下维持的庞大数周回顾活动。
预定骨架——提前写好并安排的三到五条帖子。当天无需任何人关注即可可靠交付，这是它全部也是唯一的优点。
流动发帖人——一个具名志愿者全天发布照片和引语。这产生的档案正是滋养赞助商报告、下一届推广和
```
samber/dev-event-organizer-skills@event-content-repurposing
```
的东西。
完整现场台——几个人、逐演讲帖子、一个直播线程、照片管线、实时回复。
默认层级： 单一回顾。
提升条件： 只要有志愿者可以被_写进现场流程_——而不是早上希望——就升级为流动发帖人。未具名的现场发帖职责就是那个悄然不会发生的职责。

被饿死的选项是完整现场台——价值第一，努力第一，所以效率永远不会选择它。提升条件，与 Q10 关联：赞助商协议实际约定了现场报道，或者活动有远程观众，对他们来说现场帖子_就是_活动。

对于行为准则或文化身份限制摄影的活动——严格的照片政策、非记录规范、大多数与会者使用的基于胸牌的退出——删除基于照片的层级而不是降级它们。计划纯文字报道或不报道，并说明原因，这样就不会有人在当天悄悄重新引入相机。

Failure modes

失败模式

Arguing against the umbrella's channel weight. Opening a social plan by making the case that social should lead contradicts a decision
```
samber/dev-event-organizer-skills@event-marketing-plan
```
already made, and wastes the engagement on a fight the plan already settled. Run the discounted baseline well; route a genuine reweighting case back to the plan.
Importing a creator-economy benchmark. "Post 3-5 times a week on a professional network, 3-10 times a day on a microblog" is continuous personal-brand cadence, measured on accounts that compound followers over years. An event campaign is short, dated and checkpoint-driven, starts near-cold each edition, and the mismatch is structural, not a matter of tone.
Treating a community hashtag as a campaign tag. DevOpsDays tells prospective organizers to post "(Use the #devopsdays hashtag.)" - that is a standing community-identity tag letting a decentralized network find each other, not a per-edition measurement tag. Riding a community tag without also having your own campaign tag loses the measurement purpose entirely.
Redefining positioning in a post. A new angle invented for a caption creates a second, competing story about what the event is. Carry the positioning sentence; do not improve it.
Doing the repurposing sibling's job. Cutting talk clips, writing recap articles and building an evergreen distribution plan after the event belongs to
```
samber/dev-event-organizer-skills@event-content-repurposing
```
. Hand over the archive and stop.
Presenting the sponsor thank-you as obligatory. Its own source calls it "very optional". Sold as a duty, it turns a goodwill gesture into an unfunded deliverable - and if the agreement genuinely contracts a mention, that is a fulfilment item, not this.
Importing a foundation's neutrality policy into a community or vendor event. CNCF's rules exist to enforce foundation neutrality:
- Applied to a small community event, they forbid perfectly normal posts for no reason.
- Applied to a vendor-run event, they forbid the thing the event exists to do.
Letting the same person post live and run the day. The organizer on duty cannot answer a venue problem and cover a keynote at once. Name a different person or drop to the recap rung.
Inventing a cadence number to sound precise. Anchor posts to campaign dates that actually exist instead - a date is defensible, a frequency is not.

反对总纲的渠道权重。 以“社交应该主导”为开场来制定社交计划，与
```
samber/dev-event-organizer-skills@event-marketing-plan
```
已经做出的决定相矛盾，并把合作浪费在一场计划已解决的战斗上。把被低估的基线运营好；将真正的重新加权案例路由回计划。
引入创作者经济基准。 “在专业网络上每周发 3-5 次，在微博客上每天 3-10 次”是持续的个人品牌节奏，衡量的是多年累积粉丝的账号。活动活动是短期的、有日期的、以检查点驱动的，每届接近冷启动，这种不匹配是结构性的，不是语气问题。
将社区话题标签当作活动标签。 DevOpsDays 告诉潜在组织者发布“（使用 #devopsdays 话题标签。）”——这是一个常设的社区身份标签，让去中心化网络找到彼此，而不是每届的测量标签。使用社区标签却没有自己的活动标签，完全失去测量目的。
在帖子中重新定义定位。 为配文发明的新角度制造了关于活动是什么的第二个竞争故事。承载定位句；不要改进它。
做复用兄弟的工作。 剪辑演讲片段、写回顾文章和构建活动后的常青分发计划属于
```
samber/dev-event-organizer-skills@event-content-repurposing
```
。交出档案并停下。
把赞助商感谢说成义务。 其来源称之为“非常可选”。把它作为职责销售，会把善意姿态变成无资金支持的交付物——如果协议确实约定了提及，那是履行项，不是这个。
将基金会的中立政策引入社区或厂商活动。 CNCF 的规则存在是为了执行基金会中立：
- 应用于小型社区活动，它们毫无理由地禁止完全正常的帖子。
- 应用于厂商运营的活动，它们禁止活动存在的目的。
让同一个人现场发帖并运营当天。 当值的组织者无法同时处理场地问题和报道主题演讲。指定另一个人或降到回顾层级。
发明一个频率数字来显得精确。 相反，将帖子锚定到实际存在的活动日期——日期是可辩护的，频率不是。

Measurement

测量

This skill sets no numeric pass threshold, and that refusal is deliberate. A target like "4% engagement" would be false precision imported from an unrelated domain; the reader would optimize against a number that means nothing here. Judge the channel on whether the dated posts shipped and whether the tracked links moved, not on a rate.

One real event-account figure exists and is worth naming precisely so it is not mistaken for a target: a 2025 academic study of 22 named computer-science conference accounts on X (arXiv:2503.01038) measured a median of 9 likes and 3 reposts per post, with follower counts from 206 to 74,115 and a strong correlation (Pearson 0.95) between follower count and likes. Those accounts are established conference brands that accumulated followers across up to 14 recurring editions - a continuously compounding audience, not a campaign starting near-cold each edition - so the figures describe that audience, not a threshold to import here.

Every dated post in the plan shipped on its date (self-set, binary): the only measure fully inside your control, and the one that fails most often on volunteer teams.
Per-platform tracked link (self-set): a distinct link per platform, decided before launch because it cannot be added retroactively. The marketing plan owns reading these; you own creating them.
Amplification take-up (self-set): how many speakers and partners actually posted, out of those asked. A low rate diagnoses the ask, not the audience - usually an ask that arrived without a ready-made asset attached.
The archive produced (self-set, and the one that pays next edition): photos, quotes and recordings usable by
```
samber/dev-event-organizer-skills@event-content-repurposing
```
and by next edition's promotion. A day covered by nobody produces nothing to promote with next year.

这个 skill 设定没有数字通过阈值，这种拒绝是故意的。像“4% 参与率”这样的目标是从无关领域引入的虚假精确；读者会针对一个在这里毫无意义的数字进行优化。根据日期帖子是否发布以及追踪链接是否移动来判断渠道，而不是根据某个比率。

有一个真实的活动账号数据值得精确命名，以免被误认为目标：2025 年一项对 X 上 22 个具名计算机科学会议账号的学术研究（arXiv:2503.01038）测量到每条帖子中位数 9 个赞和 3 个转发，粉丝数从 206 到 74,115，粉丝数与点赞之间有强相关性（Pearson 0.95）。这些账号是成熟的会议品牌，在多达 14 届连续性活动中累积了粉丝——一个持续复利的受众，而不是每届接近冷启动的活动——因此这些数据描述的是那个受众，而不是要在这里引入的阈值。

计划中的每个日期帖子都按约定日期发布（自设，二元）：唯一完全在你控制之内的衡量指标，也是在志愿者团队中最常失败的指标。
每平台追踪链接（自设）：每个平台一个独特链接，在启动前决定，因为它无法追溯添加。营销计划拥有读取这些链接；你拥有创建它们。
放大采纳率（自设）：在被请求的演讲者和合作伙伴中，实际发布了多少。低比率诊断的是请求，而不是受众——通常是请求没有附带现成素材。
产生的档案（自设，也是回报下一届的那个）：可供
```
samber/dev-event-organizer-skills@event-content-repurposing
```
和下一届推广使用的照片、引语和录音。没人报道的一天不会产生任何可用于明年推广的东西。

Invocation examples

调用示例

"We're four months out from our 300-person infra conference. What should we be posting, and where?"
"Our first speakers just confirmed - how do we announce them and get them to share it?"
"Should our hackathon be on TikTok, or is that a waste of time for a student audience?"
"What do we post during the event itself? Nobody has a spare pair of hands that day."
"Our conference has always run on word of mouth and the organizers hate marketing. Do we even need a social plan?"

Expected output, with every judged or self-set element labeled as such:

The platform set, with the audience answer that justified it.
The hashtag decisions, with each one's purpose.
A phase-mapped post plan pinned to the marketing plan's actual dates.
The amplification asks, with who gets asked when and the kit they receive.
A live-coverage rung, with a named person and the photo rules.

The handover list for

samber/dev-event-organizer-skills@event-content-repurposing

“距离我们 300 人的基础设施大会还有四个月。我们应该发什么，发在哪里？”
“我们的第一批演讲者刚刚确认——我们如何宣布他们并让他们分享？”
“我们的 hackathon 应该上 TikTok 吗，还是说对学生受众来说这是浪费时间？”
“活动期间我们发什么？那天没有人有空余的手。”
“我们的会议一直靠口碑运行，组织者讨厌营销。我们甚至需要社交计划吗？”

预期输出，每个判断性或自设元素都如此标记：

平台集合，以及证明其合理性的受众答案。
话题标签决策，以及每个的目的。
一个映射到营销计划实际日期的分阶段帖子计划。
放大请求，谁在什么时候被请求，以及他们收到的工具包。
一个现场报道层级，带具名的人和照片规则。

交给

samber/dev-event-organizer-skills@event-content-repurposing

的交接清单。

References

参考

references/platform-fit-and-hashtags.md - the platform-fit table by campaign phase, the three-purpose hashtag taxonomy against the community-signalling contrast, the neutrality-policy scope flag, and the who-posts-versus-who-requests workflow for a team account.
references/phase-post-plan-and-amplification-kit.md - a worked phase-mapped post plan with its negative counterpart, the speaker and sponsor ask templates, the shareable kit contents, and the live-coverage briefing checklist.