{
  "schemaVersion": "1.0",
  "item": {
    "slug": "voice-matched-content-system",
    "name": "Voice-Matched Content System",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/BrianRWagner/voice-matched-content-system",
    "canonicalUrl": "https://clawhub.ai/BrianRWagner/voice-matched-content-system",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/voice-matched-content-system",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=voice-matched-content-system",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/voice-matched-content-system"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/voice-matched-content-system",
    "agentPageUrl": "https://openagent3.xyz/skills/voice-matched-content-system/agent",
    "manifestUrl": "https://openagent3.xyz/skills/voice-matched-content-system/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/voice-matched-content-system/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Voice-Matched Content System",
        "body": "The #1 complaint about AI content: \"It doesn't sound like me.\"\n\nThis skill fixes that permanently. Not with a one-line tone instruction. With a complete voice operating system that understands HOW someone communicates — their patterns, energy, confidence zones, transitions, and editing instincts.\n\nBuilt from a real voice extraction methodology refined over 15+ years of brand strategy work."
      },
      {
        "title": "✅ Use This Skill When:",
        "body": "Someone wants to capture their authentic writing voice\nContent \"sounds too AI\" and needs to match the creator's real style\nBuilding a voice guide for consistent content across platforms\nGhostwriting or creating content on behalf of someone\nUser says: \"write like me,\" \"capture my voice,\" \"this doesn't sound like me,\" \"make it sound like me,\" \"voice guide,\" \"brand voice\""
      },
      {
        "title": "❌ Do NOT Use When:",
        "body": "Writing generic content with no voice reference → Use standard content skills\nEditing existing copy for grammar/clarity only → Use copy-editing tools\nCreating content strategy (what to write, not how) → Use content strategy skills\nNeed a brand messaging framework → Use positioning skills"
      },
      {
        "title": "Inputs Required:",
        "body": "Minimum: 3 writing samples (blog posts, emails, social posts, transcripts — anything they've written)\nBetter: 5-10 samples across different contexts (professional, casual, teaching, selling)\nBest: Samples + a 5-minute conversation about how they think about communication"
      },
      {
        "title": "Outputs Produced:",
        "body": "Complete Voice DNA Profile (reusable across all future content)\nContent generated in their authenticated voice\nPlatform-specific voice adaptations (LinkedIn vs X vs email vs proposals)\nVoice consistency checklist for self-editing"
      },
      {
        "title": "Step 1: Collect Samples",
        "body": "Ask for 3-10 writing samples. The more variety, the better the profile.\n\nGood samples:\n\nSocial posts they're proud of\nEmails they wrote quickly (less filtered = more authentic)\nBlog posts or articles\nPodcast/video transcripts (spoken voice often reveals real patterns)\nTexts or casual messages (if they're comfortable sharing)\n\nWhat to tell the user:\n\n\"Send me 3-5 pieces of writing you've done. Mix of professional and casual is ideal. The ones you wrote fast without overthinking are often the most useful — that's where your real voice lives.\""
      },
      {
        "title": "Step 2: Analyze Voice DNA",
        "body": "Read all samples and extract these 8 dimensions:\n\n1. Sentence Architecture\n\nAverage sentence length (short and punchy? Long and flowing?)\nDo they use fragments? (\"Not a chance.\" / \"Game over.\")\nSentence variety pattern (short-short-long? Building momentum?)\nParagraph length preference\n\n2. Opening Patterns (How They Start)\n\nDo they hook with a question? A bold statement? A story? A contrarian take?\nFirst-line energy level (explosive vs. measured)\nDo they set context first or dive straight in?\n\n3. Transition Signatures\n\nMap their recurring bridge phrases. Everyone has them. Examples:\n\n\"Here's the thing...\"\n\"What that means is...\"\n\"The reality is...\"\n\"But here's what's interesting...\"\n\"Let me break this down...\"\n\"So here's what happened...\"\n\nExtract at least 8-10 transition phrases from their samples. These are fingerprints.\n\n4. Energy Mapping\n\nBaseline energy level (calm authority? Electric enthusiasm? Quiet confidence?)\nWhat triggers their high-energy mode?\nHow do they express excitement? (Exclamation marks? ALL CAPS? Power words?)\nDo they use humor? What kind? (Self-deprecating? Observational? Sarcastic?)\n\n5. Authority Zones vs. Learning Zones\n\nThis is critical and most voice tools miss it entirely.\n\nAuthority zones = Topics where they write with full confidence\n\nDefinitive language: \"Here's what works,\" \"The data shows,\" \"What I've learned\"\nNo hedging, no \"I think maybe\"\n\nLearning zones = Topics where they're exploring\n\nExploratory language: \"What I'm seeing,\" \"In my experience so far,\" \"What I'm learning\"\nStill confident, but framed as ongoing discovery\n\nMap which topics fall into which zone. This prevents the AI from writing with false authority on topics the person is still learning about.\n\n6. Vocabulary Fingerprint\n\nWords they use often (favorites)\nWords they NEVER use (allergies)\nIndustry jargon: do they embrace it or avoid it?\nFormality level (contractions? Slang? Academic?)\nProfanity comfort level\n\n7. Structural Preferences\n\nDo they use lists? Numbered or bulleted?\nHeaders or flowing prose?\nShort paragraphs (1-2 sentences) or longer blocks?\nDo they use bold/italic for emphasis?\nDo they end with a CTA, a question, or a statement?\n\n8. Editing Instincts\n\nDo they tend to cut shorter or add more?\nWhat do they delete first? (Usually: hedging words, jargon, or filler)\nWhat's their \"red flag\" — the thing that makes them cringe in writing?"
      },
      {
        "title": "Phase 2: Build the Voice DNA Profile",
        "body": "After extraction, generate a structured Voice DNA document. This becomes the permanent reference for all future content."
      },
      {
        "title": "Voice DNA Profile Template",
        "body": "# [Name]'s Voice DNA Profile\n*Generated from [X] writing samples on [date]*\n\n---\n\n## Voice Foundation\n**Core Identity:** [One sentence — who they are as a communicator]\n**Natural Role:** [How they relate to their audience — teacher? Coach? Peer? Provocateur?]\n**Authority Zones:** [Topics where they write with full confidence]\n**Learning Zones:** [Topics where they're exploring/experimenting]\n**Writing Philosophy:** [Their implicit belief about communication — extracted, not asked]\n\n---\n\n## Sentence Architecture\n- Average sentence length: [short/medium/long]\n- Uses fragments: [yes/no — with examples]\n- Typical paragraph length: [1-2 / 3-4 / 5+ sentences]\n- Rhythm pattern: [describe their cadence]\n\n## Opening Patterns\n- Primary hook style: [question / bold statement / story / contrarian]\n- First-line energy: [1-10 scale]\n- Context-setting: [dives in / sets scene first]\n\n**Their best opening lines (from samples):**\n1. \"[example]\"\n2. \"[example]\"\n3. \"[example]\"\n\n## Transition Signatures\n[List 8-12 of their actual transition phrases, organized by type]\n\n### Authority Transitions:\n- \"[phrase]\"\n- \"[phrase]\"\n\n### Energy Transitions:\n- \"[phrase]\"\n- \"[phrase]\"\n\n### Story Bridges:\n- \"[phrase]\"\n- \"[phrase]\"\n\n## Energy Profile\n- Baseline energy: [calm / warm / enthusiastic / electric]\n- High-energy triggers: [what topics fire them up]\n- Excitement markers: [how they show it — exclamation marks, caps, power words]\n- Humor style: [type and frequency]\n\n## Confidence Calibration\n\n### Write with FULL AUTHORITY when discussing:\n- [topic 1]\n- [topic 2]\n- [topic 3]\n**Voice:** Confident, definitive\n**Phrases:** \"[their authority phrases]\"\n\n### Write with INFORMED PERSPECTIVE when discussing:\n- [topic 1]\n- [topic 2]\n**Voice:** Curious, exploratory but still confident\n**Phrases:** \"[their learning phrases]\"\n\n## Vocabulary\n**Favorites:** [words they use often]\n**Allergies:** [words they never use or hate]\n**Jargon stance:** [embraces / avoids / selective]\n**Formality:** [scale 1-10]\n**Profanity:** [none / occasional / frequent]\n\n## Structural Preferences\n- Lists: [yes/no, numbered/bulleted]\n- Headers: [yes/no]\n- Paragraph style: [short punchy / mixed / long form]\n- Emphasis: [bold / italic / caps / none]\n- Endings: [CTA / question / statement / callback to opening]\n\n## Editing Instincts\n- Default edit direction: [cuts shorter / adds more]\n- First things they'd delete: [hedging / jargon / filler / examples]\n- Red flags: [what makes them cringe]\n\n---\n\n## Voice Check Questions\nBefore publishing as [Name], ask:\n1. Energy Test: Does this feel like [their baseline] or flat?\n2. Authority Test: Am I writing from confidence where they'd be confident?\n3. Simplicity Test: Would [their target audience] get this immediately?\n4. Landing Test: Did I land the plane or keep circling?\n5. Authenticity Test: Does this sound like [Name] or like \"AI writing\"?\n\n## Example Transformations\n\n**Generic AI version:**\n\"[example of how AI would write it]\"\n\n**In [Name]'s voice:**\n\"[example rewritten in their actual voice]\""
      },
      {
        "title": "Phase 3: Generate Voice-Matched Content",
        "body": "With the Voice DNA Profile built, use it to generate any content type."
      },
      {
        "title": "Content Generation Process",
        "body": "Load the Voice DNA Profile (read the profile before writing anything)\nIdentify the content type (social post, article, email, proposal, etc.)\nCheck confidence calibration — Is this topic in their authority zone or learning zone?\nWrite the first draft using their patterns:\n\nOpen with their preferred hook style\nUse their transition signatures (not generic ones)\nMatch their sentence architecture\nApply their energy level\nEnd with their preferred closing style\n\n\nRun the Voice Check — Ask all 5 questions from the profile\nApply their editing instincts — Would they cut this shorter? Remove the hedging? Add more energy?"
      },
      {
        "title": "Platform-Specific Adaptations",
        "body": "The same voice adapts differently per platform. Apply these modifications ON TOP of the base voice:\n\nLinkedIn\n\nSlightly more structured (headers, line breaks)\nAuthority dialed up 10%\nHook must work in first 2 lines (before \"see more\")\nProfessional energy, not casual\nEnd with engagement driver (question or bold statement)\n\nX/Twitter\n\nPunchiest version of their voice\nFragments encouraged\nEnergy at maximum\nNo hedging at all — every character counts\nThread format: each tweet must stand alone AND build\n\nEmail\n\nMost conversational version\nCan be slightly longer\nPersonal touches (references to shared context)\nClear CTA at the end\nWarmth > authority\n\nLong-form (Blog/Article)\n\nFull voice expression\nStories and examples get more room\nStructural preferences fully applied\nMix of authority and learning zones\nLand the plane clearly at the end\n\nProposals/Professional Documents\n\nAuthority mode by default\nConcise, confident, no filler\nProof and specifics over claims\nClear structure (they're scanning, not reading)"
      },
      {
        "title": "Ongoing Calibration",
        "body": "When the user edits your output, note WHAT they changed. Those edits are voice data.\nIf they say \"this doesn't sound like me,\" ask which specific parts feel off.\nUpdate the Voice DNA Profile quarterly with new samples and corrections."
      },
      {
        "title": "Common Failure Modes and Fixes",
        "body": "ProblemCauseFix\"Sounds too formal\"Formality level too highAdd more contractions, fragments, casual transitions\"Sounds too casual\"Energy overdonePull back excitement markers, add more structure\"Sounds like AI\"Generic transitions, no voice fingerprintsReplace ALL generic phrases with their actual transitions\"Too hedgy\"Writing in authority zone with learning-zone voiceCheck confidence calibration, remove hedging language\"Not enough energy\"Baseline energy too lowAdd their power words, shorten sentences, punch up hooks\"Doesn't land the plane\"Missing their closing patternApply their specific ending style from the profile"
      },
      {
        "title": "Guardrails",
        "body": "Never fabricate voice samples. Only extract from content the user provides.\nNever assume authority zones. Ask or infer from samples — don't guess.\nAlways produce the Voice DNA Profile first before generating content. Skip this step and the output will be generic.\nIf fewer than 3 samples provided, flag that the profile will be less accurate and ask for more.\nLog all voice profile updates so changes can be reviewed and reverted.\nThe Voice DNA Profile is the user's asset. Output it in full so they own it and can use it anywhere."
      },
      {
        "title": "Quick Start",
        "body": "Minimum viable run:\n\nUser provides 3 writing samples\nSkill extracts Voice DNA → generates profile\nUser reviews profile, corrects anything off\nSkill generates requested content using the profile\n\nTime: 15-20 minutes for profile. 2-5 minutes per content piece after that.\n\nThe profile is reusable forever. Build once, use for every piece of content going forward. Update when their voice evolves."
      }
    ],
    "body": "Voice-Matched Content System\n\nThe #1 complaint about AI content: \"It doesn't sound like me.\"\n\nThis skill fixes that permanently. Not with a one-line tone instruction. With a complete voice operating system that understands HOW someone communicates — their patterns, energy, confidence zones, transitions, and editing instincts.\n\nBuilt from a real voice extraction methodology refined over 15+ years of brand strategy work.\n\nRouting\n✅ Use This Skill When:\nSomeone wants to capture their authentic writing voice\nContent \"sounds too AI\" and needs to match the creator's real style\nBuilding a voice guide for consistent content across platforms\nGhostwriting or creating content on behalf of someone\nUser says: \"write like me,\" \"capture my voice,\" \"this doesn't sound like me,\" \"make it sound like me,\" \"voice guide,\" \"brand voice\"\n❌ Do NOT Use When:\nWriting generic content with no voice reference → Use standard content skills\nEditing existing copy for grammar/clarity only → Use copy-editing tools\nCreating content strategy (what to write, not how) → Use content strategy skills\nNeed a brand messaging framework → Use positioning skills\nInputs Required:\nMinimum: 3 writing samples (blog posts, emails, social posts, transcripts — anything they've written)\nBetter: 5-10 samples across different contexts (professional, casual, teaching, selling)\nBest: Samples + a 5-minute conversation about how they think about communication\nOutputs Produced:\nComplete Voice DNA Profile (reusable across all future content)\nContent generated in their authenticated voice\nPlatform-specific voice adaptations (LinkedIn vs X vs email vs proposals)\nVoice consistency checklist for self-editing\nPhase 1: Voice Extraction\nStep 1: Collect Samples\n\nAsk for 3-10 writing samples. The more variety, the better the profile.\n\nGood samples:\n\nSocial posts they're proud of\nEmails they wrote quickly (less filtered = more authentic)\nBlog posts or articles\nPodcast/video transcripts (spoken voice often reveals real patterns)\nTexts or casual messages (if they're comfortable sharing)\n\nWhat to tell the user:\n\n\"Send me 3-5 pieces of writing you've done. Mix of professional and casual is ideal. The ones you wrote fast without overthinking are often the most useful — that's where your real voice lives.\"\n\nStep 2: Analyze Voice DNA\n\nRead all samples and extract these 8 dimensions:\n\n1. Sentence Architecture\nAverage sentence length (short and punchy? Long and flowing?)\nDo they use fragments? (\"Not a chance.\" / \"Game over.\")\nSentence variety pattern (short-short-long? Building momentum?)\nParagraph length preference\n2. Opening Patterns (How They Start)\nDo they hook with a question? A bold statement? A story? A contrarian take?\nFirst-line energy level (explosive vs. measured)\nDo they set context first or dive straight in?\n3. Transition Signatures\n\nMap their recurring bridge phrases. Everyone has them. Examples:\n\n\"Here's the thing...\"\n\"What that means is...\"\n\"The reality is...\"\n\"But here's what's interesting...\"\n\"Let me break this down...\"\n\"So here's what happened...\"\n\nExtract at least 8-10 transition phrases from their samples. These are fingerprints.\n\n4. Energy Mapping\nBaseline energy level (calm authority? Electric enthusiasm? Quiet confidence?)\nWhat triggers their high-energy mode?\nHow do they express excitement? (Exclamation marks? ALL CAPS? Power words?)\nDo they use humor? What kind? (Self-deprecating? Observational? Sarcastic?)\n5. Authority Zones vs. Learning Zones\n\nThis is critical and most voice tools miss it entirely.\n\nAuthority zones = Topics where they write with full confidence\n\nDefinitive language: \"Here's what works,\" \"The data shows,\" \"What I've learned\"\nNo hedging, no \"I think maybe\"\n\nLearning zones = Topics where they're exploring\n\nExploratory language: \"What I'm seeing,\" \"In my experience so far,\" \"What I'm learning\"\nStill confident, but framed as ongoing discovery\n\nMap which topics fall into which zone. This prevents the AI from writing with false authority on topics the person is still learning about.\n\n6. Vocabulary Fingerprint\nWords they use often (favorites)\nWords they NEVER use (allergies)\nIndustry jargon: do they embrace it or avoid it?\nFormality level (contractions? Slang? Academic?)\nProfanity comfort level\n7. Structural Preferences\nDo they use lists? Numbered or bulleted?\nHeaders or flowing prose?\nShort paragraphs (1-2 sentences) or longer blocks?\nDo they use bold/italic for emphasis?\nDo they end with a CTA, a question, or a statement?\n8. Editing Instincts\nDo they tend to cut shorter or add more?\nWhat do they delete first? (Usually: hedging words, jargon, or filler)\nWhat's their \"red flag\" — the thing that makes them cringe in writing?\nPhase 2: Build the Voice DNA Profile\n\nAfter extraction, generate a structured Voice DNA document. This becomes the permanent reference for all future content.\n\nVoice DNA Profile Template\n# [Name]'s Voice DNA Profile\n*Generated from [X] writing samples on [date]*\n\n---\n\n## Voice Foundation\n**Core Identity:** [One sentence — who they are as a communicator]\n**Natural Role:** [How they relate to their audience — teacher? Coach? Peer? Provocateur?]\n**Authority Zones:** [Topics where they write with full confidence]\n**Learning Zones:** [Topics where they're exploring/experimenting]\n**Writing Philosophy:** [Their implicit belief about communication — extracted, not asked]\n\n---\n\n## Sentence Architecture\n- Average sentence length: [short/medium/long]\n- Uses fragments: [yes/no — with examples]\n- Typical paragraph length: [1-2 / 3-4 / 5+ sentences]\n- Rhythm pattern: [describe their cadence]\n\n## Opening Patterns\n- Primary hook style: [question / bold statement / story / contrarian]\n- First-line energy: [1-10 scale]\n- Context-setting: [dives in / sets scene first]\n\n**Their best opening lines (from samples):**\n1. \"[example]\"\n2. \"[example]\"\n3. \"[example]\"\n\n## Transition Signatures\n[List 8-12 of their actual transition phrases, organized by type]\n\n### Authority Transitions:\n- \"[phrase]\"\n- \"[phrase]\"\n\n### Energy Transitions:\n- \"[phrase]\"\n- \"[phrase]\"\n\n### Story Bridges:\n- \"[phrase]\"\n- \"[phrase]\"\n\n## Energy Profile\n- Baseline energy: [calm / warm / enthusiastic / electric]\n- High-energy triggers: [what topics fire them up]\n- Excitement markers: [how they show it — exclamation marks, caps, power words]\n- Humor style: [type and frequency]\n\n## Confidence Calibration\n\n### Write with FULL AUTHORITY when discussing:\n- [topic 1]\n- [topic 2]\n- [topic 3]\n**Voice:** Confident, definitive\n**Phrases:** \"[their authority phrases]\"\n\n### Write with INFORMED PERSPECTIVE when discussing:\n- [topic 1]\n- [topic 2]\n**Voice:** Curious, exploratory but still confident\n**Phrases:** \"[their learning phrases]\"\n\n## Vocabulary\n**Favorites:** [words they use often]\n**Allergies:** [words they never use or hate]\n**Jargon stance:** [embraces / avoids / selective]\n**Formality:** [scale 1-10]\n**Profanity:** [none / occasional / frequent]\n\n## Structural Preferences\n- Lists: [yes/no, numbered/bulleted]\n- Headers: [yes/no]\n- Paragraph style: [short punchy / mixed / long form]\n- Emphasis: [bold / italic / caps / none]\n- Endings: [CTA / question / statement / callback to opening]\n\n## Editing Instincts\n- Default edit direction: [cuts shorter / adds more]\n- First things they'd delete: [hedging / jargon / filler / examples]\n- Red flags: [what makes them cringe]\n\n---\n\n## Voice Check Questions\nBefore publishing as [Name], ask:\n1. Energy Test: Does this feel like [their baseline] or flat?\n2. Authority Test: Am I writing from confidence where they'd be confident?\n3. Simplicity Test: Would [their target audience] get this immediately?\n4. Landing Test: Did I land the plane or keep circling?\n5. Authenticity Test: Does this sound like [Name] or like \"AI writing\"?\n\n## Example Transformations\n\n**Generic AI version:**\n\"[example of how AI would write it]\"\n\n**In [Name]'s voice:**\n\"[example rewritten in their actual voice]\"\n\nPhase 3: Generate Voice-Matched Content\n\nWith the Voice DNA Profile built, use it to generate any content type.\n\nContent Generation Process\nLoad the Voice DNA Profile (read the profile before writing anything)\nIdentify the content type (social post, article, email, proposal, etc.)\nCheck confidence calibration — Is this topic in their authority zone or learning zone?\nWrite the first draft using their patterns:\nOpen with their preferred hook style\nUse their transition signatures (not generic ones)\nMatch their sentence architecture\nApply their energy level\nEnd with their preferred closing style\nRun the Voice Check — Ask all 5 questions from the profile\nApply their editing instincts — Would they cut this shorter? Remove the hedging? Add more energy?\nPlatform-Specific Adaptations\n\nThe same voice adapts differently per platform. Apply these modifications ON TOP of the base voice:\n\nLinkedIn\nSlightly more structured (headers, line breaks)\nAuthority dialed up 10%\nHook must work in first 2 lines (before \"see more\")\nProfessional energy, not casual\nEnd with engagement driver (question or bold statement)\nX/Twitter\nPunchiest version of their voice\nFragments encouraged\nEnergy at maximum\nNo hedging at all — every character counts\nThread format: each tweet must stand alone AND build\nEmail\nMost conversational version\nCan be slightly longer\nPersonal touches (references to shared context)\nClear CTA at the end\nWarmth > authority\nLong-form (Blog/Article)\nFull voice expression\nStories and examples get more room\nStructural preferences fully applied\nMix of authority and learning zones\nLand the plane clearly at the end\nProposals/Professional Documents\nAuthority mode by default\nConcise, confident, no filler\nProof and specifics over claims\nClear structure (they're scanning, not reading)\nPhase 4: Voice Consistency Maintenance\nOngoing Calibration\nWhen the user edits your output, note WHAT they changed. Those edits are voice data.\nIf they say \"this doesn't sound like me,\" ask which specific parts feel off.\nUpdate the Voice DNA Profile quarterly with new samples and corrections.\nCommon Failure Modes and Fixes\nProblem\tCause\tFix\n\"Sounds too formal\"\tFormality level too high\tAdd more contractions, fragments, casual transitions\n\"Sounds too casual\"\tEnergy overdone\tPull back excitement markers, add more structure\n\"Sounds like AI\"\tGeneric transitions, no voice fingerprints\tReplace ALL generic phrases with their actual transitions\n\"Too hedgy\"\tWriting in authority zone with learning-zone voice\tCheck confidence calibration, remove hedging language\n\"Not enough energy\"\tBaseline energy too low\tAdd their power words, shorten sentences, punch up hooks\n\"Doesn't land the plane\"\tMissing their closing pattern\tApply their specific ending style from the profile\nGuardrails\nNever fabricate voice samples. Only extract from content the user provides.\nNever assume authority zones. Ask or infer from samples — don't guess.\nAlways produce the Voice DNA Profile first before generating content. Skip this step and the output will be generic.\nIf fewer than 3 samples provided, flag that the profile will be less accurate and ask for more.\nLog all voice profile updates so changes can be reviewed and reverted.\nThe Voice DNA Profile is the user's asset. Output it in full so they own it and can use it anywhere.\nQuick Start\n\nMinimum viable run:\n\nUser provides 3 writing samples\nSkill extracts Voice DNA → generates profile\nUser reviews profile, corrects anything off\nSkill generates requested content using the profile\n\nTime: 15-20 minutes for profile. 2-5 minutes per content piece after that.\n\nThe profile is reusable forever. Build once, use for every piece of content going forward. Update when their voice evolves."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/BrianRWagner/voice-matched-content-system",
    "publisherUrl": "https://clawhub.ai/BrianRWagner/voice-matched-content-system",
    "owner": "BrianRWagner",
    "version": "2.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/voice-matched-content-system",
    "downloadUrl": "https://openagent3.xyz/downloads/voice-matched-content-system",
    "agentUrl": "https://openagent3.xyz/skills/voice-matched-content-system/agent",
    "manifestUrl": "https://openagent3.xyz/skills/voice-matched-content-system/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/voice-matched-content-system/agent.md"
  }
}