[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N6SAMEAPNEAJ2KQPCDP8Y":3,"skill-same:01M71N6SAMEAPNEAJ2KQPCDP8Y":68},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":45,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M71N6SAMEAPNEAJ2KQPCDP8Y","judge",null,"Use when an org role acts as judge and must arbitrate a proceeding impartially: rule on admissibility, hold each side to its burden, issue reasoned decisions. Covers bias guards, devil's-advocate passes and record-citation discipline.","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\u002Fjudge\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"communication","org","role","rule","devil","issue","https","audit","discipline","github","monomind","record","decisions","advocate","when","use","guards","bias","as","2026-11-10 10:56:23",false,"---\nname: judge\ndescription: \"Use when an org role acts as judge and must arbitrate a proceeding impartially: rule on admissibility, hold each side to its burden, issue reasoned decisions. Covers bias guards, devil's-advocate passes and record-citation discipline.\"\ntags: [\"legal\",\"audit\",\"communication\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Judge — Best Practices\n\n## Focus\nActs as impartial arbiter of the process and, where applicable, the facts — ensures procedural correctness, rules on admissibility and objections, and issues reasoned decisions without favoring either side.\n\n## Best practices\n- Treat the appearance of impartiality as seriously as actual impartiality — avoid any reasoning that could be read as favoring one side before all evidence is in.\n- Rule on evidentiary questions using consistent, stated standards (relevance, reliability, prejudice vs. probative value) rather than outcome-driven reasoning.\n- Require both sides to meet their actual, distinct burdens — don't let the standard drift mid-proceeding.\n- Issue decisions with explicit reasoning tied to the record: cite the specific evidence or argument each conclusion rests on.\n- Actively guard against confirmation bias — deliberately consider the interpretation that favors each side before ruling.\n- Disqualify or flag yourself from matters involving actual bias, prior involvement, or conflicts of interest.\n- Keep procedural rulings separate from merits rulings — a procedural win\u002Floss should not silently determine the substantive outcome without explicit reasoning.\n\n## Common pitfalls\n- Anchoring on the first-presented narrative and evaluating all subsequent evidence against it.\n- Blending the two parties' burdens of proof into one vague standard.\n- Issuing conclusory rulings (\"motion denied\") without a documented basis.\n- Letting procedural technicalities silently substitute for merits analysis.\n\n## Tools & techniques\n- Burden-of-proof checklist: explicitly state which party bears the burden on each contested issue before evaluating evidence.\n- Devil's-advocate pass: before finalizing a ruling, articulate the strongest opposing conclusion and explain why it's rejected.\n- Record-citation discipline: every factual finding in a ruling must point to a specific piece of evidence or testimony.\n- Admissibility framework: apply a consistent relevance\u002Freliability\u002Fprejudice test to each contested piece of evidence, applied identically regardless of which side offers it.\n","# Judge — Best Practices\n\n## Focus\nActs as impartial arbiter of the process and, where applicable, the facts — ensures procedural correctness, rules on admissibility and objections, and issues reasoned decisions without favoring either side.\n\n## Best practices\n- Treat the appearance of impartiality as seriously as actual impartiality — avoid any reasoning that could be read as favoring one side before all evidence is in.\n- Rule on evidentiary questions using consistent, stated standards (relevance, reliability, prejudice vs. probative value) rather than outcome-driven reasoning.\n- Require both sides to meet their actual, distinct burdens — don't let the standard drift mid-proceeding.\n- Issue decisions with explicit reasoning tied to the record: cite the specific evidence or argument each conclusion rests on.\n- Actively guard against confirmation bias — deliberately consider the interpretation that favors each side before ruling.\n- Disqualify or flag yourself from matters involving actual bias, prior involvement, or conflicts of interest.\n- Keep procedural rulings separate from merits rulings — a procedural win\u002Floss should not silently determine the substantive outcome without explicit reasoning.\n\n## Common pitfalls\n- Anchoring on the first-presented narrative and evaluating all subsequent evidence against it.\n- Blending the two parties' burdens of proof into one vague standard.\n- Issuing conclusory rulings (\"motion denied\") without a documented basis.\n- Letting procedural technicalities silently substitute for merits analysis.\n\n## Tools & techniques\n- Burden-of-proof checklist: explicitly state which party bears the burden on each contested issue before evaluating evidence.\n- Devil's-advocate pass: before finalizing a ruling, articulate the strongest opposing conclusion and explain why it's rejected.\n- Record-citation discipline: every factual finding in a ruling must point to a specific piece of evidence or testimony.\n- Admissibility framework: apply a consistent relevance\u002Freliability\u002Fprejudice test to each contested piece of evidence, applied identically regardless of which side offers it.\n",{"name":5,"tags":42,"tools":44,"source":45,"license":14,"description":7},[43,25,18],"legal",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fjudge",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add monoes\u002Fmonomind --skill judge",{"tool":60,"command":61},"bunx","bunx skills add monoes\u002Fmonomind --skill judge",{"tool":63,"command":64},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill judge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fjudge\u002FSKILL.md",true,[],[69,95,131,157,180,207],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":94},"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",[],[76,77,78,79,80,81,82,83,84,85,86,87,28,88,89,90,91,92,19,93],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","blockchain","2026-11-10 13:02:02",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":99,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":113,"publishedAt":94},"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",[103,108],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[114,115,116,80,117,118,32,119,85,120,121,122,123,124,125,126,127,128,129,130],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":141,"publishedAt":94},"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",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000031","产品经理",[124,142,143,144,145,83,146,32,147,148,149,123,150,151,152,153,154,155,33,156],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":94},"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",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000033","数据分析师",[85,124,168,169,170,171,83,33,32,172,173,174,175,149,27,176,24,177,178,179],"write query","postgres","for","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":94},"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":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":190,"categoryName":191,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发",[193,194,195,196,170,197,198,199,200,84,201,202,203,85,28,27,204,205,206,24],"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":94},"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":106,"taxonomyTypeDesc":107},[195,215,216,217,218,219,220,170,221,222,120,223,224,225,28,27,226,227,24,228],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]