Dev Social Media Skill: Turning Developer Progress Into Public Updates

I built Dev Social Media Skill because I want to spread my project ideas more efficiently. When I am building several products at the same time, there is suddenly a lot to share: new experiments, workflow changes, product ideas, and implementation details.

The hard part is not only writing. It is switching context away from the project, deciding what matters, adapting the update for different platforms, preparing screenshots, and then pushing or scheduling the post.

The skill helps an AI coding agent inspect a project, understand what shipped, draft platform-specific posts, recommend screenshots, and create or schedule posts through Typefully after approval.

It is designed for developers who already work with Codex, Claude Code, OpenCode, or similar agents. Instead of leaving the coding workflow to write updates manually, the same agentic workflow can help turn the actual project context into a public update.

The fastest way to try it is to install the skill from the public GitHub repo. The workflow is intentionally simple: install the skill, set a Typefully token if you want remote draft creation, dry-run the payload, then create or schedule only after review.

npx skills install https://github.com/Shellishack/dev-social-media-skill

The Typefully helper reads one credential from the environment: TYPEFULLY_API_TOKEN. The token should not be pasted into drafts, screenshots, repo files, or command arguments.

[Environment]::SetEnvironmentVariable("TYPEFULLY_API_TOKEN", "your-token", "User")
$env:TYPEFULLY_API_TOKEN = [Environment]::GetEnvironmentVariable("TYPEFULLY_API_TOKEN", "User")

export TYPEFULLY_API_TOKEN="your-token"

When the update is visual, the skill can capture screenshots from a local or deployed URL. This makes the post more concrete because the social update can include proof of what shipped instead of only text.

node ./scripts/capture-screenshots.ts --url http://127.0.0.1:3000 --out C:/tmp/social-release --name app-release

node ./scripts/capture-screenshots.ts --url http://127.0.0.1:3000 --out C:/tmp/social-release --name app-preview --click ".preview-button"

The script dry-runs by default. That matters because social publishing is an external side effect. I want the agent to show the text, platforms, media, and timing before creating anything remotely.

After review, the same command can create a Typefully draft, schedule it for a future time, or publish immediately when explicitly approved.

node ./scripts/publish-typefully.ts --text "Shipping a new product update today." --platforms x,linkedin

node ./scripts/publish-typefully.ts --file C:/tmp/social-release/post.md --platforms x,linkedin --create

node ./scripts/publish-typefully.ts --file C:/tmp/social-release/post.md --platforms x,linkedin --publish-at 2026-06-03T01:00:00Z --create

node ./scripts/publish-typefully.ts --file C:/tmp/social-release/post.md --platforms x,linkedin --publish-at now --create

For X threads, the skill uses a simple separator: a line containing three or more dashes. That keeps the draft readable in a Markdown file while still giving the publishing helper enough structure to build a thread.

First post.
---
Second post.

This is not a generic content machine. I am still the person behind the post: I decide what I built, what matters, what is private, what is not ready, and what I want to say.

The skill automates the slow operational part around that: drafting, adapting text for X and LinkedIn, preparing screenshots, dry-running Typefully payloads, and scheduling only after explicit approval.

GitHub repo: https://github.com/Shellishack/dev-social-media-skill