publish-content
Skill4 starsChanged 8 months agoMITView on GitHub
Publish approved content to social media, blog, or other channels via Chrome MCP
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brand-setupSkill
- daily-digestSkill
- deploySkill
- ecosystem-scoutSkill
- process-approvalsSkill
- qa-checkSkill
- send-outreachSkill
- submit-for-approvalSkill
- venture-bootstrapSkill
- venture-health-checkSkill
- venture-intakeSkill
- venture-staffingSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 36
Use form_input to enter the tweet text
- Distinctive: line 37
Use computer to click the Post button
- Distinctive: line 42
Use computer to click "Start a post"
- Distinctive: line 43
Use form_input to enter the post content
- Distinctive: line 44
Use computer to click Post
- Distinctive: line 49
Use computer to click "Create Post"
- Distinctive: line 50
Use form_input to enter title and body
- Distinctive: line 55
Create a new post with the content
- Distinctive: line 84
Update the Decisions DB entry with the published URL in Context
≈ “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
Publish Content
Publish an approved piece of content via the appropriate channel. This skill reads from the Decisions DB and publishes via Chrome MCP.
Step 1: Read the Approved Item
Fetch the Decisions DB entry to get:
- The content to publish (from Context field)
- The target channel (Twitter/X, LinkedIn, blog, Reddit, forum, etc.)
- The venture slug
Step 2: Publish via Chrome MCP
Twitter/X
- Navigate to
https://twitter.com/compose/tweet(orhttps://x.com/compose/post) - Use form_input to enter the tweet text
- Use computer to click the Post button
- Capture the tweet URL from the resulting page
- Navigate to
https://www.linkedin.com/feed/ - Use computer to click "Start a post"
- Use form_input to enter the post content
- Use computer to click Post
- Capture the post URL
- Navigate to the target subreddit
- Use computer to click "Create Post"
- Use form_input to enter title and body
- Use computer to click Post
Blog (if venture has a blog platform)
- Navigate to the blog admin
- Create a new post with the content
- Publish and capture the URL
General approach for other platforms
- Navigate to the platform
- Find the compose/post area
- Input the content
- Submit and capture the result URL
Step 3: Log the Publication
- Save to venture's
marketing/published/{date}-{platform}-{slug}.md:# Published: {title} **Platform:** {channel} **Date:** {date} **URL:** {published-url} ## Content {the content that was published} - Append to venture's
docs/changelog.md:## {date}: [Launch] Published on {platform} {title} — {published-url} - Update the Decisions DB entry with the published URL in Context
Step 4: Report
"Published to {platform}: {url}"
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.

