[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MM4X3F0BPHG2RAVSEEEAQ":3,"skill-same:01M71MM4X3F0BPHG2RAVSEEEAQ":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":51,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M71MM4X3F0BPHG2RAVSEEEAQ","content-creator",null,"Use when an org role acts as content creator and must turn one core idea into platform-native assets across formats and platforms. Covers hooks, consistent voice and per-asset KPIs; for drafting specific posts and threads use content-engine.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-creator\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"creator","content","content creator","github","monomind","threads","engine","across","drafting","one","when","use","writing","hooks","social","for","core","platform","posts","as","2026-11-10 10:56:23",false,"---\nname: content-creator\ndescription: \"Use when an org role acts as content creator and must turn one core idea into platform-native assets across formats and platforms. Covers hooks, consistent voice and per-asset KPIs; for drafting specific posts and threads use content-engine.\"\ntags: [\"writing\",\"marketing\",\"content\",\"social\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Content Creator — Best Practices\n\n## Focus\nProduces and repurposes content across formats and platforms — turning one core idea into platform-native assets that build audience and drive measurable outcomes, not just volume.\n\n## Best practices\n- Define audience and goal before choosing platforms — don't try to be everywhere at once.\n- Create one core asset, then adapt it per platform's native format and expectations rather than cross-posting identically.\n- Prioritize short-form vertical video where discovery algorithms reward it (Reels, Shorts) without abandoning long-form where it drives deeper engagement.\n- Open with a strong, specific hook in the first 1-3 seconds\u002Flines — attention is won or lost immediately.\n- Keep branding and voice consistent across formats even as the format itself varies.\n- Check performance analytics regularly and let data — not intuition — decide what gets repeated or dropped.\n- Favor content that reflects real experience and specificity over generic, interchangeable AI-flavored output.\n\n## Common pitfalls\n- Publishing the same asset unchanged across every platform instead of adapting to format norms.\n- Optimizing for vanity metrics (views, likes) instead of the underlying business goal (leads, signups, retention).\n- Inconsistent posting cadence — sporadic bursts followed by silence perform worse than modest but steady output.\n- Treating repurposing as an afterthought instead of planning it into the original content's structure.\n\n## Tools & techniques\n- Content pillars\u002Fthemes to keep output focused rather than reactive to every trend.\n- A repurposing map: one long-form piece → clip\u002Fcarousel\u002Fthread\u002Fshort-form derivatives, each edited for its platform.\n- A small, consistent set of KPIs tracked per asset (e.g. watch-through rate, saves, click-through) reviewed on a weekly cadence.\n- Hook-testing: several opening variants for the same asset, measured against early retention\u002Fdrop-off.\n","# Content Creator — Best Practices\n\n## Focus\nProduces and repurposes content across formats and platforms — turning one core idea into platform-native assets that build audience and drive measurable outcomes, not just volume.\n\n## Best practices\n- Define audience and goal before choosing platforms — don't try to be everywhere at once.\n- Create one core asset, then adapt it per platform's native format and expectations rather than cross-posting identically.\n- Prioritize short-form vertical video where discovery algorithms reward it (Reels, Shorts) without abandoning long-form where it drives deeper engagement.\n- Open with a strong, specific hook in the first 1-3 seconds\u002Flines — attention is won or lost immediately.\n- Keep branding and voice consistent across formats even as the format itself varies.\n- Check performance analytics regularly and let data — not intuition — decide what gets repeated or dropped.\n- Favor content that reflects real experience and specificity over generic, interchangeable AI-flavored output.\n\n## Common pitfalls\n- Publishing the same asset unchanged across every platform instead of adapting to format norms.\n- Optimizing for vanity metrics (views, likes) instead of the underlying business goal (leads, signups, retention).\n- Inconsistent posting cadence — sporadic bursts followed by silence perform worse than modest but steady output.\n- Treating repurposing as an afterthought instead of planning it into the original content's structure.\n\n## Tools & techniques\n- Content pillars\u002Fthemes to keep output focused rather than reactive to every trend.\n- A repurposing map: one long-form piece → clip\u002Fcarousel\u002Fthread\u002Fshort-form derivatives, each edited for its platform.\n- A small, consistent set of KPIs tracked per asset (e.g. watch-through rate, saves, click-through) reviewed on a weekly cadence.\n- Hook-testing: several opening variants for the same asset, measured against early retention\u002Fdrop-off.\n",{"name":5,"tags":48,"tools":50,"source":51,"license":14,"description":7},[35,49,24,37],"marketing",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-creator",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add monoes\u002Fmonomind --skill content-creator",{"tool":66,"command":67},"bunx","bunx skills add monoes\u002Fmonomind --skill content-creator",{"tool":69,"command":70},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill content-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-creator\u002FSKILL.md",true,[],[75,102,133,159,182,209],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":101},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[82,83,84,85,86,87,88,89,90,91,92,93,27,94,95,96,97,98,99,100],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":116,"publishedAt":101},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[110,115],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[35,117,118,86,119,120,33,121,91,122,123,124,125,126,127,128,129,130,131,132],"writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":101},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理",[126,144,145,146,147,89,148,33,149,150,151,125,152,153,154,155,156,157,34,158],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":101},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师",[91,126,170,171,38,172,89,34,33,173,174,175,176,151,26,177,178,179,180,181],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","https","syntax","plugins","data",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":194,"publishedAt":101},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[188,191],{"categoryNo":189,"categoryName":190,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":192,"categoryName":193,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发",[195,196,197,198,38,199,200,201,202,90,203,204,205,91,27,26,206,207,208,178],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":216,"publishedAt":101},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[215],{"categoryNo":192,"categoryName":193,"taxonomyType":113,"taxonomyTypeDesc":114},[197,217,218,219,220,221,222,38,223,224,122,225,226,227,27,26,228,229,178,230],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]