Profile-Aware Social Media Pipeline

Name: Profile-Aware Social Media Pipeline
Author: skrptiq

Content Creator Official v1.0.19

Generate personalized multi-platform social content using your voice and audience profiles

by skrptiq

content-creation multi-platform personalization social-media voice-profile

workflow Updated 18 July 2026 7 nodes 3 downloads

What's included 7 nodes

1 workflow 3 skills 3 prompts

workflow (1)

Profile-Aware Social Media Pipeline

Generate personalized multi-platform social content using your voice and audience profiles

skills (3)

Core Message Drafting

Drafts the core message for a social media topic using the creator's voice profile

Platform Adaptation

Adapts the core message for a specific social media platform while maintaining the creator's voice

Voice Verification

Checks all platform adaptations against the creator's voice profile for authenticity

prompts (3)

Adapt for Platform

Adapts the core message for a specific platform — runs in for_each loop

Draft Core Message

Drafts the core social media message in the creator's voice

Verify Voice Consistency

Checks all platform adaptations against the creator's voice profile

Requirements 1 service, 1 data type

Services

LLM Service

Data Handling

Security Passed

All checks passed v1.0.19 · scanner v3.3.0

Detected

Services: llm-service
Permissions:
Data Handling:

Full report →

Version history 16 releases

v1.0.19 latest 18 July 2026

GH#863 Wave 3 (Tier-3 tail) — the output_step (language-polish) was polishing its positional-previous step (a validation/review), not the deliverable, because polish-language was pinned pre-`source`-slot. Repinned polish-language 1.0.1→1.0.6 and bound language-polish `source` ← "Platform Adaptation" (the real deliverable producer). No new steps; no other change.

v1.0.18 16 July 2026

GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.

v1.0.17 3 July 2026

GH#745 — declare per-step `output: {name, type}` on every execution step (core_message/text, platform_content/text, voice_verdict/decision, polished_posts/text, consistency_verdict/decision). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.

v1.0.16 30 June 2026

GH#711 — fix the `for_each` platform loop. The `platform-loop` iterates `{{input.platforms}}`, but the input was documented and exampled as a comma-separated string (`LinkedIn, Twitter, …`), which resolves to prose the loop cannot iterate (the engine now fails this loud — GH#557). The input contract is now a JSON array (or one platform per line), mirroring the proven `batch-competitor-analysis` for_each pattern, so the expression resolves to an iterable array. Content-only: Inputs table, Stage 2 wording (notes `{{loop.item}}`), and Example Input updated; no contract or engine change.

v1.0.15 7 June 2026

Fix-forward after Row 3b v1.0.14 publish failure. The v1.0.14 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (5697d19d…) did not match the D1 catalogue row's id (912dbfcd…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.15 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.14; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).

v1.0.13 22 May 2026

Wave 2: re-signed with canonical engine signing pipeline.

v1.0.10 19 May 2026

Signature fix — RELEASE_NOTES.md now included in integrity checksum.

v1.0.9 19 May 2026

Initial catalogue release with full structural and content-quality validation. All scanner checks pass.

v1.0.8 18 May 2026