[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMTBN0NJPTZ5GDXSWQ22HB":3,"skill-same:01M7EMTBN0NJPTZ5GDXSWQ22HB":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7EMTBN0NJPTZ5GDXSWQ22HB","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.","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Faffaan-m\u002FECC\u002Fbrand-voice\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\nlicense: MIT\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,"license":14,"description":7},"main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Faffaan-m\u002FECC\u002Fbrand-voice","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill brand-voice",{"tool":35,"command":36},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill brand-voice",{"tool":38,"command":39},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill brand-voice","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Faffaan-m\u002FECC\u002Fbrand-voice\u002FSKILL.md",true,[43,49],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"agents\u002Fopenai.yaml","REFERENCE","参考文档",259,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Faffaan-m\u002FECC\u002Fbrand-voice\u002Fagents\u002Fopenai.yaml",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fvoice-profile-schema.md",1063,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Faffaan-m\u002FECC\u002Fbrand-voice\u002Freferences\u002Fvoice-profile-schema.md",[54,62,70,78,85,92],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]