ai-content-collaboration
How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content productio…
Install / Use
npx skills add rampstackco/claude-skills --skill ai-content-collaborationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of ai-content-collaboration
ai-content-collaboration scores 86/100 on our quality scale, 1833rd of 2,780 Automation skills we index.
Its SKILL.md is 22 KB long, well organised into 15 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 902 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ai-content-collaboration is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ai-content-collaboration compared with similar skills
All 4 of these similar skills score higher than ai-content-collaboration; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ai-content-collaboration (this skill)by rampstackco | 86 | 902 | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install ai-content-collaboration?
- Run
npx skills add rampstackco/claude-skills --skill ai-content-collaboration. The install tabs above show the steps for each supported agent. - Which AI agents does ai-content-collaboration work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ai-content-collaboration safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ai-content-collaboration still maintained?
- The repository was last updated about 2 months ago, so ai-content-collaboration is actively maintained.
Skill content
View source on GitHubname: ai-content-collaboration description: "How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy." category: content catalog_summary: "How humans and AI compose in content workflows: participation boundaries, hybrid patterns, voice ownership, the AI slop problem, disclosure and transparency, team calibration, and the ethics of honest AI-assisted production" display_order: 8
AI Content Collaboration
A senior editorial leader's playbook for how humans and AI compose in content workflows. Pragmatic, tool-agnostic, honest about both what AI in the loop enables and what it threatens.
Most content programs in 2026 use AI somewhere in the workflow. Pretending otherwise is dishonest; treating AI as a magic content factory is the failure mode this skill exists to prevent. The discipline is in between: knowing where AI legitimately accelerates, where humans must own, what hybrid patterns produce work that earns reader trust, and what crosses the line into AI slop or intellectual dishonesty.
This skill is the WORKFLOW layer that composes with every other content skill. Briefs can be AI-assisted; hub architectures can be AI-assisted; programmatic SEO is almost always AI-involved; editorial QA now includes AI-content audit by necessity. The collaboration discipline applies to all production stages, not to a single artifact type.
The voice is pragmatic and tool-agnostic deliberately. The methodology applies whether the AI in your loop is one of the major commercial models, an open-source model, or whatever ships next quarter. What stays constant is the workflow shape, the participation boundaries, the voice ownership question, and the ethical frame. What changes is which specific tool you reach for, which is implementation work that varies by team and budget.
When to use this skill: building or refining an AI-content workflow, calibrating a team on consistent AI usage, addressing the "we use AI but our work feels generic" problem, designing disclosure policies, or working through the ethics of AI-assisted content production for a regulated or trust-sensitive context.
What this skill is for
This skill spans the workflow layer of AI-assisted content production. It composes with all six other content-suite skills as the cross-cutting discipline.
content-strategyis program scope: what to produce. Strategy decisions can be AI-assisted; the program-level judgment stays human.pillar-content-architectureis hub scope: how the topical hub fits together. Hub architecture can be AI-suggested; the architectural commitment stays human.content-brief-authoringis per-piece scope: briefs each piece. Briefs can be AI-drafted from research; the contract decisions stay human.content-and-copyis execution scope: writes each piece. Drafts can be AI-produced; voice and editorial judgment stay human.programmatic-seois scaled scope: generates pages from data. AI generation is the dominant production model; sampling QA is the human gate.editorial-qais gate scope: verifies before publish. AI-content audit is now a load-bearing gate; the audit's judgment stays human.- This skill is workflow scope: how the human and AI layers compose across all six stages above.
The audience: editorial leaders, content directors, content ops managers, agencies running AI-assisted production, in-house teams calibrating AI usage across writers. The voice is senior editorial leader to junior editor or content marketer. Pragmatic, honest, tool-agnostic.
What is not in scope: specific prompts (those are implementation; teams develop their own), specific tool endorsements (the methodology applies regardless of which tool is in the loop), specific integration code (varies by stack and team). Tool categories appear when they earn methodology relevance; specific tools appear only as illustrations of categories, never as recommendations.
Humans own, AI accelerates
The keystone framing.
The pathology to avoid is treating AI as either a magic content factory (cheap, fast, scaled, output quality optional) OR as a forbidden intruder (purity gospel that does not survive contact with deadlines). Both readings produce bad work.
The discipline that produces durable work: humans own the content; AI accelerates the work. Specifically:
Humans own. Editorial judgment, voice, distinctive POV, fact accuracy, ethical decisions, what to publish versus what to kill, brand voice, narrative arc, tone calibration, reader empathy, claim verification.
AI accelerates. Research synthesis, draft generation against a brief, copy edit suggestions, alternative phrasings, summary, transcription, quality-control automation at scale.
The line. AI does work that the human directs and verifies. AI does NOT make decisions about what publishes, who is quoted, what is true, or what voice the brand uses.
The litmus test. If your AI-assisted piece publishes without a human being able to defend every claim, every position, and every word, you have crossed the line. The piece is AI's work, dressed in your byline. Readers eventually notice.
Where AI legitimately participates
A non-exhaustive list of stages where AI in the loop is fine and often improves the work.
- Research synthesis. AI condenses long-form sources into briefs the writer reads. Saves hours; the writer still reads and verifies.
- Outline generation against a brief. AI proposes an H2 / H3 structure from a brief; the editor approves or restructures.
- First-draft generation. AI produces a draft against an explicit brief; the human edits substantially.
- Alternative phrasings. AI offers 3 versions of a sentence; the human picks one or rewrites.
- Copy edit suggestions. AI catches typos, awkward phrasings, repetition.
- Summary and abstraction. AI condenses long pieces into TL;DRs.
- Transcription. AI transcribes interview audio; the human verifies.
- Translation drafts. AI produces a translation draft; a native speaker reviews and corrects.
- Quality-control automation at scale. AI flags pages in a programmatic SEO set that need human review.
- Idea generation. AI proposes 30 angles; the human picks 3.
In each case, AI accelerates work the human still owns. The acceleration is real; the ownership stays unchanged.
Detail in references/ai-participation-boundaries.md.
Where humans must own
The boundary list.
- Editorial judgment. What to publish, what to kill, what is worth saying. AI cannot decide whether a piece is good enough to ship.
- Voice. Brand voice, distinctive POV, the way THIS publication sounds different from the next one. AI default voice is generic by construction; voice is a human contribution.
- Fact verification. Every claim, every statistic, every quote, every named person. AI hallucinates; humans verify.
- Ethical decisions. What is appropriate to publish, what is harmful, what crosses lines, what disclosure is required.
- Reader empathy. What the reader actually needs from this piece, not what the algorithm scores well.
- Quote attribution. Real people who actually said the thing, with consent where relevant.
- Tone calibration on hard topics. Grief, illness, sensitive history, contested politics. AI defaults to anodyne; humans calibrate to context.
- Narrative arc. How the piece unfolds, where the reader's attention goes. AI produces shapes; humans choose them.
- Final approval. The human who signs off is accountable for what shipped.
The "human in the loop" framing is necessary but insufficient. A human briefly reviewing AI-generated content before publish is not ownership; it is rubber-stamping. Ownership requires the human to have made the actual decisions the piece embodies.
Hybrid workflow patterns
Five patterns that work, with tradeoffs.
1. AI-first draft, human-edit-heavy. AI produces a 90% draft; the human spends 60% of the time editing. Output: efficient for high-volume editorial; risks generic voice if editing is light.
2. Human-first outline + research, AI-draft, human-rewrite. Human builds the outline and gathers research; AI drafts within that scaffold; human rewrites in voice. Output: preserves voice better; slower than AI-first.
3. AI-as-research-assistant, human-writes. AI condenses sources into a brief; human writes the entire piece from the brief. Output: highest voice fidelity; slowest.
4. Human-writes, AI-as-editor. Human drafts; AI suggests edits, alternative phrasings, copy edits; human accepts or rejects. Output: writer voice preserved; AI catches details.
5. AI-generates-at-scale, human-samples. For programmatic SEO. AI generates thousands of pages; human samples 50 to 200 with editorial-qa discipline. Output: scaled production; depends entirely on template quality and sampling discipline.
The pattern that fits depends on volume, voice sensitivity, team skill, and time budget. No pattern is "the right one"; pattern selection is a real decision that should match the production context.
Detail in references/hybrid-workflow-patterns.md.
Voice ownership preservation
Voice is the dominant casualty of careless AI workflows. The patterns that preserve voice.
- Voice guidelines as prompt input. Every AI generation includes the brand voice guidelines as context. Generic AI defaults regress without this.
- Sample text as voice anchor. Feed the AI 2 to 3 paragraphs of canonical brand voice as part of the prompt. AI mimics what it sees more than what it is told.
- Mid-draft voice check. At the halfway mark of a long piece, have a human or a separate AI pass read for voice drift. Long AI generations regress halfway through almost always.
- Final pass in human voice. The human edits the closing sections in their own voice; this is where the piece's emotional register often lands.
- Reject the bland. Any sentence that could appear in any other piece on the topic gets rewritten. Voice lives in the specific.
The honest framing. Voice is the hardest thing to preserve in AI-assisted work and the easiest thing to lose. Programs that do not actively preserve voice end up with content that is technically correct, semantically generic, and indistinguishable from competitors using the same tools.
Detail in references/voice-ownership-preservation.md.
The AI slop problem
AI slop is the term of art for AI-generated content that is technically functional but reads as generic, derivative, and signal-less. Cross-reference editorial-qa's ai-content-audit-patterns reference for the detection patterns; this section addresses prevention.
Patterns that produce slop.
- AI does too much of the work (no real human direction or rewriting)
- Generic prompts (no brand voice context, no audience specificity, no anti-pattern guidance)
- No editorial judgment in the loop (AI generates, human glances, ship)
- Volume prioritized over quality (10x more pages can mean 10x more slop, not 10x more value)
- No iteration (first draft ships; no rewrite for voice)
Patterns that prevent slop.
- Strong briefs (per
content-brief-authoring) - Voice guidelines as prompt context
- H
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
