write-social
Skill14 starsChanged 3 months agoMITView on GitHub
Create channel-native social and community marketing. Use for Product Hunt listings, Reddit posts or community launches, X posts and threads, LinkedIn posts, founder or company social content, reply banks, launch sequences, community participation, or rewriting social work so it delivers value in-platform without deceptive engagement tactics.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brief-creativeSkill
- brief-product-uiSkill
- conquistadorSkill
- create-brandSkill
- create-paid-campaignSkill
- create-shortformSkill
- debate-agentsSkill
- improve-conversionSkill
- knowledge-reviewSkill
- map-user-flowSkill
- measure-growthSkill
- model-growth-funnelSkill
- optimize-searchSkill
- plan-campaignSkill
- polish-vietnameseSkill
- research-channelSkill
- research-positioningSkill
- write-copySkill
- write-longformSkill
- write-outreachSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Check the specific community's current rules and norms.
- Distinctive: line 41
Prefer one well-matched community over cross-posting the same pitch.
- Distinctive: line 45
Put the claim, observation, or product change in the opening line.
- Distinctive: line 66
Keep publishing and account actions behind explicit approval.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Write social and community marketing
Produce ready-to-post work that fits the community, actor, and audience. Verify current platform rules and format limits when they affect the result.
Establish channel fit
Determine:
- actor: founder, company, employee, customer, or community participant;
- audience and community purpose;
- useful idea, product change, evidence, or question;
- affiliation and disclosure requirements;
- native format and realistic CTA;
- strongest skeptical response.
Recommend not posting when the community-product fit is weak. Never manufacture engagement, votes, controversy, vulnerability, authority, or customer advocacy.
Apply the channel
Product Hunt
Classify the product with a concrete, differentiated tagline. Explain the problem, mechanism, why now, and invitation for feedback. Make gallery assets tell a progressive product story. Prepare honest answers on audience, alternatives, pricing, privacy, and roadmap. Measure qualified activation and objections, not rank alone.
Check the specific community's current rules and norms. Lead with a useful observation, artifact, result, or honest question. State affiliation plainly. Make the post valuable without the click. Prefer one well-matched community over cross-posting the same pitch.
X
Put the claim, observation, or product change in the opening line. Compress wording, not meaning. Use a thread only when sequence creates cumulative value. Make media carry evidence. Write replies that advance the idea rather than repeat it.
Open on a concrete professional tension, result, or lesson. Prefer lived specificity and real tradeoffs over inspiration. Keep line breaks readable without theatrical fragmentation. Use founder voice for conviction and learning; company voice for product truth and proof.
Deliver
Return the final native post or listing first. Include only the useful supporting pieces:
- alternate hook or title when it tests a genuinely different angle;
- honest disclosure line;
- media or gallery brief;
- reply bank for likely questions and objections;
- sequence timing when multiple posts have distinct roles;
- measurement and a decision date.
Keep publishing and account actions behind explicit approval. If the host cannot guarantee that boundary, stop with the ready-to-post package.
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
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.

