[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MVRB6X3DFR4B51YW5N6CZ":3,"skill-same:01M71MVRB6X3DFR4B51YW5N6CZ":67},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":44,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71MVRB6X3DFR4B51YW5N6CZ","defender",null,"Use when an org role acts as defender and must test the prosecution's case: evidence gap analysis, procedural defenses and alternative theories, within ethics.","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\u002Fdefender\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"test","legal","ethics","org","role","https","audit","procedural","github","monomind","gap","case","analysis","gap analysis","when","use","strategy","evidence","as","2026-11-10 10:56:23",false,"---\nname: defender\ndescription: \"Use when an org role acts as defender and must test the prosecution's case: evidence gap analysis, procedural defenses and alternative theories, within ethics.\"\ntags: [\"legal\",\"strategy\",\"audit\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Defender — Best Practices\n\n## Focus\nProvides zealous advocacy for the opposing party within ethical bounds — the defender's job is to test the prosecution's case rigorously and ensure every weakness, gap, and alternative explanation is surfaced, not to assume the accusation is true.\n\n## Best practices\n- Never accept the opposing narrative at face value — independently reconstruct the facts and look for what doesn't fit.\n- Attack the case at its weakest evidentiary links: chain of custody, witness credibility, procedural errors, and gaps between evidence and required elements.\n- Develop alternative explanations for the evidence, not just objections to it — juries and judges respond to competing stories, not just doubt.\n- Hold the other side strictly to its actual burden — do not let unproven assumptions get treated as established fact.\n- Prepare witnesses and evidence meticulously; credibility under cross-examination is often decisive.\n- Stay within ethical bounds: zealous advocacy never extends to presenting evidence known to be false or misleading the tribunal.\n- Build a coherent trial theme early and repeat it consistently — juries retain themes, not isolated objections.\n\n## Common pitfalls\n- Being reflexively obstructive rather than substantively rigorous — objecting without building a case.\n- Overlooking procedural defenses (standing, admissibility, timeliness) in favor of only merits-based arguments.\n- Failing to prepare an affirmative narrative and relying solely on poking holes in the opposing case.\n- Conflating \"zealous\" with \"aggressive\" — losing credibility with the decision-maker through overreach.\n\n## Tools & techniques\n- Evidence gap analysis: mirror the prosecution's element-by-element case and mark every element with weak, missing, or contested support.\n- Alternative-theory drafting: generate at least one plausible innocent\u002Fnon-liable explanation for each major piece of evidence.\n- Procedural checklist: verify chain of custody, disclosure timeliness, and admissibility before accepting evidence as usable.\n- Theme consistency check: ensure every argument and cross-examination point ties back to a single core defense theory.\n","# Defender — Best Practices\n\n## Focus\nProvides zealous advocacy for the opposing party within ethical bounds — the defender's job is to test the prosecution's case rigorously and ensure every weakness, gap, and alternative explanation is surfaced, not to assume the accusation is true.\n\n## Best practices\n- Never accept the opposing narrative at face value — independently reconstruct the facts and look for what doesn't fit.\n- Attack the case at its weakest evidentiary links: chain of custody, witness credibility, procedural errors, and gaps between evidence and required elements.\n- Develop alternative explanations for the evidence, not just objections to it — juries and judges respond to competing stories, not just doubt.\n- Hold the other side strictly to its actual burden — do not let unproven assumptions get treated as established fact.\n- Prepare witnesses and evidence meticulously; credibility under cross-examination is often decisive.\n- Stay within ethical bounds: zealous advocacy never extends to presenting evidence known to be false or misleading the tribunal.\n- Build a coherent trial theme early and repeat it consistently — juries retain themes, not isolated objections.\n\n## Common pitfalls\n- Being reflexively obstructive rather than substantively rigorous — objecting without building a case.\n- Overlooking procedural defenses (standing, admissibility, timeliness) in favor of only merits-based arguments.\n- Failing to prepare an affirmative narrative and relying solely on poking holes in the opposing case.\n- Conflating \"zealous\" with \"aggressive\" — losing credibility with the decision-maker through overreach.\n\n## Tools & techniques\n- Evidence gap analysis: mirror the prosecution's element-by-element case and mark every element with weak, missing, or contested support.\n- Alternative-theory drafting: generate at least one plausible innocent\u002Fnon-liable explanation for each major piece of evidence.\n- Procedural checklist: verify chain of custody, disclosure timeliness, and admissibility before accepting evidence as usable.\n- Theme consistency check: ensure every argument and cross-examination point ties back to a single core defense theory.\n",{"name":5,"tags":42,"tools":43,"source":44,"license":14,"description":7},[19,34,24],[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdefender",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add monoes\u002Fmonomind --skill defender",{"tool":59,"command":60},"bunx","bunx skills add monoes\u002Fmonomind --skill defender",{"tool":62,"command":63},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill defender","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdefender\u002FSKILL.md",true,[],[68,94,130,156,179,206],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":93},"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",[],[75,76,77,78,79,80,81,82,83,84,85,86,27,87,88,89,90,91,21,92],"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":112,"publishedAt":93},"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",[102,107],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[113,114,115,79,116,117,32,118,84,119,120,121,122,123,124,125,126,127,128,129],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":93},"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",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000031","产品经理",[123,141,142,143,144,82,145,32,146,147,148,122,149,150,151,152,153,154,33,155],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":93},"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",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000033","数据分析师",[84,123,167,168,169,170,82,33,32,171,172,173,174,148,26,175,23,176,177,178],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":191,"publishedAt":93},"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",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":189,"categoryName":190,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000023","Skill与智能体开发",[192,193,194,195,169,196,197,198,199,83,200,201,202,84,27,26,203,204,205,23],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":213,"publishedAt":93},"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",[212],{"categoryNo":189,"categoryName":190,"taxonomyType":105,"taxonomyTypeDesc":106},[194,214,215,216,217,218,219,169,220,221,119,222,223,224,27,26,225,226,23,227],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]