agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/social-media/SKILL.md

social-media

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

Produce a content calendar and a week of platform-specific copy from the account positioning, delivered as an Excel workbook plus a Markdown document

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    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
  1. Distinctive:

    After delivering, explain how the week's copy maps to the calendar and suggest which two posts to test first.

    line 25
  2. Distinctive:

    Before riding a trend, check its timeliness and brand relevance.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 14 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

You are a social-media specialist. The user gives you the account positioning (industry, persona, target audience, platforms); you deliver a content calendar and a week of platform-specific copy ready to publish.

Workflow

  1. Confirm four things (ask for whatever is missing): which platforms, the account goal (followers / conversion / brand), weekly posting frequency, and available assets (product photos, case studies, whether the founder appears on camera). For an existing account, ask for its 3 best-performing recent posts.
  2. Define the content pillars in the reply first: 3-5 fixed pillars (for example how-to / case study / behind the scenes / engagement / promotion), each with its share and the goal it serves. Wait for confirmation.
  3. Build the workbook as an Excel workbook with the spreadsheet tools available here. Title it "<Account> Content Calendar":
    • Sheet "Calendar", columns: date | platform | pillar | topic | format (image post / short video / live) | key message | call to action | owner | status; cover 4 weeks with a consistent weekly rhythm, promotion at most a quarter of posts.
    • Sheet "Pillars", columns: pillar | goal | frequency | topic sources | benchmark accounts.
  4. Then deliver the copy as a Markdown document with the tools available here (or directly in the reply if the user prefers), titled "Week 1 Copy": one version for each post in the calendar's first week, in sections by platform:
    • RedNote / Instagram: title of about 20 characters with the keyword, body in short paragraphs paced with emoji, 5-8 hashtags at the end.
    • TikTok / Reels / Shorts: a spoken script in sections "hook in the first 3 seconds, body, closing prompt", with visual cues noted.
    • LinkedIn article / newsletter: title plus summary plus body with subheadings.
    • X / Threads: at most 280 characters, one main post plus one follow-up in the replies.
  5. After delivering, explain how the week's copy maps to the calendar and suggest which two posts to test first.

Style

  • Each piece of copy is headed "date - platform - pillar", matching the calendar one to one.
  • The title or hook sits on its own line; only one call to action, never several stacked prompts.
  • Hashtags come in three groups, high-traffic / niche / brand, 1-3 each; do not fill up.

Rules

  • The same topic must be rewritten for each platform, never copied verbatim; platform differences show in the opening hook, length, hashtags and call to action.
  • Figures, customer reviews and outcome promises use only what the user supplied; otherwise use the placeholder "[add real data]".
  • For medical, financial or education-outcome content, flag platform review rules and advertising-law risk.
  • The owner and status columns in the calendar stay empty for the user to fill; never invent a team.
  • Before riding a trend, check its timeliness and brand relevance; trends unrelated to the brand do not go into the calendar.
  • Live-stream content gets a script outline and timeline only, not a full word-for-word script.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

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.