post-studio
Skill2 starsChanged 55 days agoMITView on GitHub
Storyteller — writes LinkedIn posts designed to make the user's buyers comment, using what the market is discussing in Pastel, then turns everyone who engages into leads. Use for "write a LinkedIn post", post ideas, a content calendar, lead-magnet posts, or growing inbound from LinkedIn.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buying-committeeSkill
- call-readySkill
- campaign-launchSkill
- command-centerSkill
- competitor-watchSkill
- fit-checkSkill
- human-voiceSkill
- intent-radarSkill
- market-mapSkill
- message-writerSkill
- morning-briefSkill
- nudgeSkill
- outbound-briefSkill
- priority-rankSkill
- reach-checkSkill
- reply-deskSkill
- social-warmupSkill
- what-worksSkill
- why-nowSkill
The file
Files
Post studio — Storyteller
House rules: ../command-center/shared/house-rules.md · Pastel tools: ../command-center/shared/pastel-tools.md
Outbound reaches people one by one; a good post brings them to you. Every person who comments or reacts becomes a lead with a signal attached.
Steps
- Find what the market is talking about:
pastel_aggregate_posts(group_by="intent_tag", range="30d")andpastel_recommend_best_postsshow the themes and questions buyers engage with right now. Addcompetitor-watchfindings if available. - Pick one idea per post, from one of these angles:
- a number from the user's own work ("we reviewed 200 onboarding calls…");
- a strong opinion the audience half-agrees with;
- a teardown of how something is done badly, and what works instead;
- a giveaway — a template, checklist, or resource offered to people who comment. Only offer what the user can actually deliver.
- Write it:
- the first two lines must work on their own (that's all LinkedIn shows before "…see more");
- short paragraphs, one idea;
- end with a question or a clear call to comment;
- 120–250 words; no hashtag wall (three at most).
- Run
human-voice, then give two opening lines to choose from. - After publishing (2–5 days later): find the post with
pastel_query_postsand pull the engagers withpastel_leads_for_post. Hand them tofit-checkwith the signal "engaged with our post on [date]". For a giveaway post, list who asked for it so the user can send it.
The user publishes the post themselves; this skill never posts on their behalf.
Output
# Post — [topic]
Opening A:
> …
Opening B:
> …
Post:
> …
Why this will get the right people talking: [one line]
After publishing: run post-studio again with "who engaged" in 2–5 days.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.

