content-shipped
Skill1 starsChanged 6 months agoMITView on GitHub
Log shipped content to the content log. Use when user says "I shipped", "I published", "just posted", or mentions completing content work.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asana-taskSkill
- briefing-prepSkill
- case-studySkill
- content-draftSkill
- content-strategySkill
- email-draftSkill
- event-promoSkill
- handoffSkill
- lab-summarySkill
- launch-strategySkill
- linkedin-scrapeSkill
- meeting-followupSkill
- member-commsSkill
- mma-brand-guidelinesSkill
- mma-org-contextSkill
- mma-pptx-builderSkill
- mma-writing-styleSkill
- office-editingSkill
- press-releaseSkill
- reddit-scrapeSkill
- research-briefSkill
- researchSkill
- search-and-scrapeSkill
- sharepoint-findSkill
- slack-summarySkill
- zapier-workflow-builderSkill
- commitSkill
- daily-briefingSkill
- endSkill
- marvinSkill
- mavenSkill
- skill-creatorSkill
- template-skillSkill
- updateSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
If any details are unclear, ask:
- Very specific: line 56
Check state/goals.md for relevant monthly targets and note progress.
- Distinctive: line 72
Don't require explicit trigger if context is clear
- Distinctive: line 73
Keep celebration brief, not over-the-top
≈ “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
Content Shipped Skill
Log completed content to track progress against goals.
When to Use
Trigger phrases:
- "I shipped..."
- "I published..."
- "Just posted..."
- "Finished the..."
- "The {article/video/post} is live"
Process
Step 1: Extract Content Details
From the conversation, identify:
- Type: Article, video, podcast, social post, etc.
- Title: The content title
- URL: Link if available
- Platform: Where it was published
- Goal: Which monthly/annual goal this counts toward
Step 2: Confirm Details
If any details are unclear, ask:
- "What's the title?"
- "Where was it published?"
- "Which goal does this count toward?"
Step 3: Log to Content File
Append to content/log.md:
### {DATE}
- **[{TYPE}]** "{Title}"
- URL: {link}
- Platform: {where published}
- Goal: {which goal this supports}Step 4: Update Progress
Check state/goals.md for relevant monthly targets and note progress.
Step 5: Celebrate (briefly)
Acknowledge the shipped work:
- "Nice! That's {X}/{Y} for the month."
- "Logged. You're on track for {goal}."
Output Format
Logged: **[{TYPE}]** "{Title}"
Progress: {X}/{Y} {content type} this monthNotes
- Be proactive about detecting shipped content in conversation
- Don't require explicit trigger if context is clear
- Keep celebration brief, not over-the-top
Skill created: 2026-01-22
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.

