social
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add whyashthakker/estack --skill socialCompatible with
Supported agents
Write X posts, X threads, and LinkedIn posts with a clear point of view, in the user's own voice.
Names the subject in the first line, takes a debatable side on ideas (never on people), backs it with sourced facts, keeps links in the first reply, and scores each draft before offering it.
Use when the user asks to write, draft, or plan posts for X, Twitter, or LinkedIn, or to turn a blog post, launch, or news story into social posts.
| name | social |
| description | Write X posts, X threads, and LinkedIn posts with a clear point of view, in the user's own voice. Names the subject in the first line, takes a debatable side on ideas (never on people), backs it with sourced facts, keeps links in the first reply, and scores each draft before offering it. Use when the user asks to write, draft, or plan posts for X, Twitter, or LinkedIn, or to turn a blog post, launch, or news story into social posts. |
Goal: posts people share because they say something, not posts that are only correct.
Read the user's recent posts if they share them, or their site and bio. Note sentence length, how they open, words they use and never use. If you have nothing, write plain and direct, and ask for 3 sample posts next time.
For each story, write the claim in one sentence and who would disagree with it. If no one would disagree ("AI is changing everything"), it is not a point yet. Find one:
Take sides on ideas, products, company decisions, and hype. Never on people, groups, or protected traits. No insults. No claims of wrongdoing you cannot source.
Rules for both platforms:
ste100 (stock AI words, hype, "not X but Y" frames, em dash chains). Keep the user's voice; the STE sentence rules do not apply here.X single post: up to 280 characters, 2 to 4 short blocks, no hashtags (one at most). X thread: only when the story needs 3 to 7 beats. Each post stands alone and adds one thing. The last post is the takeaway. LinkedIn: 120 to 250 words. A story or a sharp claim to open, short paragraphs, one lesson. Media (image or short video) helps.
Vary the shape across a day: a take, a number with context, a reaction to a demo, a lesson learned, a real question.
Give each draft a score out of 100 and show the parts:
| Part | Max | Question |
|---|---|---|
| Point of view | 30 | Would a real share of readers argue with it? |
| Timing | 20 | Is the story rising now? |
| Fit | 20 | Does the hook work in one line for this platform and audience? |
| Gap | 15 | Has no one in this space posted this angle yet today? |
| Proof | 15 | Are the facts specific and sourced? |
Do not offer drafts under 55. Zero drafts is a valid answer.
For each draft: platform, the text, the first reply or comment (with links), the media to attach, and the score. Never post without the user's go-ahead.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsocialExecute the skills CLI command in your project's root directory to begin installation:
epx add whyashthakker/estack --skill socialFetches social from whyashthakker/estack and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/social
Restart Cursor to activate social. Access via /socialin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
estack
whyashthakker/estack · eStack · same repo
quiz-me
whyashthakker/estack · eStack · same repo
premortem
whyashthakker/estack · eStack · same repo
explain
whyashthakker/estack · eStack · same repo
ux-review
whyashthakker/estack · eStack · same repo
social-media-marketing
dengineproblem/agents-monorepo · Marketing · tag: social
social is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
social reduced setup friction for our internal harness; good balance of opinion and flexibility.
social is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: social is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend social for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added social from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
social fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in social — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for social matched our evaluation — installs cleanly and behaves as described in the markdown.
social fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 57