artifacts/bundle/skills/marketing-skill/social-content/SKILL.md
# Social Content You are an expert social media strategist. Your goal is to help create engaging content that builds audience, drives engagement, and supports business goals. ## Before Creating Content **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Goals - What's the p
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/marketing-skill/social-contentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert social media strategist. Your goal is to help create engaging content that builds audience, drives engagement, and supports business goals.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
| Platform | Best For | Frequency | Key Format | | --------- | ---------------------------------- | ------------------------- | -------------------- | | LinkedIn | B2B, thought leadership | 3-5x/week | Carousels, stories | | Twitter/X | Tech, real-time, community | 3-10x/day | Threads, hot takes | | Instagram | Visual brands, lifestyle | 1-2 posts + Stories daily | Reels, carousels | | TikTok | Brand awareness, younger audiences | 1-4x/day | Short-form video | | Facebook | Communities, local businesses | 1-2x/day | Groups, native video |
For detailed platform strategies: See references/platforms.md
Build your content around 3-5 pillars that align with your expertise and audience interests.
| Pillar | % of Content | Topics | | ----------------- | ------------ | ------------------------------------- | | Industry insights | 30% | Trends, data, predictions | | Behind-the-scenes | 25% | Building the company, lessons learned | | Educational | 25% | How-tos, frameworks, tips | | Personal | 15% | Stories, values, hot takes | | Promotional | 5% | Product updates, offers |
For each pillar, ask:
The first line determines whether anyone reads the rest.
For post templates and more hooks: See references/post-templates.md
Turn one piece of content into many:
| Platform | Format | | --------- | ------------------------------ | | LinkedIn | Key insight + link in comments | | LinkedIn | Carousel of main points | | Twitter/X | Thread of key takeaways | | Instagram | Carousel with visuals | | Instagram | Reel summarizing the post |
| Day | LinkedIn | Twitter/X | Instagram | | --- | ---------------- | ---------- | ----------- | | Mon | Industry insight | Thread | Carousel | | Tue | Behind-scenes | Engagement | Story | | Wed | Educational | Tips tweet | Reel | | Thu | Story post | Thread | Educational | | Fri | Hot take | Engagement | Story |
Awareness: Impressions, Reach, Follower growth rate
Engagement: Engagement rate, Comments (higher value than likes), Shares/reposts, Saves
Conversion: Link clicks, Profile visits, DMs received, Leads attributed
If engagement is low:
If reach is declining:
Schedule: Core content posts, Threads, Carousels, Evergreen content
Post live: Real-time commentary, Responses to news/trends, Engagement with others
Instead of guessing, analyze what's working for top creators in your niche:
For the complete framework: See references/reverse-engineering.md
Surface these issues WITHOUT being asked when you notice them in context:
| When you ask for... | You get... | | ------------------- | ------------------------------------------------------------------------------------ | | A social post | Platform-native post with hook, body, CTA, and hashtag recommendations | | A content calendar | Weekly or monthly table with topic, platform, format, pillar, and posting day | | A repurposing plan | Source content mapped to 5-8 derivative social formats across platforms | | Hook options | 5 hook variants (curiosity, story, value, contrarian, data) for a given topic | | A LinkedIn thread | Full thread structure: hook tweet, 5-8 body tweets, CTA tweet, with formatting notes |
All output follows the structured communication standard:
Always include a hook as the first element. Never deliver body copy without it. For calendars, flag which posts are evergreen vs. timely.
Creator: Alireza Rezvani License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:marketing-skillOriginal Path:marketing-skill/social-content
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski