Agent skill
content-shipped
Log shipped content to the content log. Use when user says "I shipped", "I published", "just posted", or mentions completing content work.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/content-shipped
Metadata
Additional technical details for this skill
- model
- default
- proactive
- YES
- slash command
- user invocable
- NO
- marvin category
- content
SKILL.md
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 month
Notes
- 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?