[{"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 21:16:57",{"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,95,102,109,116],{"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},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":93,"publishedAt":94},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":94},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":94},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"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":115,"publishedAt":94},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":94},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]