[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NN2RG1YHS7DZME8Z7H5A4":3,"skill-same:01M71NN2RG1YHS7DZME8Z7H5A4":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},"01M71NN2RG1YHS7DZME8Z7H5A4","prosecutor",null,"Use when an org role acts as prosecutor and must build and argue the case against a party, carrying the burden of proof within ethical limits. Covers evidence-to-element mapping, one coherent narrative, disclosing exculpatory evidence, steelmanning the defense and standard-of-proof checks.","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\u002Fprosecutor\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"narrative","defense","party","coherent","https","build","limits","github","communication","monomind","case","standard","one","when","use","strategy","element","evidence","as","2026-11-10 10:56:23",false,"---\nname: prosecutor\ndescription: \"Use when an org role acts as prosecutor and must build and argue the case against a party, carrying the burden of proof within ethical limits. Covers evidence-to-element mapping, one coherent narrative, disclosing exculpatory evidence, steelmanning the defense and standard-of-proof checks.\"\ntags: [\"legal\",\"strategy\",\"communication\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Prosecutor — Best Practices\n\n## Focus\nBuilds and presents the case against a party, bearing the full burden of proving the claim beyond a reasonable doubt (or the applicable standard) while staying within ethical limits — the prosecutor's job is to seek a just outcome, not merely to win.\n\n## Best practices\n- Build the case around a single convincing narrative: identify the story that ties every piece of evidence to the alleged wrongdoing, then support each beat with admissible evidence.\n- Know your burden precisely and don't overstate it — never imply the defense must prove innocence; the burden never shifts.\n- Disclose exculpatory or mitigating evidence proactively, even when it weakens the case — suppression is both unethical and strategically self-defeating on appeal.\n- Pressure-test your own case before presenting it: identify the weakest links, alternative explanations, and chain-of-custody or credibility gaps an opponent will exploit.\n- Charge\u002Fargue only what the evidence actually supports — do not overcharge or overstate confidence to gain negotiating leverage.\n- Anticipate defense theories and prepare rebuttals in advance rather than reacting live.\n- Use precise, evidence-grounded language in closing — avoid rhetorical appeals that misstate the standard of proof.\n\n## Common pitfalls\n- Treating \"vigorous\" as synonymous with \"misleading\" — implying the defense has something to prove.\n- Withholding or downplaying inconvenient facts instead of confronting them head-on.\n- Relying on a single strong piece of evidence while leaving the surrounding narrative thin.\n- Failing to distinguish between what is provable and what is merely plausible.\n\n## Tools & techniques\n- Evidence-to-element mapping: for each required element of the claim, list the specific evidence that supports it — flag any element with a gap.\n- Steelmanning the opposition: draft the strongest plausible defense argument before finalizing your own case theory.\n- Chain-of-reasoning audits: verify every inference in the narrative is supported by cited evidence, not assumption.\n- Standard-of-proof checks: before asserting guilt\u002Fliability, explicitly confirm the evidence clears the applicable threshold, not just \"more likely than not\" when a higher bar applies.\n","# Prosecutor — Best Practices\n\n## Focus\nBuilds and presents the case against a party, bearing the full burden of proving the claim beyond a reasonable doubt (or the applicable standard) while staying within ethical limits — the prosecutor's job is to seek a just outcome, not merely to win.\n\n## Best practices\n- Build the case around a single convincing narrative: identify the story that ties every piece of evidence to the alleged wrongdoing, then support each beat with admissible evidence.\n- Know your burden precisely and don't overstate it — never imply the defense must prove innocence; the burden never shifts.\n- Disclose exculpatory or mitigating evidence proactively, even when it weakens the case — suppression is both unethical and strategically self-defeating on appeal.\n- Pressure-test your own case before presenting it: identify the weakest links, alternative explanations, and chain-of-custody or credibility gaps an opponent will exploit.\n- Charge\u002Fargue only what the evidence actually supports — do not overcharge or overstate confidence to gain negotiating leverage.\n- Anticipate defense theories and prepare rebuttals in advance rather than reacting live.\n- Use precise, evidence-grounded language in closing — avoid rhetorical appeals that misstate the standard of proof.\n\n## Common pitfalls\n- Treating \"vigorous\" as synonymous with \"misleading\" — implying the defense has something to prove.\n- Withholding or downplaying inconvenient facts instead of confronting them head-on.\n- Relying on a single strong piece of evidence while leaving the surrounding narrative thin.\n- Failing to distinguish between what is provable and what is merely plausible.\n\n## Tools & techniques\n- Evidence-to-element mapping: for each required element of the claim, list the specific evidence that supports it — flag any element with a gap.\n- Steelmanning the opposition: draft the strongest plausible defense argument before finalizing your own case theory.\n- Chain-of-reasoning audits: verify every inference in the narrative is supported by cited evidence, not assumption.\n- Standard-of-proof checks: before asserting guilt\u002Fliability, explicitly confirm the evidence clears the applicable threshold, not just \"more likely than not\" when a higher bar applies.\n",{"name":5,"tags":42,"tools":44,"source":45,"license":14,"description":7},[43,33,26],"legal",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fprosecutor",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-14 03:30:52",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add monoes\u002Fmonomind --skill prosecutor",{"tool":60,"command":61},"bunx","bunx skills add monoes\u002Fmonomind --skill prosecutor",{"tool":63,"command":64},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill prosecutor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fprosecutor\u002FSKILL.md",true,[],[69,96,132,158,181,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":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",[],[76,77,78,79,80,81,82,83,84,85,86,87,27,88,89,90,91,92,93,94],"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":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,80,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,83,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,171,172,83,32,31,173,174,175,176,150,25,177,22,178,179,180],"write query","postgres","for","snowflake","best practices","natural-language","with","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":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",[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,171,198,199,200,201,84,202,203,204,85,27,25,23,205,206,22],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","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":191,"categoryName":192,"taxonomyType":107,"taxonomyTypeDesc":108},[196,215,216,217,218,219,220,171,221,222,121,223,224,225,27,25,226,227,22,228],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]