content-pipeline
Skill2 starsChanged 9 months agoMITView on GitHub
Full automated content pipeline — write, review, edit, and fact-check in one command
17 other projects use a version of this.
Adopted by
Most recently taken up by
- Kianzzz/Zhouxing-skill-publictheir own version, first seen Nov 8, 2026
- LazyIsEfficient/agentic-ostheir own version, first seen Oct 22, 2026
- claude-world/claude-world-studiotheir own version, first seen Oct 22, 2026
- Aravind7262/content-pipelinetheir own version, first seen Oct 20, 2026
- runxhq/runxtheir own version, first seen Oct 13, 2026
- pobsteta/aigoratheir own version, first seen Oct 2, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- OrangeViolin/content-pipeline★ 217same name
- fivetaku/content-pipeline★ 100same name
- runxhq/runx★ 97same name
- claude-world/claude-world-studio★ 71same name
- coopersimson96/ai-content-system★ 17same name
- LazyIsEfficient/agentic-os★ 17same name
- zad111ak-ai/hermes-agent-skills★ 7same name
- Kianzzz/Zhouxing-skill-public★ 4same name
- rami-maalouf/skills★ 2same name
- ahnchen1983/agentic-substrate★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- auto-fixSkill
- edit-contentSkill
- fact-checkSkill
- review-contentSkill
- shipSkill
- write-contentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 15 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
15
Distinctive
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 19
Create, review, edit, and fact-check content in a single command.
- Distinctive: line 34
If the brief is ambiguous, choose sensible defaults and state your assumptions at the top of the output
- Distinctive: line 38
Use WebSearch to gather 5-8 credible sources on the topic
- Distinctive: line 47
Create an outline with thesis, supporting points, and conclusion
- Distinctive: line 48
Write the full draft following the template structure
- Distinctive: line 51
Verify word count falls within the Word Count Guidelines for the content type
- Distinctive: line 64
If the review verdict is REVISE, or after a REJECT rewrite:
- Very specific: line 67
After editing, re-submit to content-reviewer for a second review
- Distinctive: line 68
If the second review is still REVISE or REJECT:
- Distinctive: line 70
Do NOT request a third review — proceed to Phase 6
- Distinctive: line 71
If the review is APPROVE — proceed to Phase 6
- Distinctive: line 85
Run a final self-review against the quality checklist:
- Distinctive: line 98
If content is still not APPROVE after 2 cycles, finalize with the best version and note remaining issues in the quality report
- Distinctive: line 167
Follow all phases in order — do not skip Research or Fact-Check
- Distinctive: line 170
Use Task to delegate to other agents — never impersonate them
- Distinctive: line 172
If WebSearch fails or returns no results, note the gap and proceed with available information
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Pipeline — End-to-End Automated Content Creation
Create, review, edit, and fact-check content in a single command.
Brief: $ARGUMENTS
Instructions
This skill chains all four content agents into one automated pipeline. Follow each phase in order. Cap revision cycles at 2 to prevent infinite loops.
Phase 1: Parse the Brief
- Extract from $ARGUMENTS:
- Topic — the subject to write about
- Content type — blog post, tutorial, API docs, or landing page (default: blog post)
- Target audience — developers, executives, end users, or marketers (default: developers)
- Special requirements — tone, word count, keywords, or other constraints
- If the brief is ambiguous, choose sensible defaults and state your assumptions at the top of the output
Phase 2: Research
- Use WebSearch to gather 5-8 credible sources on the topic
- Prioritize primary sources: official documentation, research papers, industry reports
- Extract key data points: statistics, quotes, examples, and counterarguments
- Identify the unique angle — what do existing articles miss?
- Record all source URLs for citation in the draft
Phase 3: Draft
- Select the matching Content Template from your agent guidelines (blog post, tutorial, API docs, or landing page)
- Create an outline with thesis, supporting points, and conclusion
- Write the full draft following the template structure
- Include inline citations for all facts and statistics
- Save the draft to a file (e.g.,
content/<slug>.md) - Verify word count falls within the Word Count Guidelines for the content type
Phase 4: Review
- Delegate to
content-reviewervia Task:- "Review the content at
content/<slug>.mdusing the full 6-dimension scoring rubric. Return the scored report with verdict (APPROVE/REVISE/REJECT) and action items."
- "Review the content at
- Parse the reviewer's response:
- APPROVE (score >= 24/30) — proceed to Phase 6 (Fact-Check)
- REVISE (score 18-23/30) — proceed to Phase 5 (Edit)
- REJECT (score < 18/30) — rewrite the draft addressing all action items, then re-submit for review (counts as revision cycle 1)
Phase 5: Edit
- If the review verdict is REVISE, or after a REJECT rewrite:
- Delegate to
editorvia Task:- "Edit the content at
content/<slug>.md. Apply all three editing passes (structure, clarity, grammar). Target 20% word reduction. Address these reviewer action items: [paste action items]."
- "Edit the content at
- After editing, re-submit to
content-reviewerfor a second review
- Delegate to
- If the second review is still REVISE or REJECT:
- Apply the remaining action items yourself (this is revision cycle 2)
- Do NOT request a third review — proceed to Phase 6
- If the review is APPROVE — proceed to Phase 6
Phase 6: Fact-Check
- Delegate to
fact-checkervia Task:- "Fact-check the content at
content/<slug>.md. Verify every statistic, quote, technical claim, and external reference. Return the full claim verification table."
- "Fact-check the content at
- Parse the fact-checker's report:
- Incorrect claims — fix immediately with the correct information and source
- Unverified claims — add a source if one exists, or soften the language ("approximately", "reportedly")
- Verified claims — no action needed
Phase 7: Final Polish
- Apply all fact-check corrections to the content file
- Run a final self-review against the quality checklist:
- All facts cited with sources
- Headings descriptive and scannable
- Paragraphs 3-4 sentences max
- No weasel words or filler phrases
- Clear call-to-action or next steps
- Word count within guidelines
- Reading level appropriate for audience
- Save the final version
Revision Cycle Limits
- Maximum 2 revision cycles through Phase 4-5
- If content is still not APPROVE after 2 cycles, finalize with the best version and note remaining issues in the quality report
- This prevents infinite review-edit loops while still producing high-quality content
Output Format
Deliver two artifacts:
1. Final Content File
Saved to content/<slug>.md with metadata footer:
# [Title]
[Final content here]
---
## Metadata
- **Word count:** [number]
- **Reading time:** [X minutes at 250 words/min]
- **Content type:** [blog post / tutorial / API docs / landing page]
- **Target audience:** [audience]
- **Primary keyword:** [keyword]
- **Sources used:** [count]2. Quality Report
Print to the conversation:
## Content Pipeline Report
### Pipeline Summary
| Phase | Status | Notes |
|-------|--------|-------|
| Research | DONE | [X] sources gathered |
| Draft | DONE | [word count] words |
| Review | [APPROVE/REVISE] | Score: [X]/30 |
| Edit | [DONE/SKIPPED] | [X]% word reduction |
| Fact-Check | DONE | [X] verified, [Y] corrected, [Z] unverified |
| Final Polish | DONE | [corrections applied] |
### Revision History
- **Cycle 1:** [summary of changes]
- **Cycle 2:** [summary or "Not needed"]
### Review Scores (Final)
| Dimension | Score |
|-----------|-------|
| Accuracy | X/5 |
| Clarity | X/5 |
| Style | X/5 |
| Structure | X/5 |
| Completeness | X/5 |
| Audience | X/5 |
| **Total** | **X/30** |
### Fact-Check Summary
- **Total claims:** [X]
- **Verified:** [Y]
- **Corrected:** [Z]
- **Unverified:** [W]
### File Location
`content/<slug>.md`Rules
- Follow all phases in order — do not skip Research or Fact-Check
- Maximum 2 revision cycles, then finalize
- Save the content file after each phase so progress is preserved
- Use Task to delegate to other agents — never impersonate them
- Cite every factual claim with a source URL
- If WebSearch fails or returns no results, note the gap and proceed with available information
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.

