[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZFTHHVZV4ZJEJCSP7S43Q":3,"skill-same:01M72ZFTHHVZV4ZJEJCSP7S43Q":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M72ZFTHHVZV4ZJEJCSP7S43Q","brand-voice",null,"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.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Fbrand-voice\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: brand-voice\ndescription: 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.\n---\n\n# Brand Voice\n\nBuild 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.\n\n## When to Activate\n\n- the user wants content or outreach in a specific voice\n- writing for X, LinkedIn, email, launch posts, threads, or product updates\n- adapting a known author's tone across channels\n- the existing content lane needs a reusable style system instead of one-off mimicry\n\n## Source Priority\n\nUse the strongest real source set available, in this order:\n\n1. recent original X posts and threads\n2. articles, essays, memos, launch notes, or newsletters\n3. real outbound emails or DMs that worked\n4. product docs, changelogs, README framing, and site copy\n\nDo not use generic platform exemplars as source material.\n\n## Collection Workflow\n\n1. Gather 5 to 20 representative samples when available.\n2. Prefer recent material over old material unless the user says the older writing is more canonical.\n3. Separate \"public launch voice\" from \"private working voice\" if the source set clearly splits.\n4. If live X access is available, use `x-api` to pull recent original posts before drafting.\n5. If site copy matters, include the current ECC landing page and repo\u002Fplugin framing.\n\n## What to Extract\n\n- rhythm and sentence length\n- compression vs explanation\n- capitalization norms\n- parenthetical use\n- question frequency and purpose\n- how sharply claims are made\n- how often numbers, mechanisms, or receipts show up\n- how transitions work\n- what the author never does\n\n## Output Contract\n\nProduce a reusable `VOICE PROFILE` block that downstream skills can consume directly. Use the schema in [references\u002Fvoice-profile-schema.md](references\u002Fvoice-profile-schema.md).\n\nKeep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.\n\n## Affaan \u002F ECC Defaults\n\nIf the user wants Affaan \u002F ECC voice and live sources are thin, start here unless newer source material overrides it:\n\n- direct, compressed, concrete\n- specifics, mechanisms, receipts, and numbers beat adjectives\n- parentheticals are for qualification, narrowing, or over-clarification\n- capitalization is conventional unless there is a real reason to break it\n- questions are rare and should not be used as bait\n- tone can be sharp, blunt, skeptical, or dry\n- transitions should feel earned, not smoothed over\n\n## Hard Bans\n\nDelete and rewrite any of these:\n\n- fake curiosity hooks\n- \"not X, just Y\"\n- \"no fluff\"\n- forced lowercase\n- LinkedIn thought-leader cadence\n- bait questions\n- \"Excited to share\"\n- generic founder-journey filler\n- corny parentheticals\n\n## Persistence Rules\n\n- Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session.\n- If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.\n- Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.\n\n## Downstream Use\n\nUse this skill before or inside:\n\n- `content-engine`\n- `crosspost`\n- `lead-intelligence`\n- article or launch writing\n- cold or warm outbound across X, LinkedIn, and email\n\nIf another skill already has a partial voice capture section, this skill is the canonical source of truth.\n","# Brand Voice\n\nBuild 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.\n\n## When to Activate\n\n- the user wants content or outreach in a specific voice\n- writing for X, LinkedIn, email, launch posts, threads, or product updates\n- adapting a known author's tone across channels\n- the existing content lane needs a reusable style system instead of one-off mimicry\n\n## Source Priority\n\nUse the strongest real source set available, in this order:\n\n1. recent original X posts and threads\n2. articles, essays, memos, launch notes, or newsletters\n3. real outbound emails or DMs that worked\n4. product docs, changelogs, README framing, and site copy\n\nDo not use generic platform exemplars as source material.\n\n## Collection Workflow\n\n1. Gather 5 to 20 representative samples when available.\n2. Prefer recent material over old material unless the user says the older writing is more canonical.\n3. Separate \"public launch voice\" from \"private working voice\" if the source set clearly splits.\n4. If live X access is available, use `x-api` to pull recent original posts before drafting.\n5. If site copy matters, include the current ECC landing page and repo\u002Fplugin framing.\n\n## What to Extract\n\n- rhythm and sentence length\n- compression vs explanation\n- capitalization norms\n- parenthetical use\n- question frequency and purpose\n- how sharply claims are made\n- how often numbers, mechanisms, or receipts show up\n- how transitions work\n- what the author never does\n\n## Output Contract\n\nProduce a reusable `VOICE PROFILE` block that downstream skills can consume directly. Use the schema in [references\u002Fvoice-profile-schema.md](references\u002Fvoice-profile-schema.md).\n\nKeep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.\n\n## Affaan \u002F ECC Defaults\n\nIf the user wants Affaan \u002F ECC voice and live sources are thin, start here unless newer source material overrides it:\n\n- direct, compressed, concrete\n- specifics, mechanisms, receipts, and numbers beat adjectives\n- parentheticals are for qualification, narrowing, or over-clarification\n- capitalization is conventional unless there is a real reason to break it\n- questions are rare and should not be used as bait\n- tone can be sharp, blunt, skeptical, or dry\n- transitions should feel earned, not smoothed over\n\n## Hard Bans\n\nDelete and rewrite any of these:\n\n- fake curiosity hooks\n- \"not X, just Y\"\n- \"no fluff\"\n- forced lowercase\n- LinkedIn thought-leader cadence\n- bait questions\n- \"Excited to share\"\n- generic founder-journey filler\n- corny parentheticals\n\n## Persistence Rules\n\n- Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session.\n- If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.\n- Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.\n\n## Downstream Use\n\nUse this skill before or inside:\n\n- `content-engine`\n- `crosspost`\n- `lead-intelligence`\n- article or launch writing\n- cold or warm outbound across X, LinkedIn, and email\n\nIf another skill already has a partial voice capture section, this skill is the canonical source of truth.\n",{"name":5,"description":7},"master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Fbrand-voice",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add SriramGandhiS\u002FSkills --skill brand-voice",{"tool":39,"command":40},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill brand-voice",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill brand-voice","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Fbrand-voice\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",259,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Fbrand-voice\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fvoice-profile-schema.md",1063,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Fbrand-voice\u002Freferences\u002Fvoice-profile-schema.md",[58,65,70,76,83,90],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":66,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]