[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FQMQM0FSZJ54YBE34HTGD":3,"skill-same:01M70FQMQM0FSZJ54YBE34HTGD":78},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70FQMQM0FSZJ54YBE34HTGD","content-engine",null,"Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcontent-engine\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"content engine","content","engine","use","linkedin","for","platform","campaigns","source","asset","scripts","native","youtube","threads","create","across","when","social","tiktok","posts","2026-11-10 10:12:30",false,"---\nname: content-engine\ndescription: Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.\nmetadata:\n  origin: ECC\n---\n\n# Content Engine\n\nBuild platform-native content without flattening the author's real voice into platform slop.\n\n## When to Activate\n\n- writing X posts or threads\n- drafting LinkedIn posts or launch updates\n- scripting short-form video or YouTube explainers\n- repurposing articles, podcasts, demos, docs, or internal notes into public content\n- building a launch sequence or ongoing content system around a product, insight, or narrative\n\n## Non-Negotiables\n\n1. Start from source material, not generic post formulas.\n2. Adapt the format for the platform, not the persona.\n3. One post should carry one actual claim.\n4. Specificity beats adjectives.\n5. No engagement bait unless the user explicitly asks for it.\n\n## Source-First Workflow\n\nBefore drafting, identify the source set:\n- published articles\n- notes or internal memos\n- product demos\n- docs or changelogs\n- transcripts\n- screenshots\n- prior posts from the same author\n\nIf the user wants a specific voice, build a voice profile from real examples before writing.\nUse `brand-voice` as the canonical workflow when voice consistency matters across more than one output.\n\n## Voice Handling\n\n`brand-voice` is the canonical voice layer.\n\nRun it first when:\n\n- there are multiple downstream outputs\n- the user explicitly cares about writing style\n- the content is launch, outreach, or reputation-sensitive\n\nReuse the resulting `VOICE PROFILE` here instead of rebuilding a second voice model.\nIf the user wants Affaan \u002F ECC voice specifically, still treat `brand-voice` as the source of truth and feed it the best live or source-derived material available.\n\n## Hard Bans\n\nDelete and rewrite any of these:\n- \"In today's rapidly evolving landscape\"\n- \"game-changer\", \"revolutionary\", \"cutting-edge\"\n- \"here's why this matters\" unless it is followed immediately by something concrete\n- ending with a LinkedIn-style question just to farm replies\n- forced casualness on LinkedIn\n- fake engagement padding that was not present in the source material\n\n## Platform Adaptation Rules\n\n### X\n\n- open with the strongest claim, artifact, or tension\n- keep the compression if the source voice is compressed\n- if writing a thread, each post must advance the argument\n- do not pad with context the audience does not need\n\n### LinkedIn\n\n- expand only enough for people outside the immediate niche to follow\n- do not turn it into a fake lesson post unless the source material actually is reflective\n- no corporate inspiration cadence\n- no praise-stacking, no \"journey\" filler\n\n### Short Video\n\n- script around the visual sequence and proof points\n- first seconds should show the result, problem, or punch\n- do not write narration that sounds better on paper than on screen\n\n### YouTube\n\n- show the result or tension early\n- organize by argument or progression, not filler sections\n- use chaptering only when it helps clarity\n\n### Newsletter\n\n- open with the point, conflict, or artifact\n- do not spend the first paragraph warming up\n- every section needs to add something new\n\n## Repurposing Flow\n\n1. Pick the anchor asset.\n2. Extract 3 to 7 atomic claims or scenes.\n3. Rank them by sharpness, novelty, and proof.\n4. Assign one strong idea per output.\n5. Adapt structure for each platform.\n6. Strip platform-shaped filler.\n7. Run the quality gate.\n\n## Deliverables\n\nWhen asked for a campaign, return:\n- a short voice profile if voice matching matters\n- the core angle\n- platform-native drafts\n- posting order only if it helps execution\n- gaps that must be filled before publishing\n\n## Quality Gate\n\nBefore delivering:\n- every draft sounds like the intended author, not the platform stereotype\n- every draft contains a real claim, proof point, or concrete observation\n- no generic hype language remains\n- no fake engagement bait remains\n- no duplicated copy across platforms unless requested\n- any CTA is earned and user-approved\n\n## Related Skills\n\n- `brand-voice` for source-derived voice profiles\n- `crosspost` for platform-specific distribution\n- `x-api` for sourcing recent posts and publishing approved X output\n","# Content Engine\n\nBuild platform-native content without flattening the author's real voice into platform slop.\n\n## When to Activate\n\n- writing X posts or threads\n- drafting LinkedIn posts or launch updates\n- scripting short-form video or YouTube explainers\n- repurposing articles, podcasts, demos, docs, or internal notes into public content\n- building a launch sequence or ongoing content system around a product, insight, or narrative\n\n## Non-Negotiables\n\n1. Start from source material, not generic post formulas.\n2. Adapt the format for the platform, not the persona.\n3. One post should carry one actual claim.\n4. Specificity beats adjectives.\n5. No engagement bait unless the user explicitly asks for it.\n\n## Source-First Workflow\n\nBefore drafting, identify the source set:\n- published articles\n- notes or internal memos\n- product demos\n- docs or changelogs\n- transcripts\n- screenshots\n- prior posts from the same author\n\nIf the user wants a specific voice, build a voice profile from real examples before writing.\nUse `brand-voice` as the canonical workflow when voice consistency matters across more than one output.\n\n## Voice Handling\n\n`brand-voice` is the canonical voice layer.\n\nRun it first when:\n\n- there are multiple downstream outputs\n- the user explicitly cares about writing style\n- the content is launch, outreach, or reputation-sensitive\n\nReuse the resulting `VOICE PROFILE` here instead of rebuilding a second voice model.\nIf the user wants Affaan \u002F ECC voice specifically, still treat `brand-voice` as the source of truth and feed it the best live or source-derived material available.\n\n## Hard Bans\n\nDelete and rewrite any of these:\n- \"In today's rapidly evolving landscape\"\n- \"game-changer\", \"revolutionary\", \"cutting-edge\"\n- \"here's why this matters\" unless it is followed immediately by something concrete\n- ending with a LinkedIn-style question just to farm replies\n- forced casualness on LinkedIn\n- fake engagement padding that was not present in the source material\n\n## Platform Adaptation Rules\n\n### X\n\n- open with the strongest claim, artifact, or tension\n- keep the compression if the source voice is compressed\n- if writing a thread, each post must advance the argument\n- do not pad with context the audience does not need\n\n### LinkedIn\n\n- expand only enough for people outside the immediate niche to follow\n- do not turn it into a fake lesson post unless the source material actually is reflective\n- no corporate inspiration cadence\n- no praise-stacking, no \"journey\" filler\n\n### Short Video\n\n- script around the visual sequence and proof points\n- first seconds should show the result, problem, or punch\n- do not write narration that sounds better on paper than on screen\n\n### YouTube\n\n- show the result or tension early\n- organize by argument or progression, not filler sections\n- use chaptering only when it helps clarity\n\n### Newsletter\n\n- open with the point, conflict, or artifact\n- do not spend the first paragraph warming up\n- every section needs to add something new\n\n## Repurposing Flow\n\n1. Pick the anchor asset.\n2. Extract 3 to 7 atomic claims or scenes.\n3. Rank them by sharpness, novelty, and proof.\n4. Assign one strong idea per output.\n5. Adapt structure for each platform.\n6. Strip platform-shaped filler.\n7. Run the quality gate.\n\n## Deliverables\n\nWhen asked for a campaign, return:\n- a short voice profile if voice matching matters\n- the core angle\n- platform-native drafts\n- posting order only if it helps execution\n- gaps that must be filled before publishing\n\n## Quality Gate\n\nBefore delivering:\n- every draft sounds like the intended author, not the platform stereotype\n- every draft contains a real claim, proof point, or concrete observation\n- no generic hype language remains\n- no fake engagement bait remains\n- no duplicated copy across platforms unless requested\n- any CTA is earned and user-approved\n\n## Related Skills\n\n- `brand-voice` for source-derived voice profiles\n- `crosspost` for platform-specific distribution\n- `x-api` for sourcing recent posts and publishing approved X output\n",{"name":5,"metadata":54,"description":7},{"origin":55},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fcontent-engine",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 06:54:12",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill content-engine",{"tool":70,"command":71},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill content-engine",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill content-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcontent-engine\u002FSKILL.md",true,[],[79,87,109,130,149,164],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M72JT3YP1SQHD0MANGDXQ4RT","higgsfield-websites","Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1\u002FR2\u002FKV\u002FDO\u002FContainers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references\u002Fwebsite-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references\u002Fapp-flow.md), `game` (realtime multiplayer rooms — references\u002Fgame-flow.md). Routes to the right flow; each carries its own rules and deploy\u002Fpublish gates.\nUse when: \"build me a website\", \"make a landing page\", \"create a web app\", \"build a SaaS dashboard \u002F portfolio\", \"make me a game\", \"deploy this site\", \"publish\". Also owns GAME ART: \"make a spritesheet\", \"tileable texture\", \"animate a 3D character\", game music\u002FSFX — see the game-* references.\nNOT for: single image\u002Fvideo\u002Faudio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fhiggsfield-ai_skills\u002Fhiggsfield-websites\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":101,"publishedAt":49},"01M70JPK8HAXXA85P7Q8NKZZYG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-skills\u002FSKILL.md",[93,96,97,98],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[102,103,104,105,32,106,107,45,108],"writing","writing skills","editing","deployment","Existing","new","work",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":49},"01M70JP4PHBH1CQVVDWZ94W159","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-plans\u002FSKILL.md",[115,116,117],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":118,"categoryName":119,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[102,121,122,123,45,124,34,32,125,126,127,128,129],"writing plans","plans","you","code","requirements","task","multi","spec","multi-step task",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":49},"01M70JNTYVGXFZT8PASZ844TH8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fverification-before-completion\u002FSKILL.md",[],[137,138,139,140,141,142,32,143,144,145,45,146,108,147,148],"verification","verification before completion","complete","about","output","assertions","prs","evidence","claim","claims","commands","running",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":49},"01M70JNGVSQDESWN0Q5BPJ875V","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-superpowers\u002FSKILL.md",[155],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,159,160,32,45,161,162,163],"using superpowers","superpowers","conversation","how to","how","find","questions",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":49},"01M70JN57CE588NPYPYTWH1DWG","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[171,172,173,174,175,176,45,108,177,178,40,179,180,181,182,122,32,183,184],"using git worktrees","Using git","git","worktrees","git worktrees","implementation","git worktree","worktree","Tools","isolation","fallback","feature","via","workspace"]