[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MF6DRBXGDV9B8P6E47Z7B":3,"skill-same:01M71MF6DRBXGDV9B8P6E47Z7B":79},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":56,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M71MF6DRBXGDV9B8P6E47Z7B","case-analyst",null,"Use when an org role acts as case analyst and must neutrally evaluate a legal matter: facts, applicable law, precedent hierarchy and risks on both sides. Research with cited sources, flagging ambiguity rather than advocating.","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\u002Fcase-analyst\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"case","analyst","case analyst","ambiguity","org","role","https","audit","evaluate","precedent","github","monomind","research","hierarchy","with","facts","when","use","as","sources","2026-11-10 10:56:23",false,"---\nname: case-analyst\ndescription: \"Use when an org role acts as case analyst and must neutrally evaluate a legal matter: facts, applicable law, precedent hierarchy and risks on both sides. Research with cited sources, flagging ambiguity rather than advocating.\"\ntags: [\"legal\",\"research\",\"audit\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Case Analyst — Best Practices\n\n## Focus\nPerforms neutral, systematic case evaluation and legal research — gathers facts, maps applicable law, identifies precedent, and surfaces risks and weaknesses for whichever party or process consumes the analysis.\n\n## Best practices\n- Start every analysis with a clear plan: gather facts, isolate the core legal questions, then research — don't research before you know what question you're answering.\n- Ground analysis in primary authority first (statutes, controlling case law) and respect hierarchy — supreme\u002Fappellate authority outweighs lower-court or persuasive authority.\n- Translate the fact pattern into targeted research terms before querying case law or statute databases; vague queries produce noisy results.\n- Identify risks and weaknesses on both sides of the matter, not just the side that benefits the requester — a one-sided analysis misleads downstream decisions.\n- Maintain a clear evidentiary record: cite the specific source (statute section, case name\u002Fcitation, document) for every factual or legal claim.\n- Flag ambiguity and conflicting authority explicitly rather than silently picking one interpretation.\n- Distinguish holdings from dicta, and binding precedent from persuasive precedent, when citing case law.\n\n## Common pitfalls\n- Skipping straight to case-law search without first defining the legal question precisely.\n- Treating a single favorable case as dispositive without checking for controlling or conflicting authority.\n- Presenting analysis as more certain than the underlying law supports.\n- Failing to note jurisdictional differences that change which authority applies.\n\n## Tools & techniques\n- Issue-spotting checklist: enumerate every claim\u002Felement and map available facts and authority against each.\n- Citation hierarchy pass: rank sources by binding vs. persuasive weight before drawing conclusions.\n- Fact-to-law matrix: a simple table linking each key fact to the legal standard it satisfies or undermines.\n- Gap\u002Frisk log: a running list of unresolved factual disputes, weak evidentiary links, and unsettled legal questions.\n","# Case Analyst — Best Practices\n\n## Focus\nPerforms neutral, systematic case evaluation and legal research — gathers facts, maps applicable law, identifies precedent, and surfaces risks and weaknesses for whichever party or process consumes the analysis.\n\n## Best practices\n- Start every analysis with a clear plan: gather facts, isolate the core legal questions, then research — don't research before you know what question you're answering.\n- Ground analysis in primary authority first (statutes, controlling case law) and respect hierarchy — supreme\u002Fappellate authority outweighs lower-court or persuasive authority.\n- Translate the fact pattern into targeted research terms before querying case law or statute databases; vague queries produce noisy results.\n- Identify risks and weaknesses on both sides of the matter, not just the side that benefits the requester — a one-sided analysis misleads downstream decisions.\n- Maintain a clear evidentiary record: cite the specific source (statute section, case name\u002Fcitation, document) for every factual or legal claim.\n- Flag ambiguity and conflicting authority explicitly rather than silently picking one interpretation.\n- Distinguish holdings from dicta, and binding precedent from persuasive precedent, when citing case law.\n\n## Common pitfalls\n- Skipping straight to case-law search without first defining the legal question precisely.\n- Treating a single favorable case as dispositive without checking for controlling or conflicting authority.\n- Presenting analysis as more certain than the underlying law supports.\n- Failing to note jurisdictional differences that change which authority applies.\n\n## Tools & techniques\n- Issue-spotting checklist: enumerate every claim\u002Felement and map available facts and authority against each.\n- Citation hierarchy pass: rank sources by binding vs. persuasive weight before drawing conclusions.\n- Fact-to-law matrix: a simple table linking each key fact to the legal standard it satisfies or undermines.\n- Gap\u002Frisk log: a running list of unresolved factual disputes, weak evidentiary links, and unsettled legal questions.\n",{"name":5,"tags":53,"tools":55,"source":56,"license":14,"description":7},[54,40,35],"legal",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcase-analyst",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add monoes\u002Fmonomind --skill case-analyst",{"tool":71,"command":72},"bunx","bunx skills add monoes\u002Fmonomind --skill case-analyst",{"tool":74,"command":75},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill case-analyst","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcase-analyst\u002FSKILL.md",true,[],[80,106,138,164,186,213],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":105},"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",[],[87,88,89,90,91,92,93,94,95,96,97,98,39,99,100,101,102,103,32,104],"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":110,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":120,"publishedAt":105},"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",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":118,"categoryName":119,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",[121,122,123,91,124,125,44,126,96,127,128,129,130,131,132,133,134,135,136,137],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":148,"publishedAt":105},"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",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000031","产品经理",[131,149,150,151,152,94,153,44,154,155,156,130,157,158,159,160,161,162,45,163],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":105},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000033","数据分析师",[96,131,175,176,177,178,94,45,44,179,180,42,181,156,38,182,34,183,184,185],"write query","postgres","for","snowflake","best practices","natural-language","multi","sql","syntax","plugins","data",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":198,"publishedAt":105},"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",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":196,"categoryName":197,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[199,200,201,202,177,203,204,205,206,95,207,208,209,96,39,38,210,211,212,34],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":220,"publishedAt":105},"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",[219],{"categoryNo":196,"categoryName":197,"taxonomyType":20,"taxonomyTypeDesc":21},[201,221,222,223,224,225,226,177,227,228,127,229,230,231,39,38,232,233,34,234],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]