[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MJ4MVKGDWFZAZFWR48E2H":3,"skill-same:01M71MJ4MVKGDWFZAZFWR48E2H":69},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":46,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M71MJ4MVKGDWFZAZFWR48E2H","collective-coord",null,"Use when an org role acts as collective intelligence coordinator and must merge what several agents found into one reconciled, retrievable knowledge store. Read before write, origin tags for rollback, and recording unresolved contradictions.","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\u002Fcollective-coord\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"collective coord","collective","https","rollback","read","merge","operations","github","monomind","store","coordination","tags","one","when","use","coordinator","knowledge","for","as","recording","2026-11-10 10:56:23",false,"---\nname: collective-coord\ndescription: \"Use when an org role acts as collective intelligence coordinator and must merge what several agents found into one reconciled, retrievable knowledge store. Read before write, origin tags for rollback, and recording unresolved contradictions.\"\ntags: [\"operations\",\"coordination\",\"agents\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Collective Intelligence Coordinator — Best Practices\n\n## Focus\nTurns what several agents each found separately into one coherent, retrievable body of knowledge — the shared store other agents and later sessions actually read from.\n\n## Best practices\n- Read before writing: check existing entities\u002Fvocabulary before minting new ones. Reusing an existing name is worth more than a precise-but-duplicate new one.\n- Reconcile, don't concatenate — two agents reporting on the same subject should produce one entry, not two. Where they agree, merge; where they conflict, go back to the evidence each cited and decide.\n- Persist only durable insight — entities, relationships, and rules that will still be true next month. Session narration, task status, and one-off observations don't belong in shared long-term knowledge.\n- Tag every write with its origin (session\u002Ftask id) so a bad ingest can be traced and undone without touching everything else.\n- Close the loop: when retrieved knowledge materially helped a task, record that feedback so future retrieval ranks it appropriately.\n- If a contradiction can't be resolved from available evidence, record the disagreement *as* the finding, with both positions stated — a hidden contradiction is worse than an open one.\n\n## Common pitfalls\n- Treating multiple agents as having a live shared mind — they don't; the only real substrate is persistent storage others can later read, and quality depends entirely on how well it's curated.\n- Writing near-duplicate entities under slightly different names, which fragments retrieval and makes the store progressively less useful.\n- Fabricating confidence scores or \"consensus levels\" that nothing actually computed — report what was actually reconciled, not an invented metric.\n- Skipping the read-before-write step and letting the store accumulate contradictory claims that no one ever reconciles.\n- Persisting transient status (\"agent X finished step 3\") into durable knowledge, cluttering the store with things nobody will need to retrieve later.\n\n## Tools & techniques\n- Search the existing knowledge store and its entity vocabulary before every ingest — that's the whole defense against duplication.\n- Use an explicit rollback path keyed to the origin tag so any bad batch can be cleanly undone.\n- Batch and structure writes (entities\u002Frelationships\u002Frules) rather than dumping raw agent output verbatim.\n- Periodically consolidate\u002Fcondense accumulated material so the store stays retrievable instead of growing without bound.\n","# Collective Intelligence Coordinator — Best Practices\n\n## Focus\nTurns what several agents each found separately into one coherent, retrievable body of knowledge — the shared store other agents and later sessions actually read from.\n\n## Best practices\n- Read before writing: check existing entities\u002Fvocabulary before minting new ones. Reusing an existing name is worth more than a precise-but-duplicate new one.\n- Reconcile, don't concatenate — two agents reporting on the same subject should produce one entry, not two. Where they agree, merge; where they conflict, go back to the evidence each cited and decide.\n- Persist only durable insight — entities, relationships, and rules that will still be true next month. Session narration, task status, and one-off observations don't belong in shared long-term knowledge.\n- Tag every write with its origin (session\u002Ftask id) so a bad ingest can be traced and undone without touching everything else.\n- Close the loop: when retrieved knowledge materially helped a task, record that feedback so future retrieval ranks it appropriately.\n- If a contradiction can't be resolved from available evidence, record the disagreement *as* the finding, with both positions stated — a hidden contradiction is worse than an open one.\n\n## Common pitfalls\n- Treating multiple agents as having a live shared mind — they don't; the only real substrate is persistent storage others can later read, and quality depends entirely on how well it's curated.\n- Writing near-duplicate entities under slightly different names, which fragments retrieval and makes the store progressively less useful.\n- Fabricating confidence scores or \"consensus levels\" that nothing actually computed — report what was actually reconciled, not an invented metric.\n- Skipping the read-before-write step and letting the store accumulate contradictory claims that no one ever reconciles.\n- Persisting transient status (\"agent X finished step 3\") into durable knowledge, cluttering the store with things nobody will need to retrieve later.\n\n## Tools & techniques\n- Search the existing knowledge store and its entity vocabulary before every ingest — that's the whole defense against duplication.\n- Use an explicit rollback path keyed to the origin tag so any bad batch can be cleanly undone.\n- Batch and structure writes (entities\u002Frelationships\u002Frules) rather than dumping raw agent output verbatim.\n- Periodically consolidate\u002Fcondense accumulated material so the store stays retrievable instead of growing without bound.\n",{"name":5,"tags":43,"tools":45,"source":46,"license":14,"description":7},[24,28,44],"agents",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcollective-coord",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add monoes\u002Fmonomind --skill collective-coord",{"tool":61,"command":62},"bunx","bunx skills add monoes\u002Fmonomind --skill collective-coord",{"tool":64,"command":65},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill collective-coord","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcollective-coord\u002FSKILL.md",true,[],[70,96,132,158,180,207],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":95},"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",[],[77,78,79,80,81,82,83,34,84,85,86,87,26,88,89,90,91,92,93,94],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":114,"publishedAt":95},"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",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[115,116,117,81,118,119,31,120,85,121,122,123,124,125,126,127,128,129,130,131],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":95},"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",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000031","产品经理",[125,143,144,145,146,34,147,31,148,149,150,124,151,152,153,154,155,156,32,157],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":95},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000033","数据分析师",[85,125,169,170,35,171,34,32,31,172,173,174,175,150,25,176,20,177,178,179],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":192,"publishedAt":95},"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",[186,189],{"categoryNo":187,"categoryName":188,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":190,"categoryName":191,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发",[193,194,195,196,35,197,198,199,200,84,201,202,203,85,26,25,204,205,206,20],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":95},"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",[213],{"categoryNo":190,"categoryName":191,"taxonomyType":107,"taxonomyTypeDesc":108},[195,215,216,217,218,219,220,35,221,222,121,223,224,225,26,25,226,24,20,227],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","systems"]