post-substack
Skill9 starsChanged 2 months agoMITView on GitHub
Adapt and publish campaign items on Substack — newsletter issues that email real subscribers
In this repository29 other files it gives its agents.
- content-writingSkill
- image-generationSkill
- post-blueskySkill
- post-devtoSkill
- post-facebookSkill
- post-hackernewsSkill
- post-indiehackersSkill
- post-linkedinSkill
- post-mediumSkill
- post-producthuntSkill
- post-redditSkill
- post-substackSkill
- post-threadsSkill
- post-xSkill
- social-campaignSkill
- content-writingSkill
- image-generationSkill
- post-blueskySkill
- post-devtoSkill
- post-facebookSkill
- post-hackernewsSkill
- post-indiehackersSkill
- post-linkedinSkill
- post-mediumSkill
- post-producthuntSkill
- post-redditSkill
- post-threadsSkill
- post-xSkill
- social-campaignSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 34
No public write API.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Substack Adapter
Facts live in platforms/substack.json. A Substack publish emails actual
subscribers — that makes approval discipline non-optional.
What Substack rewards (culture)
- A consistent personal voice and recognizable sections — subscribers signed up for YOU.
- Email-subject-line quality titles; the subject is the open rate.
- Delivered value per issue: takeaways, not announcements.
Drafting from the content graph
core-claim→ subject-line title (clear > clever).context→ the lede paragraph.proof/technical→ the issue body, sectioned.demo/link→ inline links and a "try it" block.cta→ the close: what you'd like readers to do/reply.- Campaign items that are pure announcements should be reshaped into an issue with a point — or shipped as a Substack Note instead.
Publishing
manual→ draft package (title, subtitle, body, media manifest).agent-browser→ playbook exists for the publish editor; remember: "Publish" SENDS EMAIL. Stop at preview/schedule unless the human explicitly confirmed send.- No public write API.
Genuine engagement
- Reply to subscriber replies; newsletters are relationships.
- Cross-promote honestly; list-broking and fake testimonials are out.
Pitfalls
- Publishing emails subscribers — an accidental send is not recoverable. Agent-browser runs end at preview unless explicitly told to send.
- Blast-radius judgment: one good issue > three thin ones.
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.

