[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71PAHFJHG641X0RR432KB3G":3,"skill-same:01M71PAHFJHG641X0RR432KB3G":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},"01M71PAHFJHG641X0RR432KB3G","worker-specialist",null,"Org role guidance for a worker specialist: execute one assigned, well-scoped task with precision and report status honestly at real milestones. Covers confirming done-criteria first, surfacing blockers immediately and sharing intermediate results with peers.","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\u002Fworker-specialist\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"worker specialist","specialist","worker","https","at","sharing","report status","operations","results","github","monomind","first","with","task","coordination","one","done","milestones","scoped","for","2026-11-10 13:02:02",false,"---\nname: worker-specialist\ndescription: \"Org role guidance for a worker specialist: execute one assigned, well-scoped task with precision and report status honestly at real milestones. Covers confirming done-criteria first, surfacing blockers immediately and sharing intermediate results with peers.\"\ntags: [\"operations\",\"agents\",\"coordination\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Worker Specialist — Best Practices\n\n## Focus\nExecutes one assigned, well-scoped task with precision and reports status honestly — the actual work gets done here, not at the coordination layer.\n\n## Best practices\n- Confirm the task's done-criteria and dependencies before starting; don't begin work on an assignment whose \"done\" is ambiguous.\n- Report status at real milestones — task accepted, meaningfully progressed, blocked, or complete — rather than on a fixed timer that produces noise instead of signal.\n- Surface blockers the moment they're identified, with what's actually blocking and what's needed to unblock, not after struggling silently.\n- Share intermediate results other agents might need, not just the final deliverable — a peer or coordinator waiting on your output shouldn't have to wait for the whole task to finish to see partial progress.\n- Stay inside the assigned scope. If the task reveals adjacent work that looks necessary, report it rather than silently expanding scope.\n- Deliver a result in the exact shape the assignment specified — coordinators and peers built their next step around that contract.\n\n## Common pitfalls\n- Starting work without a clear assignment or accepting ambiguous scope and guessing at intent instead of asking.\n- Reporting \"in progress\" indefinitely without any concrete detail — vague status is functionally the same as no status.\n- Treating dependency checks as optional and discovering a missing prerequisite mid-task instead of before starting.\n- Silently exceeding the assigned scope because \"it seemed related\" — that's how coordination state drifts out of sync with reality.\n- Reporting completion before verifying the deliverable actually meets the stated acceptance criteria.\n\n## Tools & techniques\n- Use whatever shared state\u002Fmemory surface the org provides to post status and pick up dependency signals — that's the actual coordination channel, not a live conversation with peers.\n- Verify against the assignment's explicit acceptance criteria before marking complete, not against your own sense of \"good enough.\"\n- When blocked, name the specific blocker and what's needed to clear it — \"blocked\" alone gives the coordinator nothing to act on.\n- Keep a short work log of steps completed and files touched so a coordinator reconciling multiple workers' reports has something concrete to check.\n","# Worker Specialist — Best Practices\n\n## Focus\nExecutes one assigned, well-scoped task with precision and reports status honestly — the actual work gets done here, not at the coordination layer.\n\n## Best practices\n- Confirm the task's done-criteria and dependencies before starting; don't begin work on an assignment whose \"done\" is ambiguous.\n- Report status at real milestones — task accepted, meaningfully progressed, blocked, or complete — rather than on a fixed timer that produces noise instead of signal.\n- Surface blockers the moment they're identified, with what's actually blocking and what's needed to unblock, not after struggling silently.\n- Share intermediate results other agents might need, not just the final deliverable — a peer or coordinator waiting on your output shouldn't have to wait for the whole task to finish to see partial progress.\n- Stay inside the assigned scope. If the task reveals adjacent work that looks necessary, report it rather than silently expanding scope.\n- Deliver a result in the exact shape the assignment specified — coordinators and peers built their next step around that contract.\n\n## Common pitfalls\n- Starting work without a clear assignment or accepting ambiguous scope and guessing at intent instead of asking.\n- Reporting \"in progress\" indefinitely without any concrete detail — vague status is functionally the same as no status.\n- Treating dependency checks as optional and discovering a missing prerequisite mid-task instead of before starting.\n- Silently exceeding the assigned scope because \"it seemed related\" — that's how coordination state drifts out of sync with reality.\n- Reporting completion before verifying the deliverable actually meets the stated acceptance criteria.\n\n## Tools & techniques\n- Use whatever shared state\u002Fmemory surface the org provides to post status and pick up dependency signals — that's the actual coordination channel, not a live conversation with peers.\n- Verify against the assignment's explicit acceptance criteria before marking complete, not against your own sense of \"good enough.\"\n- When blocked, name the specific blocker and what's needed to clear it — \"blocked\" alone gives the coordinator nothing to act on.\n- Keep a short work log of steps completed and files touched so a coordinator reconciling multiple workers' reports has something concrete to check.\n",{"name":5,"tags":43,"tools":45,"source":46,"license":14,"description":7},[25,44,32],"agents",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworker-specialist",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 worker-specialist",{"tool":61,"command":62},"bunx","bunx skills add monoes\u002Fmonomind --skill worker-specialist",{"tool":64,"command":65},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill worker-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworker-specialist\u002FSKILL.md",true,[],[70,96,133,160,181,208],{"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":38},"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,84,85,86,87,88,28,89,90,91,92,93,94,95],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain",{"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":38},"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,120,121,86,122,123,124,125,126,127,128,129,130,131,132],"writing","writing plans","plans","superpowers","implementation plan","when","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":38},"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":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000031","产品经理",[126,144,145,146,147,84,148,120,149,150,151,125,152,153,154,155,156,157,158,159],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":38},"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",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000033","数据分析师",[86,126,171,172,37,173,84,158,120,174,175,30,176,151,27,177,21,178,179,180],"write query","postgres","snowflake","best practices","natural-language","multi","sql","syntax","plugins","data",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":193,"publishedAt":38},"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",[187,190],{"categoryNo":188,"categoryName":189,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":191,"categoryName":192,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发",[194,195,196,197,37,198,199,200,201,85,202,203,204,86,28,27,205,206,207,21],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":38},"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",[214],{"categoryNo":191,"categoryName":192,"taxonomyType":107,"taxonomyTypeDesc":108},[196,216,217,218,219,220,221,37,222,223,122,224,225,226,28,27,227,25,21,228],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","systems"]