Skill detail

social-media-publishing

Publishes LinkedIn posts but is a broader distribution workflow.

MatchPossibleReviewed for linkedin posts
Sourcewisdom-in-a-nutshell/agentsExternal source
Reported installs19Popularity signal only

Inspect before use

Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: social-media-publishing
description: Multi-channel social publishing workflow plus blog-post publication prep and channel CLIs for Reddit, LinkedIn, X, YouTube, Instagram, and TikTok. Use when Codex needs to publish or distribute a blog post, video, launch, or visual explainer; prepare blog assets; decide between gallery, image, self, link, or native video format; publish the source post before distribution; post to Reddit; publish LinkedIn text/link/image/video posts; post X text/video posts; or prepare Instagram/TikTok posts through dry-run channel CLIs.
---

# Social Media Publishing

## Overview

Use this skill to package publishing and distribution work as a reusable workflow instead of repo-specific one-offs.

Keep campaign assets in the active project. Keep durable repo-specific publishing conventions in the owning repo. The current bundled channel helpers cover Reddit, LinkedIn, X, Modal-backed YouTube uploads, and initial dry-run scaffolds for Instagram and TikTok.

## Workflow

1. Decide whether the content needs to be published at the source first, for example in a blog repo.
2. Keep campaign state in the active repo, not in this skill.
3. Choose the post shape with the user first: gallery, self, link, or image.
4. Inspect subreddit flairs before posting when flair is required or likely to matter.
5. Prefer a plan file for repeatable or multi-step posts.
6. Dry-run the plan before live submission when paths, long comments, or strict communities are involved.
7. After posting, update the project-local tracker with the post URL, comment URL, and moderation outcome.
8. For source-post workflows, default to publishing the post publicly (set `hidden: false` in frontmatter unless the user explicitly asks for a private/draft post).

## Blog-backed publishing

If the user asks to publish the source post itself before distribution, read:
- `references/blog/publishing.md`

Keep durable repo-specific publishing mechanics in the owning repo and in the reference file, not in this top-level skill body.

## Reddit

Use the bundled CLI at `scripts/reddit/cli.py`.

For live commands and plan structure, read:
- `references/reddit/workflow.md`
- `references/reddit/plan-schema.md`

If the content is Codex / App Server / coding-agent-internals related and you expect repeated Reddit distribution, also read:
- `references/reddit/topics/codex.md`

Core commands:

```bash
python3 ~/GitHub/agents/skills-source/owned/social-media-publishing/scripts/reddit/cli.py status
python3 ~/GitHub/agents/skills-source/owned/social-media-publishing/scripts/reddit/cli.py list-flairs --subreddit OpenAI
python3 ~/GitHub/agents/skills-source/owned/social-media-publishing/scripts/reddit/cli.py list-submissions --max-items 20 --days 7
python3 ~/GitHub/agents/skills-source/owned/social-media-publishing/scripts/reddit/cli.py comment --post-url https://reddit.com/r/OpenAI/comments/abc123/example/ --text-file /abs/path/comment.md --dry-run
python3 ~/GitHub/agents/skills-source/owned/social-media-publishing/scripts/reddit/cli.py submit-plan --plan /abs/path/post-plan.json --dry-run
python3 ~/GitHub/agents/skills-source/owned/social-media-publishing/scripts/reddit/cli.py submit-plan --plan /abs/path/post-plan.json
```

The CLI supports:
- flair discovery
- gallery submission
- image submission
- link submission
- self-post submission
- optional first-comment posting
- standalone commenting on existing posts
- authenticated submission history lookup

## LinkedIn

Use the bundled LinkedIn CLI at `scripts/linkedin/cli.py` for local LinkedIn publishing.

Read first:
- `references/linkedin/posting.md`
- `references/linkedin/copy.md`

If LinkedIn app product access changes, company pages are involved, or analytics/read-back is needed:
- `references/linkedin/community-management.md`

Only if setup or re-auth is needed:
- `references/linkedin/auth.md`

Current supported flow:
- local OAuth authorization
- Community Management API scope presets and capability probes
Read the full source on GitHub (opens external page)
Context

Related work