content-pipeline

Orchestrates research, drafting, bilingual translation, and review into a finished UA/EN content artifact.

5|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/PatriotAi/ai-lab --skill content-pipeline-patriotai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-pipeline
Source: https://github.com/PatriotAi/ai-lab/tree/main/.claude/skills/content-pipeline
Command: npx skills add https://github.com/PatriotAi/ai-lab --skill content-pipeline-patriotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating well-researched, bilingual (Ukrainian/English) content involves many disconnected steps—research, drafting, translation, and review—that are easy to do inconsistently. This Skill orchestrates the full cycle so one run produces one polished, two-language artifact with cited sources. ## Core Features & Use Cases - End-to-End Orchestration: Coordinates the full flow from topic clarification through research, UA canonical draft, EN mirror, and editorial review. - Delegation to Specialized Skills: Routes deep research to deep-research, translation to translate-uaen, and publishing to publish, keeping one responsibility per skill. - Terminology and Source Discipline: Checks terms against docs/glossary.md, requires cited sources for facts, and blocks secrets or PII from content. - Use Case: Ask for a bilingual overview of MCP connectors—the pipeline researches sources, writes the UA canonical draft, mirrors it in EN, reviews terminology and links, and saves the artifact to docs/ or experiments/. ## Quick Start Ask the assistant to run the content pipeline to prepare a bilingual article on your chosen topic, specifying the format, audience, and target folder.

Frequently Asked Questions about content-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a bilingual Ukrainian-English article with AI?▼

Run the content pipeline with your topic, format, and audience. It researches sources, writes the Ukrainian canonical draft first, mirrors it in English via the translate-uaen skill, then reviews terminology, facts, and links before saving the artifact.

What steps does a content pipeline workflow include?▼

The workflow covers topic and audience clarification, research with cited sources, a Ukrainian canonical draft checked against the project glossary, an English mirror translation, and a final review of terminology, facts, Markdown formatting, and links.

When should I use the content pipeline instead of a translation skill?▼

Use the content pipeline when starting from a topic or idea that needs the full journey to a finished bilingual artifact. If you already have finished text that only needs localization, use the translate-uaen skill directly instead.

Can the content pipeline publish the finished article?▼

The pipeline itself ends at a reviewed, saved artifact in docs/ or experiments/. When publishing is needed, it hands the artifact off to the separate publish skill rather than publishing inline.

What are the limitations of this content workflow?▼

One pipeline run produces exactly one artifact, and facts without cited sources are not published. Experiment-related runs must record measurements and conclusions through the experiment skill rather than inline in the pipeline.