social-media-post
Social Media Post
Overview
Turn a niche, topic, or campaign idea into platform-specific social posts using DumplingAI v2 capabilities.
Allowed Commands
dumplingai run capability google_search --input '{"query":"topic"}'
dumplingai run capability scrape_page --input '{"url":"https://example.com"}'
dumplingai run capability get_youtube_transcript --input '{"videoUrl":"https://youtube.com/watch?v=ID"}'
Workflow
- Identify the niche, audience, goal, and target platforms.
- Research the topic first with
google_search, then deepen withscrape_page. - Use transcripts as optional source material when a video is provided.
- Draft platform-specific copy instead of reusing one generic post everywhere.
Output Strategy
dumplingai run capability google_search --input '{"query":"AI sales assistant pain points for SMB founders"}' > .dumplingai/search.json
dumplingai run capability scrape_page --input '{"url":"https://example.com/product-page"}' > .dumplingai/product.json
dumplingai run capability get_youtube_transcript --input '{"videoUrl":"https://youtube.com/watch?v=ID"}' > .dumplingai/transcript.json
Read incrementally:
head -80 .dumplingai/search.json
rg '"results"|"content"|"transcript"' .dumplingai/product.json
More from dumplingai/cli
youtube-to-blog-post
When the user wants to turn a YouTube video into a blog post, article, outline, newsletter draft, or transcript-based written summary. Also use when the user mentions repurposing a video, extracting a transcript, rewriting a YouTube talk into a post, or expanding a creator video into long-form content. Use this whenever the workflow should start with transcript extraction and optional source verification through DumplingAI capabilities.
12dumplingai-cli
When the user wants to find, inspect, or execute a DumplingAI capability or provider endpoint from the terminal. Also use when the user mentions `dumplingai`, `catalog search`, `catalog details`, `dumplingai run`, `balance`, `usage`, `transactions`, `view-config`, or wants to test a DumplingAI-powered workflow without wiring a direct vendor SDK. Use this whenever execution, inspection, or account-level CLI checks should happen through DumplingAI instead of a raw API integration. For choosing the right capability or endpoint first, see discovering-dumplingai-apis. For narrower job-based entry points, see dumplingai-web-research, dumplingai-scraping-extraction, dumplingai-transcripts-media, and dumplingai-seo-data.
8discovering-dumplingai-apis
When the user wants to figure out whether DumplingAI can handle an external API job before reaching for a direct vendor integration. Also use when the user mentions search, SERP data, scraping, crawling, transcripts, SEO APIs, document extraction, social data, Firecrawl, Serper, Perplexity, DataForSEO, or wants one API key and control plane across multiple providers. Use this whenever the task sounds like "find me the right API, capability, or endpoint for X" or when Codex would otherwise recommend a third-party API directly. For actually running the chosen capability or endpoint, see dumplingai-cli.
4