social-content git:20261022.860e2dcA

Immutable. This exact content never changes and is served at /api/v1/blob/9293078b419f08c1.

---
name: social-content
description: "Draft and revise LinkedIn and other social posts, product announcements, threads and carousel copy from supplied evidence in the author's voice. Use social-preview for visual assets and feed mockups."
---

# Social writing

Turn the user's material into a post people can understand without knowing the
project. This skill covers personal and product accounts; do not assume a
personal update should use Orbyn's product voice.

## Establish the message

Use the supplied notes, draft, screenshots, links or named source files. Read
existing voice/brand guidance in the requested project when available. Determine
the platform, intended reader, purpose and one useful point. Ask only when a
missing fact would change the message; otherwise state a reasonable assumption
and draft. Do not inspect unrelated accounts or private material for inspiration.

For project announcements, distinguish implemented, locally checked, released
and publicly available. A screenshot or merged commit does not establish every
claim. Keep a short source note outside the post for material claims and unresolved
details. Never invent performance numbers, customer quotes, personal experiences
or a release date. Omit unsupported claims or mark them for the author to resolve.

## Write in the author's voice

Preserve supplied style examples and the user's chosen intent. Without examples,
start with plain, specific prose and restrained formatting; identify this as a
starting voice rather than a learned personal profile. Do not save a personal
profile or alter memory unless requested.

Open with the concrete event, problem or observation. Explain what happened,
why it matters to this reader, and the relevant evidence or limitation. Choose a
natural ending: the takeaway, a useful link, or a question the author actually
wants answered. Avoid invented drama, exaggerated launches, generic inspiration,
forced contrarian hooks and requests for empty engagement. Apply
[unslop](../unslop/SKILL.md) for a prose pass while retaining the author's voice.

Offer distinct angles when the user is exploring; when they request one finished
post, deliver one. Adapt the substance for each platform instead of mechanically
shortening the same text. Preserve useful paragraph breaks. Use hashtags, emoji
and calls to action only when they suit the author and purpose.

For carousels, choose a narrative suited to the evidence: problem → explanation
→ example → takeaway, or a short demonstration. Give each slide one job and a
clear reading order. Write slide text, visual intent and alt text together.
Do not stretch a small point into an arbitrary slide count.

## Handoff and boundaries

Deliver copyable post text plus only the alternatives, claim notes or visual brief
needed for the request. Keep editorial notes out of the copyable post. For images,
carousels or a feed preview, pass the chosen copy, audience, brand assets, slide
order and evidence limits to [social-preview](../social-preview/SKILL.md).
Use its [brief format](../social-preview/references/production.md) when running
the bundled renderer; do not require that format for ordinary writing.

Use [product content design](../orbyn-content-design/SKILL.md) for in-app labels
and help. Use [UI design](../orbyn-ui-design/SKILL.md) for changes to the product
itself. A slide outline is not a rendered carousel. A content calendar is a draft
plan, not a scheduled automation. Publishing, scheduling, comments and messages
require the user's applicable instruction; preparing content does not perform them.

Check current primary platform guidance when a request depends on exact upload
limits, format support or other changing rules. Do not present posting frequency,
algorithm tricks or a preview's truncation as established platform behavior.
Research context and source distinctions live in the
[source record](../../tools/research/social-content.md).