Open Source Roundup Thread

Open Source Roundup Thread

Create a Typefully draft for the brand account from a source brief, reference thread, or GitHub PR roundup. The default output is:

• X thread
• Bluesky thread
• LinkedIn single post

Prerequisites

Load the typefully skill and use its CLI for all Typefully operations.

Inputs

Accept any of these input styles:

• A pasted brief with the desired opener, theme, PR links, and notes.
• A reference post or thread URL whose structure and voice should be matched.
• A request to round up recent GitHub activity, e.g. "find the top Windows community PRs from the last week."
• A mixed request, e.g. "Use this reference thread, but make the theme Windows fixes and include these PRs."

Clarify only if a missing detail blocks the work. Otherwise choose sensible defaults:

• Brand account: / @your-brand
• Platforms: X, Bluesky, LinkedIn
• X and Bluesky: thread
• LinkedIn: single consolidated post
• Draft only, not scheduled or published
• Generate a share URL when creating the draft

Reference pattern

When matching a prior open-source roundup, read references/community-contribution-thread.md. It captures the thread cadence from the reference thread used to create this skill:

• Short opener about open source/community momentum.
• One post per contribution.
• Name the contributor when known.
• Explain the user-facing fix in plain language.
• Link the PR.
• End with a simple contribution CTA.

Execution notes

Ground the draft in source facts before writing. For PR-based threads, fetch PR metadata and contributor profile details. Look up each contributor's GitHub profile twitter_username and linked social accounts before writing any @ mention. Use an X/Twitter @ handle only when it is explicitly linked from the contributor's GitHub profile or otherwise provided by the user/source material. If no verified X/Twitter handle is found, default to the contributor's display name plus GitHub handle, or just their GitHub handle without an @ prefix. Prefer merged PRs, and describe open PRs as "in review" or "in progress."

If the user provides a reference X thread, fetch the full thread rather than only the opener. If drafting for the brand, use .agents/skills/draft-brand-tweet/style-notes.md when available for voice guardrails.

When querying GitHub for community PRs, filter by label:external-contributor to surface externally contributed work. Use user.list in Slack to look up the relevant teammate's user ID before sending any Slack messages.

Draft around the contribution story:

• Opener: community/open-source angle + theme.
• Body: one post per community contribution or highlighted fix.
• Maintainer fixes: include only the strongest one or two unless asked otherwise.
• Close: simple contribution CTA.

Aim for 5 posts total. Use 6-7 only when there are enough strong, distinct contributions to justify the extra length; do not pad the thread with weaker fixes.

For each post, explain the user-facing fix plainly, keep gratitude brief, and avoid implying community work failed. If a maintainer completes a fix with community signal, framing like "got it to the finish line" works well.

Use the typefully CLI to look up the social set, confirm configured platforms, and create a draft with --share. X and Bluesky should be threads; LinkedIn should be one consolidated post. Put factual caveats, open PR notes, or review concerns in --scratchpad.

Return the private edit URL, share URL, included platforms, and any caveats. Do not paste the full draft back unless the user asks; Typefully is the source of truth after creation.

Quality checklist

Before creating the Typefully draft:

• Every non-trivial claim maps to a PR, reference post, or user-provided fact.
• Open PRs are described as in review/in progress.
• Contributor names/handles are accurate and not guessed.
• The opener fits the theme and does not feel over-sold.
• The LinkedIn version is a single post, not a thread.
• Scratchpad includes caveats the social team should review.