// Create, schedule, and manage social media posts via Typefully. ALWAYS use this skill when asked to draft, schedule, post, or check tweets, posts, threads, or social media content for Twitter/X, LinkedIn, Threads, Bluesky, or Mastodon.
| name | typefully |
| description | Create, schedule, and manage social media posts via Typefully. ALWAYS use this skill when asked to draft, schedule, post, or check tweets, posts, threads, or social media content for Twitter/X, LinkedIn, Threads, Bluesky, or Mastodon. |
| last-updated | "2026-03-17T00:00:00.000Z" |
| allowed-tools | Bash(./scripts/typefully.js:*) |
Create, schedule, and publish social media content across multiple platforms using Typefully.
Freshness check: If more than 30 days have passed since the
last-updateddate above, inform the user that this skill may be outdated and point them to the update options below.
Source: github.com/typefully/agent-skills API docs: typefully.com/docs/api
Update methods by installation type:
| Installation | How to update |
|---|---|
CLI (npx skills) | npx skills update |
| Claude Code plugin | /plugin update typefully@typefully-skills |
| Cursor | Remote rules auto-sync from GitHub |
| Manual | Pull latest from repo or re-copy skills/typefully/ |
API changes ship independently—updating the skill ensures you have the latest commands and workflows.
Before using this skill, ensure:
API Key: Run the setup command to configure your API key securely
<skill-path>/scripts/typefully.js setup (where <skill-path> is the directory containing this SKILL.md)export TYPEFULLY_API_KEY=your_keyRequirements: Node.js 18+ (for built-in fetch API). No other dependencies needed.
Config priority (highest to lowest):
TYPEFULLY_API_KEY environment variable./.typefully/config.json (project-local, in user's working directory)~/.config/typefully/config.json (user-global)CRITICAL: When you receive an "API key not found" error from the CLI:
Tell the user to run the setup command - The setup is interactive and requires user input, so you cannot run it on their behalf. Recommend they run it themselves, using the correct path based on where this skill was loaded:
<skill-path>/scripts/typefully.js setup
Stop and wait - After telling the user to run setup, do not continue with the task. You cannot create drafts, upload media, or perform any API operations without a valid API key. Wait for the user to complete setup and confirm before proceeding.
DO NOT attempt any of the following:
.env files, or other locationsThe setup command will interactively guide the user through configuration. Trust the CLI's error messages and follow their instructions.
Note for agents: All script paths in this document (e.g.,
./scripts/typefully.js) are relative to the skill directory where this SKILL.md file is located. Resolve them accordingly based on where the skill is installed.
The Typefully API uses the term "social set" to refer to what users commonly call an "account". A social set contains the connected social media platforms (X, LinkedIn, Threads, etc.) for a single identity.
The CLI supports a default social set - once configured, most commands work without specifying the social_set_id.
You can pass the social set either way:
drafts:list 123drafts:list --social-set-id 123 (also supports --social_set_id)When determining which social set to use:
Check for a configured default first - Run config:show to see if a default is already set:
./scripts/typefully.js config:show
If default_social_set is configured, the CLI uses it automatically when you omit the social_set_id.
Check project context - Look for configuration in project files like CLAUDE.md or AGENTS.md:
## Typefully
Default social set ID: 12345
Single social set shortcut - If the user only has one social set and no default is configured, use it automatically
Multiple social sets, no default - Ask the user which to use, then offer to save their choice as the default:
./scripts/typefully.js config:set-default
This command lists available social sets and saves the choice to the config file.
Reuse previously resolved social set - If determined earlier in the session, use it without asking again
| User says... | Action |
|---|---|
| "Draft a tweet about X" | drafts:create --text "..." (uses default social set) |
| "Post this to LinkedIn" | drafts:create --platform linkedin --text "..." |
| "Mention a company on LinkedIn" | linkedin:organizations:resolve --organization-url "<linkedin_url>" then use returned mention_text in drafts:create |
| "Post to X and LinkedIn" (same content) | drafts:create --platform x,linkedin --text "..." |
| "X thread + LinkedIn post" (different content) | Create one draft, then drafts:update to add platform (see Publishing to Multiple Platforms) |
| "What's scheduled?" | drafts:list --status scheduled |
| "Show my recent posts" | drafts:list --status published |
| "Schedule this for tomorrow" | drafts:create ... --schedule "2025-01-21T09:00:00Z" |
| "Post this now" | drafts:create ... --schedule now or drafts:publish <draft_id> --use-default |
| "Add notes/ideas to the draft" | drafts:create ... --scratchpad "Your notes here" |
| "Check available tags" | tags:list |
| "Show my X post analytics for last week" | analytics:posts:list --start-date YYYY-MM-DD --end-date YYYY-MM-DD |
| "Show my X post analytics including replies" | analytics:posts:list --start-date YYYY-MM-DD --end-date YYYY-MM-DD --include-replies |
| "Show my queue for next week" | queue:get --start-date YYYY-MM-DD --end-date YYYY-MM-DD |
Follow this workflow when creating posts:
Check if a default social set is configured:
./scripts/typefully.js config:show
If default_social_set shows an ID, skip to step 3.
If no default, list social sets to find available options:
./scripts/typefully.js social-sets:list
If multiple exist, ask the user which to use and offer to set it as default:
./scripts/typefully.js config:set-default
Create drafts (social_set_id is optional if default is configured):
./scripts/typefully.js drafts:create --text "Your post"
Note: If --platform is omitted, the first connected platform is auto-selected.
For multi-platform posts: See Publishing to Multiple Platforms — always use a single draft, even when content differs per platform.
Schedule or publish as needed
Tags help organize drafts within Typefully. Always check existing tags before creating new ones:
List existing tags first:
./scripts/typefully.js tags:list
Use existing tags when available - if a tag with the desired name already exists, use it directly when creating drafts:
./scripts/typefully.js drafts:create --text "..." --tags existing-tag-name
Only create new tags if needed - if the tag doesn't exist, create it:
./scripts/typefully.js tags:create --name "New Tag"
Important: Tags are scoped to each social set. A tag created for one social set won't appear in another.
If a single draft needs to be created for different platforms, you need to make sure to create a single draft and not multiple drafts.
When the content is the same across platforms, create a single draft with multiple platforms:
# Specific platforms
./scripts/typefully.js drafts:create --platform x,linkedin --text "Big announcement!"
# All connected platforms
./scripts/typefully.js drafts:create --all --text "Posting everywhere!"
IMPORTANT: When content should be tailored (e.g., X thread with a LinkedIn post version), still use a single draft — create with one platform first, then update to add the other:
# 1. Create draft with the primary platform first
./scripts/typefully.js drafts:create --platform linkedin --text "Excited to share our new feature..."
# Returns: { "id": "draft-123", ... }
# 2. Update the same draft to add another platform with different content
./scripts/typefully.js drafts:update draft-123 --platform x --text "🧵 Thread time!
---
Here's what we shipped and why it matters..." --use-default
So make sure to NEVER create multiple drafts unless the user explicitly wants separate drafts for each platform.
LinkedIn mentions are supported via text syntax inside post content:
@[Company Name](urn:li:organization:123456)
Use the resolver command to convert a public LinkedIn organization URL into ready-to-paste mention syntax:
# Resolve a LinkedIn URL into mention metadata
./scripts/typefully.js linkedin:organizations:resolve --organization-url "https://www.linkedin.com/company/typefullycom/"
# Returns mention_text like: @[Typefully](urn:li:organization:86779668)
Then include that mention_text in your LinkedIn draft text:
./scripts/typefully.js drafts:create --platform linkedin --text "Thanks @[Typefully](urn:li:organization:86779668) for the support."
| Command | Description |
|---|---|
me:get | Get authenticated user info |
social-sets:list | List all social sets you can access |
social-sets:get <id> | Get social set details including connected platforms |
linkedin:organizations:resolve [social_set_id] --organization-url <url> | Resolve LinkedIn company/school URL into mention metadata (mention_text, urn) |
All analytics commands support an optional [social_set_id] - if omitted, the configured default is used.
The public API currently supports X post analytics only on this endpoint. The CLI defaults --platform to x, so you can usually omit it.
Replies are now excluded by default so the result set matches the main published-post view more closely. Add --include-replies when you explicitly want reply posts included.
Analytics responses return post-level metrics for the requested inclusive date range, including:
impressionslikes, comments, shares, quotes, saves, profile_clicks, and link_clicks| Command | Description |
|---|---|
analytics:posts:list [social_set_id] --start-date <YYYY-MM-DD> --end-date <YYYY-MM-DD> | List X posts with normalized analytics metrics for an inclusive date range |
analytics:posts:list ... --start_date <YYYY-MM-DD> --end_date <YYYY-MM-DD> | Snake case aliases for date flags (copied from API docs) |
analytics:posts:list ... --include-replies | Include X replies in the results (excluded by default) |
analytics:posts:list ... --include_replies | Snake case alias for the include-replies flag |
analytics:posts:list ... --limit 100 --offset 25 | Paginate through results |
analytics:posts:list ... --platform x | Explicitly request X analytics (currently the only supported platform) |
All drafts commands support an optional [social_set_id] - if omitted, the configured default is used.
Safety note: For commands that take [social_set_id] <draft_id>, if you pass only a single argument (the draft_id) while a default social set is configured, you must add --use-default to confirm intent.
| Command | Description |
|---|---|
drafts:list [social_set_id] | List drafts (add --status scheduled to filter, --sort to order) |
drafts:get [social_set_id] <draft_id> | Get a specific draft with full content (single-arg requires --use-default if a default is configured) |
drafts:create [social_set_id] --text "..." | Create a new draft (auto-selects platform) |
drafts:create [social_set_id] --platform x --text "..." | Create a draft for specific platform(s) |
drafts:create [social_set_id] --all --text "..." | Create a draft for all connected platforms |
drafts:create [social_set_id] --file <path> | Create draft from file content |
drafts:create ... --media <media_ids> | Attach media. , separates ids on the same post; | delimits per-post groups in a thread (mirrors how --- delimits text). |
drafts:create ... --reply-to <url> | Reply to an existing X post |
drafts:create ... --community <id> | Post to an X community |
drafts:create ... --quote-post-url <url> | Quote an existing X post URL |
drafts:create ... --share | Generate a public share URL for the draft |
drafts:create ... --scratchpad "..." | Add internal notes/scratchpad to the draft |
drafts:update [social_set_id] <draft_id> --text "..." | Update an existing draft (single-arg requires --use-default if a default is configured) |
drafts:update ... --quote-post-url <url> | Update X post(s) in a draft to quote an existing post URL |
drafts:update [social_set_id] <draft_id> --tags "tag1,tag2" | Update tags on an existing draft (content unchanged) |
drafts:update ... --share | Generate a public share URL for the draft |
drafts:update ... --scratchpad "..." | Update internal notes/scratchpad |
drafts:update [social_set_id] <draft_id> --append --text "..." | Append to existing thread |
Safety note: These commands require --use-default when using the default social set with a single argument (to prevent accidental operations from ambiguous syntax).
| Command | Description |
|---|---|
drafts:delete <social_set_id> <draft_id> | Delete a draft (explicit IDs) |
drafts:delete <draft_id> --use-default | Delete using default social set |
drafts:schedule <social_set_id> <draft_id> --time next-free-slot | Schedule to next available slot |
drafts:schedule <draft_id> --time next-free-slot --use-default | Schedule using default social set |
drafts:publish <social_set_id> <draft_id> | Publish immediately |
drafts:publish <draft_id> --use-default | Publish using default social set |
All queue commands support an optional [social_set_id] - if omitted, the configured default is used.
The queue is a social-set-specific timeline made of:
Use queue:get when the user asks what is already scheduled (or free) for a given account in a date range.
| Command | Description |
|---|---|
queue:get [social_set_id] --start-date <YYYY-MM-DD> --end-date <YYYY-MM-DD> | Get the queue timeline for one social set: free queue slots plus scheduled drafts/posts in a date range |
queue:get ... --start_date <YYYY-MM-DD> --end_date <YYYY-MM-DD> | Snake case aliases for date flags (copied from API docs) |
queue:schedule:get [social_set_id] | Get queue schedule rules |
queue:schedule:put [social_set_id] --rules '[{"h":9,"m":30,"days":["mon","wed","fri"]}]' | Replace queue schedule rules (full replacement) |
| Command | Description |
|---|---|
tags:list [social_set_id] | List all tags |
tags:create [social_set_id] --name "Tag Name" | Create a new tag |
| Command | Description |
|---|---|
media:upload [social_set_id] <file_path> | Upload media, wait for processing, return ready media_id |
media:upload ... --no-wait | Upload and return immediately (use media:status to poll) |
media:upload ... --timeout <seconds> | Set custom timeout (default: 60) |
media:status [social_set_id] <media_id> | Check media upload status |
| Command | Description |
|---|---|
setup | Interactive setup - prompts for API key, storage location, and default social set |
setup --key <key> --location <global|local> | Non-interactive setup for scripts/CI (auto-selects default if only one social set) |
setup --key <key> --default-social-set <id> | Non-interactive setup with explicit default social set |
setup --key <key> --no-default | Non-interactive setup, skip default social set selection |
config:show | Show current config, API key source, and default social set |
config:set-default [social_set_id] | Set default social set (interactive if ID omitted) |
# Check current config
./scripts/typefully.js config:show
# Set default (interactive - lists available social sets)
./scripts/typefully.js config:set-default
# Set default (non-interactive)
./scripts/typefully.js config:set-default 123 --location global
./scripts/typefully.js drafts:create --text "Hello, world!"
./scripts/typefully.js drafts:create 123 --text "Hello, world!"
./scripts/typefully.js drafts:create --platform x,linkedin,threads --text "Big announcement!"
./scripts/typefully.js linkedin:organizations:resolve --organization-url "https://www.linkedin.com/company/typefullycom/"
./scripts/typefully.js drafts:create --platform linkedin --text "Thanks @[Typefully](urn:li:organization:86779668) for the support."
./scripts/typefully.js drafts:create --all --text "Posting everywhere!"
./scripts/typefully.js drafts:create --text "Scheduled post" --schedule next-free-slot
./scripts/typefully.js drafts:create --text "Marketing post" --tags marketing,product
./scripts/typefully.js drafts:list --status scheduled --sort scheduled_date
./scripts/typefully.js queue:get --start-date 2026-02-01 --end-date 2026-02-29
./scripts/typefully.js analytics:posts:list --start-date 2026-03-01 --end-date 2026-03-07
./scripts/typefully.js analytics:posts:list --start-date 2026-03-01 --end-date 2026-03-07 --include-replies
./scripts/typefully.js analytics:posts:list --start-date 2026-03-01 --end-date 2026-03-31 --limit 100 --offset 100
./scripts/typefully.js queue:schedule:get
./scripts/typefully.js queue:schedule:put --rules '[{"h":9,"m":30,"days":["mon","wed","fri"]}]'
./scripts/typefully.js drafts:create --platform x --text "Great thread!" --reply-to "https://x.com/user/status/123456"
./scripts/typefully.js drafts:create --platform x --text "Community update" --community 1493446837214187523
./scripts/typefully.js drafts:create --platform x --text "My take on this" --quote-post-url "https://x.com/user/status/1234567890123456789"
./scripts/typefully.js drafts:update 456 --platform x --quote-post-url "https://x.com/user/status/1234567890123456789" --use-default
./scripts/typefully.js drafts:create --text "Check this out" --share
./scripts/typefully.js drafts:create --text "Launching next week!" --scratchpad "Draft for product launch. Coordinate with marketing team before publishing."
# Single command handles upload + polling - returns when ready!
./scripts/typefully.js media:upload ./image.jpg
# Returns: {"media_id": "abc-123-def", "status": "ready", "message": "Media uploaded and ready to use"}
# Create post with the media attached
./scripts/typefully.js drafts:create --text "Check out this image!" --media abc-123-def
# Upload each file (each waits for processing)
./scripts/typefully.js media:upload ./photo1.jpg # Returns media_id: id1
./scripts/typefully.js media:upload ./photo2.jpg # Returns media_id: id2
# Create post with multiple media on one post (comma-separated)
./scripts/typefully.js drafts:create --text "Photo dump!" --media id1,id2
Use | to delimit per-post media groups, mirroring how --- delimits text into a thread. Each |-separated group is attached to the post at the matching index. Within a group, , still attaches multiple media to the same post.
# Thread of 3 posts, one image per post:
./scripts/typefully.js drafts:create --platform x --media id1,id2,id3 --text "Intro post
---
Middle post
---
Final post"
# Wait — that comma form attaches all three to post 0. Use `|` instead:
./scripts/typefully.js drafts:create --platform x --media "id1|id2|id3" --text "Intro post
---
Middle post
---
Final post"
# Mix multiple media on one post and skip another post:
./scripts/typefully.js drafts:create --media "a,b||c" --text "Two images here
---
This post has no media
---
One image on the last post"
A single comma-only spec (no |) keeps the historical behavior of attaching to post 0 only.
# Upload media
./scripts/typefully.js media:upload ./new-image.jpg # Returns media_id: xyz
# Update draft with media (456 is the draft_id)
./scripts/typefully.js drafts:update 456 --text "Updated post with image" --media xyz --use-default
./scripts/typefully.js setup
# Auto-selects default social set if only one exists
./scripts/typefully.js setup --key typ_xxx --location global
# With explicit default social set
./scripts/typefully.js setup --key typ_xxx --location global --default-social-set 123
# Skip default social set selection entirely
./scripts/typefully.js setup --key typ_xxx --no-default
Use these exact names for the --platform option:
x - X (formerly Twitter)linkedin - LinkedInthreads - Threadsbluesky - Blueskymastodon - MastodonTypefully draft URLs contain the social set and draft IDs:
https://typefully.com/?a=<social_set_id>&d=<draft_id>
Example: https://typefully.com/?a=12345&d=67890
a=12345 → social_set_idd=67890 → draft_idWhen the user explictly asked to add notes, ideas, or anything else in the draft scratchpad, use the --scratchpad flag—do NOT write to local files!
The --scratchpad option attaches internal notes directly to the Typefully draft. These notes:
# CORRECT: Notes attached to the draft in Typefully
./scripts/typefully.js drafts:create 123 --text "My post" --scratchpad "Ideas for expanding: 1) Add stats 2) Include quote"
# WRONG: Do NOT write notes to local files when the user wants them in Typefully
# Writing to /tmp/scratchpad/ or any local file is NOT the same thing
When automating posts, especially on X, follow these rules to keep accounts in good standing:
When in doubt, create drafts for user review rather than publishing directly.
Publishing confirmation: Unless the user explicitly asks to "publish now" or "post immediately", always confirm before publishing. Creating a draft is safe; publishing is irreversible and goes public instantly.
--platform is omitted, the first connected platform is auto-selected--all to post to all connected platforms at once@[Name](urn:li:organization:ID) in post text; resolve IDs via linkedin:organizations:resolve--- on its own line to split into multiple posts (thread)next-free-slot to let Typefully pick the optimal time--platform x,linkedin--title for internal organization (not posted to social media)--scratchpad to attach notes to the draft in Typefully (NOT local files!) - perfect for thread ideas, research, contextanalytics:posts:list --start-date ... --end-date ... to fetch post metrics for a social set; replies are excluded by default, and --include-replies opts back in--file ./post.txt instead of --text to read content from a file--sort with values like created_at, -created_at, scheduled_date, etc.Update Spatie package documentation on spatie.be by re-importing docs for a given repo. Use after merging a PR that touches docs/, or when the user says 'update docs for [package]', 'rebuild docs for [repo]', 'import docs for [repo]', or invokes /update-spatie-docs [repo-name]. Takes a repo name argument (e.g., 'backup', 'laravel-medialibrary', 'laravel-pdf').
Generate beautiful code snippet images (PNG) for social media, tweets, LinkedIn, and documentation. Creates light-themed, macOS-style window chrome screenshots from code using HTML templates and Chrome headless. Use when asked to create code images, tweet images, snippet screenshots, code cards, or visual code examples for sharing. Supports single snippets, multi-image sets, and 2x2 grid composites.
Flux UI component library for Livewire. Use when building UIs with Flux components like buttons, inputs, modals, tables, forms, navigation, or any Livewire interface using the flux: Blade component prefix. Triggers include "Flux component", "flux:button", "flux:input", "Livewire UI components", or building admin/dashboard interfaces.
Create and schedule link posts on freek.dev blog. Use when asked to publish, post, or share a link on freek.dev. Handles post creation, updating, and scheduling via the blog API.
Laravel PHP framework conventions and best practices. Use when building Laravel applications, writing controllers, models, migrations, routes, middleware, form requests, policies, jobs, events, or any Laravel-specific code. Triggers include "Laravel", "Eloquent", "Artisan", "php artisan", routing, migrations, or working with Laravel projects.
Build Livewire 4 components and applications. Use when creating reactive Laravel interfaces, single-file components, multi-file components, page components, forms, actions, or any Livewire-based UI. Triggers include "Livewire component", "wire:model", "wire:click", building interactive Laravel UIs, or working with Livewire 4 projects.