Use social to turn an article, podcast, or product explanation into social content, or to plan a sustainable publishing rhythm. It starts with audience, platform, objective, and available time. The useful output is a reviewable set of drafts and production requirements, rather than automatic posting everywhere.
Install and invoke
Run this in your project terminal to install only this skill for Claude Code:
npx skills add coreyhaines31/marketingskills --skill social -a claude-code
Node.js and npx must be available. For Codex, replace -a claude-code with -a codex. In the agent conversation, explicitly ask it to use social and supply your material. The installation command belongs in the terminal, not in your content brief.
Begin with a useful source
Provide a complete article or timestamped transcript, not just a title and a request to go viral. Explain whether this is a personal or company account, the main platforms, and weekly capacity. Product context can come from .agents/product-marketing.md.
Example brief:
Use social to adapt workshop.md into one week of LinkedIn and X drafts.
The audience is design-team leaders. Limit each platform to three posts. First find five self-contained insights.
For each draft, give the source location, opening, body, action, and required visual. Preserve the speaker’s qualifications.
Turn one idea into a six-slide carousel outline. Draft only.
Choose the content units before writing posts. A unit may be a complete short story, actionable method, or sourced finding. Removing a sentence from its surroundings must not change its meaning. Each post needs enough context to work for someone who has not seen the original article or previous posts.
Make the production plan executable
For carousels, choose the narrative structure before assigning information to individual slides. Repeating one claim across different layouts is not a useful sequence. For short video, separate visual action, narration, and captions. Keep source timestamps when actual clips are required; a written script is not edited footage.
Leave time in the calendar for replies and timely material. The repository provides frequency examples, but a small team should not copy a high-volume schedule it cannot maintain. First-person stories, customer outcomes, and figures must come from your supplied evidence rather than be invented for a stronger hook.
If every platform receives almost identical text, ask the agent to explain the audience and intended action for each, then adapt the format. During review, distinguish reach from saves, replies, visits, and business outcomes. One popular post does not establish reliable acquisition. Check links, facts, and context before returning older material to the queue.
Turn one source into genuinely standalone posts
Give the skill an article, podcast notes, or event record you have permission to use. Extract points, examples, steps, and possible visuals that can stand alone. Ask of each candidate, “Would a reader understand this without the original?” One article can support several angles, but cropping its opening into an X post and adding an emoji does not create an Instagram piece. Adapt the hook, length, and call to action to the platform’s audience and available media.
A product-launch retrospective might become one decision lesson on X, a team tradeoff on LinkedIn, and a short video showing one real operation. If no real screenshot or licensed footage exists, request a shot list rather than filling the gap with invented imagery. Have the agent attach the source passage, required asset, and intended reader action to every draft so an editor can catch unsupported simplification.
Leave time to reply after scheduling. Social work is not only a publishing quota; repeated questions in comments can improve the original help article. Review useful replies, relevant site visits, and follow-up questions each week alongside reach. If people misunderstand the post, fix the framing or audience first instead of simply doubling frequency.
Example: turn webinar questions into next week’s content
A forty-minute product webinar has repeated questions about permissions. Provide a checked transcript, shareable timestamps, and speaker permission. Ask: “Use social to select three operational questions that make sense independently. Draft a short step-by-step X post, a LinkedIn post with context, and a shot list for a fifteen-second video. Do not clip half a sentence so it changes the meaning, and do not claim attendees successfully fixed their settings.”
Compare each draft with the original exchange. Are terms, limitations, and conditional statements preserved? If only a timestamp is available and the visuals have not been reviewed, the video deliverable is a proposed shot list, not verified footage. After publication, watch for the same confusion in replies. If it persists, improve the help page and link to it rather than repackaging the same incomplete answer again.
Match assets and review to channel risk
Do not paste the same text into every channel. Define each platform’s audience, available asset, desired action, and publishing owner, then extract distinct angles from the original material. Jeff Simmons, who manages 23 social profiles, relies on preapproved strategy rather than approving every post, but separately reviews potentially sensitive nightlife photos and uses monthly reports to change asset types. The operating rhythm is reusable; photo choice and publishing risk still require human judgment.
Phoebe Fu turned one of her Skill field notes into a LinkedIn story post, ten-slide carousel, eight-post X thread, 30-second video script and conversation prompt. Each draft has its own hook and information order. She had no historical engagement data, so she specified saves, comments and artifact visits to watch after posting. Start with two channels if five formats exceed your capacity.
Natan Abramov described using the predecessor social-content: he supplied a one-sentence idea, audience and desired action, got an initial draft and several hooks, then iterated on length, examples, tone and CTA. This page now uses social, so follow its current install command. His older post is most useful as a model for staged editing, not for copying the old name.