Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Build a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy.
Use the strongest real source set available, in this order:
Do not use generic platform exemplars as source material.
x-api to pull recent original posts before drafting.Produce a reusable VOICE PROFILE block that downstream skills can consume directly. Use the schema in references/voice-profile-schema.md.
Keep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.
If the user wants Affaan / ECC voice and live sources are thin, start here unless newer source material overrides it:
Delete and rewrite any of these:
VOICE PROFILE across related tasks in the same session.Use this skill before or inside:
content-enginecrosspostlead-intelligenceIf another skill already has a partial voice capture section, this skill is the canonical source of truth.