---

name: typefully description: Create, schedule, list, edit, and delete drafts on Typefully. Supports single tweets, threads, and multi-platform posts (X, LinkedIn, Threads, Bluesky, Mastodon). Use when user wants to draft, schedule, or manage social media posts via Typefully. version: 1.2.0 homepage: https://github.com/gisk0/typefully-skill requires: env: - TYPEFULLY_API_KEY tools: - curl - python3

Typefully Skill

Manage Typefully drafts via the v2 API.

Setup

1. Set your API key via one of:
   • Environment variable: export TYPEFULLY_API_KEY=your-key
   • Password store: pass insert typefully/api-key
2. (Optional) Set your social set ID:
   • Environment variable: export TYPEFULLY_SOCIAL_SET_ID=123456
   • Password store: pass insert typefully/social-set-id
   • If not set, the script auto-detects (errors if multiple accounts exist — use list-social-sets to find yours)
3. Enable "Development mode" in Typefully Settings → API to see draft IDs in the UI.

Script Usage

bash scripts/typefully.sh <command> [options]

Commands

Examples

Create a simple tweet draft:

bash scripts/typefully.sh create-draft "Just shipped a new feature 🚀"

Create a thread:

bash scripts/typefully.sh create-draft "First tweet of the thread\n---\nSecond tweet\n---\nThird tweet" --thread

Create a thread from stdin (for longer content):

cat <<'EOF' | bash scripts/typefully.sh create-draft - --thread
First tweet of the thread\n---\nSecond tweet\n---\nThird tweet with the punchline
EOF

Create cross-platform draft (X + LinkedIn):

bash scripts/typefully.sh create-draft "Exciting update!" --platform x,linkedin

Schedule a draft for a specific time:

bash scripts/typefully.sh create-draft "Morning thoughts ☀️" --schedule "2026-03-01T09:00:00Z"

Schedule to next free slot:

bash scripts/typefully.sh schedule-draft 8196074 next-free-slot

List recent drafts:

bash scripts/typefully.sh list-drafts draft 5

Notes

• publish_at: "now" publishes immediately — use with caution
• publish_at: "next-free-slot" uses the user's Typefully queue schedule
• Thread posts are separated by \n---\n in the text argument
• The script outputs JSON; pipe through jq for formatting
• All API errors surface meaningful messages (401, 404, 429, etc.)