[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P1EVRCHRVY4APQ87YSQT8":3,"skill-same:01M71P1EVRCHRVY4APQ87YSQT8":82},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":59,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M71P1EVRCHRVY4APQ87YSQT8","social-media",null,"Use when an org role acts as social media manager and must run a platform-native presence: per-platform content, posting cadence and fast community engagement. Covers audience-based platform choice, per-platform briefs and KPIs and conversation-driving content. Role guidance; for strategy playbooks see social-media-manager.","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\u002Fsocial-media\u002FSKILL.md",[17,22,27],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"social","social media","Media","posting","as","briefs","org","manager","marketing","run","native","social media manager","monomind","when","presence","writing","cadence","choice","community","conversation","2026-11-10 10:56:23",false,"---\nname: social-media\ndescription: \"Use when an org role acts as social media manager and must run a platform-native presence: per-platform content, posting cadence and fast community engagement. Covers audience-based platform choice, per-platform briefs and KPIs and conversation-driving content. Role guidance; for strategy playbooks see social-media-manager.\"\ntags: [\"writing\",\"marketing\",\"social\",\"content\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Social Media — Best Practices\n\n## Focus\nRuns platform-native social presence — content, scheduling, and community engagement — tuned to each platform's format and audience rather than a single cross-posted strategy.\n\n## Best practices\n- Choose platforms based on audience research, not industry trends or personal preference.\n- Give each platform its own brief, format, and KPI — a platform-native approach beats a single repurposed asset everywhere.\n- Prioritize consistency of posting over raw volume; a steady cadence outperforms sporadic viral attempts long-term.\n- Respond quickly to comments and DMs — response speed is itself a core driver of engagement and part of social customer service.\n- Optimize for content that sparks conversation and saves, not just impressions or views.\n- Let real business goals (leads, signups, retention) drive strategy, not vanity metrics alone.\n- Use AI to speed up production while keeping human review — content with visible human experience and personality still outperforms generic AI output.\n\n## Common pitfalls\n- Cross-posting identical content to every platform instead of adapting tone\u002Fformat per channel.\n- Treating follower count or likes as success metrics disconnected from actual business outcomes.\n- Slow or inconsistent response times to comments\u002FDMs, which reads as neglect and suppresses reach.\n- Publishing on a reactive, trend-chasing basis instead of a planned, consistent cadence.\n\n## Tools & techniques\n- Platform-specific content calendars with separate briefs per channel.\n- Short-form vertical video prioritization (Reels\u002FShorts) where the algorithm rewards it, paired with native community engagement (replies, polls, comments) rather than one-way broadcasting.\n- Weekly performance review against a small, fixed set of indicators per platform, with findings translated into concrete changes.\n- Escalation path for negative\u002Fsensitive comments to human review before public reply.\n","# Social Media — Best Practices\n\n## Focus\nRuns platform-native social presence — content, scheduling, and community engagement — tuned to each platform's format and audience rather than a single cross-posted strategy.\n\n## Best practices\n- Choose platforms based on audience research, not industry trends or personal preference.\n- Give each platform its own brief, format, and KPI — a platform-native approach beats a single repurposed asset everywhere.\n- Prioritize consistency of posting over raw volume; a steady cadence outperforms sporadic viral attempts long-term.\n- Respond quickly to comments and DMs — response speed is itself a core driver of engagement and part of social customer service.\n- Optimize for content that sparks conversation and saves, not just impressions or views.\n- Let real business goals (leads, signups, retention) drive strategy, not vanity metrics alone.\n- Use AI to speed up production while keeping human review — content with visible human experience and personality still outperforms generic AI output.\n\n## Common pitfalls\n- Cross-posting identical content to every platform instead of adapting tone\u002Fformat per channel.\n- Treating follower count or likes as success metrics disconnected from actual business outcomes.\n- Slow or inconsistent response times to comments\u002FDMs, which reads as neglect and suppresses reach.\n- Publishing on a reactive, trend-chasing basis instead of a planned, consistent cadence.\n\n## Tools & techniques\n- Platform-specific content calendars with separate briefs per channel.\n- Short-form vertical video prioritization (Reels\u002FShorts) where the algorithm rewards it, paired with native community engagement (replies, polls, comments) rather than one-way broadcasting.\n- Weekly performance review against a small, fixed set of indicators per platform, with findings translated into concrete changes.\n- Escalation path for negative\u002Fsensitive comments to human review before public reply.\n",{"name":5,"tags":56,"tools":58,"source":59,"license":14,"description":7},[46,39,31,57],"content",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsocial-media",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add monoes\u002Fmonomind --skill social-media",{"tool":74,"command":75},"bunx","bunx skills add monoes\u002Fmonomind --skill social-media",{"tool":77,"command":78},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill social-media","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsocial-media\u002FSKILL.md",true,[],[83,108,137,164,189,216],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":107},"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",[],[90,91,92,93,94,48,95,96,97,98,99,100,43,101,102,103,104,105,37,106],"zk","zk steward","steward","zero-knowledge","engineer","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","blockchain","2026-11-10 13:02:02",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":120,"publishedAt":107},"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",[116,119],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},[46,121,122,94,123,124,44,125,98,126,127,128,129,130,131,132,133,134,135,136],"writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":107},"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",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000031","产品经理",[130,148,149,150,151,96,152,44,153,154,155,129,156,157,158,159,160,161,162,163],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":107},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000033","数据分析师",[98,130,175,176,177,178,96,162,44,179,180,181,182,155,183,184,185,186,187,188],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":201,"publishedAt":107},"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",[195,198],{"categoryNo":196,"categoryName":197,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[202,203,204,205,177,206,207,208,209,97,210,211,212,98,43,183,213,214,215,185],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":223,"publishedAt":107},"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",[222],{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},[204,224,225,226,227,228,229,177,230,231,126,232,233,234,43,183,235,236,185,237],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]