Social media strategy for developers including Twitter/X, LinkedIn, and community platforms
Generates platform-specific social media content for developers. Triggers when creating posts for Twitter/X, LinkedIn, YouTube, Reddit, or Discord with specified content types.
/plugin marketplace add pluginagentmarketplace/custom-plugin-devrel-engineer/plugin install devrel-engineer-plugin@pluginagentmarketplace-devrel-engineerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/content-calendar.yamlreferences/SOCIAL_GUIDE.mdscripts/social_scheduler.pyBuild developer-focused social media presence that drives engagement and community growth.
parameters:
required:
- platform: enum[twitter, linkedin, youtube, reddit, discord]
- content_type: enum[post, thread, video, story]
optional:
- topic: string
- campaign: string
output:
content:
text: string
hashtags: array[string]
media_specs: object
scheduling: datetime
| Platform | Audience | Content Type |
|---|---|---|
| Twitter/X | Developers, tech | Quick tips, threads |
| Professionals | Long-form, career | |
| YouTube | Learners | Tutorials, deep dives |
| Communities | Discussions, Q&A | |
| Discord | Real-time | Support, community |
Tweet 1: Hook (problem/question)
Tweet 2-5: Main content (tips/steps)
Tweet 6: Summary + CTA
Strong opening line (hook)
Short paragraphs.
Use line breaks liberally.
• Bullet points work well
• Easy to scan
End with question or CTA
#relevanthashtags (3-5 max)
| Day | Platform | Content |
|---|---|---|
| Mon | Weekly thread | |
| Tue | Industry insight | |
| Wed | Quick tip | |
| Thu | Personal story | |
| Fri | Fun/community |
retry_patterns:
low_engagement:
strategy: "Adjust timing, improve hook"
algorithm_change:
strategy: "Adapt content format"
negative_feedback:
strategy: "Address directly, learn"
| Failure Mode | Detection | Recovery |
|---|---|---|
| Low reach | <avg impressions | Boost with engagement |
| Negative response | Comments | Address, apologize if needed |
| Account issues | Restricted | Contact support |
□ Content aligned with platform?
□ Optimal posting time?
□ Hashtags relevant?
□ Media formatted correctly?
□ Links working?
□ CTA clear?
test_social_media:
unit_tests:
- test_content_format:
assert: "Meets platform specs"
- test_links_work:
assert: "All links resolve"
integration_tests:
- test_engagement:
assert: "Above baseline rate"
metrics:
- posts_published: integer
- engagement_rate: float
- follower_growth: integer
- reach: integer
See assets/ for content templates.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.