[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JCSEBTW4YMYYX3RM5CTCEX":3,"skill-same:01M6JCSEBTW4YMYYX3RM5CTCEX":76},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6JCSEBTW4YMYYX3RM5CTCEX","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.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fcontent-engine\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"content","content engine","engine","source","create","for","threads","posts","native","multi","asset","scripts","platform","campaigns","across","social","tiktok","youtube","use","linkedin","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.\norigin: 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,"origin":53,"description":7},"ECC","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fecc\u002Fcontent-engine",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add S3YED\u002Fappie-kit --skill content-engine",{"tool":68,"command":69},"bunx","bunx skills add S3YED\u002Fappie-kit --skill content-engine",{"tool":71,"command":72},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill content-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fcontent-engine\u002FSKILL.md",true,[],[77,109,142,167,198,222],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":90,"publishedAt":48},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[83,86,89],{"categoryNo":84,"categoryName":85,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":121,"publishedAt":48},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":119,"categoryName":120,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师",[122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":150,"publishedAt":48},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[148,149],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":119,"categoryName":120,"taxonomyType":25,"taxonomyTypeDesc":26},[123,151,127,152,153,154,129,155,156,157,158,159,160,161,162,163,164,165,166,31],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":177,"publishedAt":48},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":48},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[204],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,33],"workflows","quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":235,"publishedAt":48},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[228,231,234],{"categoryNo":229,"categoryName":230,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":232,"categoryName":233,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[236,237,238,239,240,241,242,243,181,244,245,129,246,184,247,215,248,249,250,251],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]