agentleFS
whyashthakkerwhyashthakker/estack/skills/social/SKILL.md

social

Skill0 starsChanged 12 days agoMITView on GitHub

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.

40 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use popups, free-tools and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 16 projects that use this

  • CesarjoquinSkill

    free-tools

    When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

    Also in 17 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 19 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 16 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 10 projects that use this

  • +7 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the user's recent posts if they share them, or their site and bio.

    line 12
  2. Distinctive:

    Not salesy: No urgency, discounts, "link in bio", or hype words.

    line 30
  3. Distinctive:

    Facts from sources: Every number and name comes from a source you read.

    line 31
  4. Very specific:

    No slop: Run the slop check from ste100 (stock AI words, hype, "not X but Y" frames, em dash chains).

    line 33
  5. Distinctive:

    X thread: only when the story needs 3 to 7 beats.

    line 36
  6. Distinctive:

    Do not offer drafts under 55.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social

Goal: posts people share because they say something, not posts that are only correct.

1. Learn the voice

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.

2. Find the point

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:

  • A named company's decision you think is right or wrong, and why.
  • A number that contradicts the common belief.
  • A practical result: what you can do now that you could not do last week.

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.

3. Write

Rules for both platforms:

  • First line does the work. Name the subject (company, product, person, or number). Under about 15 words on X. On LinkedIn the hook must fit in the first ~140 characters, before "see more".
  • One idea per post. One sentence per line. Concrete nouns and real numbers.
  • Resolve it in the post. The reader gets the point without clicking.
  • No link in the post. Links go in the first reply (X) or first comment (LinkedIn).
  • Not salesy. No urgency, discounts, "link in bio", or hype words. Product mentions go in the first reply, only when relevant.
  • Facts from sources. Every number and name comes from a source you read. Never invent a first-person story.
  • End on a takeaway or a real question. Not "thoughts?" or "agree?".
  • No slop. Run the slop check from 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.

4. Score before you offer

Give each draft a score out of 100 and show the parts:

PartMaxQuestion
Point of view30Would a real share of readers argue with it?
Timing20Is the story rising now?
Fit20Does the hook work in one line for this platform and audience?
Gap15Has no one in this space posted this angle yet today?
Proof15Are the facts specific and sourced?

Do not offer drafts under 55. Zero drafts is a valid answer.

5. Hand off

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.