写作与内容
写作、编辑、发布和翻译工作流
Skills 列表
developer-journey-map
Maps the developer journey for one audience segment - discovery, trial, adoption, contribution, advocacy - as a stage-by-stage table where each stage carries an exit event, a named owner, cited friction evidence and one signal, and names the single leak worth fixing next. Use whenever someone asks what their developer journey looks like, wants a developer adoption funnel or journey map, asks why developers try the product but never reach production, where adoption drops off, who owns each step of developer experience, or how developers become contributors - even if they only say "we lose people somewhere". Not the metrics framework - use samber/developer-relations-skills@devrel-metrics.
samberdevrel-content-calendar
Plans a quarter of developer-relations content as a dated slot plan with named owners and reviewers - fixed anchors (releases, launches, CFP deadlines, conferences), a surface, pillar, journey and shelf-life mix, and sizing against real writing and review capacity. Use whenever the user asks for a devrel content calendar, an editorial calendar or content plan for a developer audience, what to publish next quarter, how to balance evergreen against launch-tied content, how many pieces a small team can ship, or says their content plan keeps slipping - even if they only say "we publish randomly". Plans the quarter only; individual pieces go to the per-format skills such as samber/developer-relations-skills@engineering-blog-post.
sambergithub-profile-optimization
Audits and rebuilds a personal or organization profile on GitHub as a developer-relations surface - the profile README, the six pinned items, bio and social fields, the organization profile repository, and the contribution signals visitors read as evidence. Use whenever someone says "optimize my GitHub profile", "profile README", "our GitHub org page is empty", "what should I pin", "nobody knows what our company builds on GitHub", or is preparing a launch, a talk or a job search - even if they only mention their GitHub page. Covers solo maintainers, company organizations, and engineers whose profile gets read during hiring. GitHub-scoped: the audit script and pin/contribution-graph mechanics are GitHub-specific, though the checklist reasoning transfers by hand to another forge. Not a single repository's README - use samber/developer-relations-skills@readme-optimization.
samberdeveloper-champions
Designs an unpaid, perks-only developer champions or ambassador program end to end - readiness check, intake model, published selection criteria, behaviour-based obligations, an access-first perk ladder, fixed terms with renewal and alumni status, and a cohort scorecard. Use whenever the user mentions an ambassador or champions program, MVP-style recognition, community heroes, "how do we recognise our top community members", what perks ambassadors should get, an ambassador program that went quiet, or removing an inactive champion - even if they never say "champion". Not for paid creator, affiliate or revenue-share partnerships. For measuring the community itself use samber/developer-relations-skills@developer-community-health.
samberconference-cfp-submission
Turns a talk idea into a submission-ready conference proposal for one specific event, or helps choose which conferences to target and plan a submission calendar across several - track fit, title options, an attendee-facing abstract, verb-first takeaways, the reviewer-only fields, a credibility package, and a self-review against the committee's own criteria. Use whenever the user mentions a CFP, a call for papers, a conference proposal, a talk abstract, a session description, submitting to KubeCon, PyCon or FOSDEM, which conference to submit to, planning a CFP season, or says their proposals keep getting rejected - even if they only ask to shorten an abstract. Covers community-run and vendor-run events. Do NOT use for structuring the accepted talk (samber/developer-relations-skills@tech-talk-outline) or its demo (samber/developer-relations-skills@developer-live-demo-design).
samberengineering-blog-post
Writes or edits a technical blog post a skeptical developer audience will believe - the right post pattern, evidence behind every claim, published trade-offs and limitations, runnable snippets, and no marketing voice. Use whenever the user wants an engineering blog post, a technical article, a "how we built it" or "we rewrote it in X" story, a debugging write-up, a public postmortem, a benchmark post, or a product post that must not read as marketing, and when they ask to review, edit, de-jargon or de-market an existing technical draft - even if they only call it "the article". Not a teaching tutorial - use samber/developer-relations-skills@developer-tutorial. Not release notes, a migration guide, a case study or a talk.
samberbuild-in-public
Designs a sustainable build-in-public practice for an open-source project or developer tool: how far up the disclosure ladder to go (shipping log, decisions, failures, metrics, revenue), a cadence the maintainer can hold, the platform mix, and the boundaries that keep security, customer and roadmap detail off the public record. Use whenever someone mentions building in public, a devlog, weekly updates, an open-startup or transparency dashboard, sharing metrics or revenue openly, fear of copycats, oversharing, wanting to stop publishing numbers, or a stalled practice they want to restart, even if they never say "build in public". Covers solo maintainers, bootstrapped and funded devtools teams. Not for a one-time launch; use samber/developer-relations-skills@oss-launch.
sambertech-podcast-youtube-channel
Run an organizer's own standing podcast or video channel as a cross-edition media property - whether to sustain a channel at all, the cadence commitment and its named owner in the quiet months, guest sourcing from the speaker pool outward, the two-way feed with the event cycle, and the wind-down or handover when organizers change. Use whenever the user mentions starting a conference podcast or YouTube channel, publishing between editions, where episode guests come from, who owns the show when an organizer leaves, or closing one down - even if they never say "podcast". Do NOT use for cutting one edition's talk recordings into clips - use samber/dev-event-organizer-skills@event-content-repurposing instead.
samberhackathon-brief-design
Write the hackathon challenge document teams read before they build - problem statements sized to the time box, thematic challenge tracks, the published rules and eligibility text, the submission-artifact checklist, sponsor-challenge framing, and naming (never weighting) the evaluation categories. Use whenever the user mentions a hackathon brief, challenge or track prompts, hackathon rules or eligibility, submission guidelines, or turning a sponsor's API into a challenge - even if they never say "brief". Challenge tracks here are thematic categories a team enters, not parallel session streams. Do NOT use for rubric weights and judging mechanics - use samber/dev-event-organizer-skills@hackathon-judging instead.
samberevent-media-partnerships
Set up barter media and community partnerships for a technical event - visibility-for-visibility deals with newsletters, podcasts, online communities and developer-ambassador programs, where no cash changes hands. Covers deal classes, partner types, the exchange format (calendar listing, logo-and-social swap, newsletter mention swap, podcast exchange, full media-partner tier), the deal terms, and both sides' delivery tracking. Use whenever asked to find media partners, set up a community-sponsor tier, trade newsletter mentions or podcast slots for event visibility, or formalize a logo-for-promotion deal. Do NOT use for earned press - use samber/dev-event-organizer-skills@event-press-relations - or swaps with other events - use samber/dev-event-organizer-skills@cross-event-promotion.
samberevent-social-media
Run a technical event's own social presence inside the weight, phase and dates the marketing plan already fixed - platform selection, the campaign versus community hashtag, posts mapped onto campaign phases (announcement, CFP, speaker reveal, final push, live), speaker and sponsor amplification asks, and day-of coverage. Use whenever the user mentions event social media, a conference or hackathon content calendar, speaker-announcement posts, which platforms an event should post on, an event hashtag, or briefing a volunteer on live posting - even if they never say "social media". Do NOT use for channel weight and budget - use samber/dev-event-organizer-skills@event-marketing-plan; mining talk recordings afterwards is samber/dev-event-organizer-skills@event-content-repurposing.
samber
indexion-readme
README 构建 — 初始化模板结构，从文档注释生成每个包的 README，规划写作任务，通过 doc.json 配置从 docs/ 和包 README 组装根 README，并使用 `plan drift` 验证编辑。
trkbt10indexion-refactor
编写代码后，检测并清理三个层面的重复——复制粘贴块、跨包共享代码、不必要的包装器以及概念层面的单一真实来源（SoT）违规。使用 indexion 检测、修复并验证。
trkbt10
affiliate-disclosure-compliance
Check a specific piece of affiliate or influencer content (caption, video script, transcript, screenshot, or live URL) against disclosure regulations and return a pass/fail compliance review with placement, wording, and per-format fixes. Covers FTC affiliate disclosure (16 CFR 255 and 465), UK CAP/CMA rules, EU UCPD and DSA, and German, French and Italian overlays, pre-publication or already live. Use whenever the user mentions affiliate disclosure, FTC disclosure, paid partnership labeling, sponsored content, ad tags, or a partner post that may be missing or burying its disclosure, even if they never say compliance. Reviews content only - for disclosure clauses inside program terms use mbfinotti/partnerships-skills@affiliate-program-terms.
mbfinottiaffiliate-recruitment-outreach
Draft the outreach copy and sequence plan used to recruit new affiliates into a commission-based affiliate program - prospect qualification and tiering, pitch angle, first-touch recruitment email, follow-up sequence with a breakup touch, channel mix, and outreach tracking. Covers B2B SaaS and B2C ecommerce/DTC programs. Use whenever the user mentions recruiting affiliates, affiliate sourcing, or pitching content and review sites, coupon and cashback partners, newsletter operators, communities, podcasters, or agencies to join a program, even if they never say recruitment. Do NOT use for pitching one individually vetted creator - use mbfinotti/partnerships-skills@influencer-outreach instead.
mbfinottiinfluencer-discovery-brief
Define creator sourcing criteria and produce the discovery brief used to shortlist candidate influencers and creators - weighted criteria for audience fit, engagement quality, niche consistency and brand safety, knockout screens, and a ranked shortlist scoring template with evidence per score. Covers B2C brand campaigns and B2B creator and thought-leader programs. Use whenever the user mentions finding creators, vetting influencers, audience fit, creator shortlists, or deciding which creators to approach, even if they never say discovery. Runs before any contact. Do NOT use for writing the pitch message itself - use mbfinotti/partnerships-skills@influencer-outreach instead.
mbfinottiinfluencer-measurement-framework
Design the pre-launch measurement plan for one influencer or creator campaign - KPIs matched to the objective (awareness, engagement, conversion, affiliate-linked, always-on ambassador), an attribution method and data source behind each KPI, reporting cadence per stakeholder, and declared blind spots. Delivered as a measurement plan document before launch, for B2B and B2C alike. Use whenever the user mentions influencer KPIs, creator campaign attribution, campaign reporting, or asks how to measure a creator partnership, even if they never say measurement. Do NOT use for an ongoing affiliate program dashboard - use mbfinotti/partnerships-skills@affiliate-performance-dashboard instead.
mbfinottiinfluencer-negotiation-playbook
Prepare a brand-side partnership manager to negotiate deal terms with an influencer or creator, from the creator's first positive reply to a signed contract - a written playbook of term-by-term opening positions, a concession ladder, red-flag responses, and walk-away thresholds covering rates, usage rights, exclusivity, revision limits, payment terms, and kill fees. Covers B2C brand collabs and B2B creator programs. Use whenever the user mentions creator rates, creator deal terms, usage rights, exclusivity, or negotiating with a creator's talent manager, even if they never say negotiation. Requires the user's own rate benchmarks. Do NOT use for the first-touch pitch - use mbfinotti/partnerships-skills@influencer-outreach instead.
mbfinottiinfluencer-outreach
Draft the personalized first-touch pitch message and follow-up plan used to propose a partnership to one already-vetted influencer or creator - personalization angle, the compensation stated on offer, a message fitted to the channel the creator actually lists (email, DM, or their manager), and a bounded follow-up cadence. Covers B2C brand collabs and B2B creator programs (newsletter writers, podcasters, industry experts). Use whenever the user mentions pitching a creator, DMing an influencer, a collab proposal, or a creator outreach message, even if they never say outreach. Stops at the first positive reply. Do NOT use for list-scale affiliate recruitment - use mbfinotti/partnerships-skills@affiliate-recruitment-outreach instead.
mbfinotti
remove-ai-style
审查并改写中文或英文散文，以减少AI生成模式。适用于去AI润色、自然语言重写、机器人化或公式化写作，以及出版前清理。始终先运行捆绑的确定性Markdown分析器，检查每个报告的位置，然后通读全文以查找规则无法枚举的语义模式。
zc277584121content-rewrite
为不同平台（LinkedIn、X、Reddit、英文博客、微信公众号）调整和重写内容。每个平台都有其独特的语气、格式和长度要求。
zc277584121image-generation
为文章和文档生成插图，采用 Codex 优先工作流，OpenAI API 作为备用，Gemini 作为最后备用。
zc277584121
decision-records
Draft, promote, archive, and supersede ADR-style decision records (types are open: architecture, product, security, policy, legal, …) and keep INDEX.md and cross-links generated, via the bundled scripts/decisions.py tool. Use when creating or promoting decision drafts, superseding or archiving a decision, fixing a promotion breach, or running build, check, promote, rename-draft-id, or install.
skymavismilvus-meme-sticker
Create tiny no-text Milvus-style sticker memes for technical marketing, WeChat-style article moments, community posts, and developer-group reactions. Use when the user wants an original meme/sticker with an abstract Milvus bird/eagle mascot, strong exaggerated emotion, internet-native sticker energy, light-blue accents without making the whole character blue, and deterministic small-size exports such as 512, 240, 120, or 50 px.
zc277584121