← ClaudeAtlas

armor-social-media-pipelinelisted

The single Hermes runtime entrypoint for producing ARMOR overseas social-media content for LinkedIn, Facebook, Instagram, TikTok, and YouTube. Use when selecting topics, building social Topic Briefs, drafting platform-specific copy, producing video packages, auditing social content, routing approved social-copy deliverables, or reviewing published performance. The canonical workflow and templates live in the ARMOR Vault Social Media Production Pipeline folder.
licat233/Enterprise-AI-Office · ★ 0 · AI & Automation · score 70
Install: claude install-skill licat233/Enterprise-AI-Office
# ARMOR Social Media Production Pipeline This is the single runtime entrypoint for ARMOR overseas social-media production. It is an adapter: the canonical stages, artifacts, gates, and save boundaries live in independent Markdown standards in the Vault pipeline folder. Do not duplicate the full workflow in this skill. Canonical folder: `${ARMOR_VAULT_ROOT}/02-Projects/Workspaces/Content/ARMOR-Content-Operations/ARMOR-Social-Media-Production-Pipeline-v2.0/` `ARMOR_VAULT_ROOT` is supplied by the Enterprise runtime. Do not replace it with a host-specific absolute path. Read the matching Markdown standard for the current stage. The main stage map and contracts live in `armor-social-media-pipeline.md`; detailed stage standards are `intake-standard.md`, `topic-selection-standard.md`, `topic-brief-standard.md`, `social-writing-standard.md`, `platform-adaptation-standard.md`, `social-audit-standard.md`, `approval-standard.md`, `save-standard.md`, and `performance-standard.md`. ## Stable flow ```text Intake / topic confirmation → topic signals and deduplication → evidence pack and Topic Brief → core draft → humanization (ai-writing-audit detect → fix → re-detect) → humanization and platform adaptation → social audit → focused correction when required → write every artifact directly into the Router destination (quality_status: DRAFT) → user approval of the Vault file (Obsidian) → status update and read-back in the same file → post-publication performance review ``` ## Draft loc