case-analyst
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.
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- case-analyst
- tags
- [ "legal", "research", "audit" ]
- tools
- []
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- description
- 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.
03 SKILL.md 正文
Case Analyst — Best Practices
Focus
Performs 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.
Best practices
- 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.
- Ground analysis in primary authority first (statutes, controlling case law) and respect hierarchy — supreme/appellate authority outweighs lower-court or persuasive authority.
- Translate the fact pattern into targeted research terms before querying case law or statute databases; vague queries produce noisy results.
- 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.
- Maintain a clear evidentiary record: cite the specific source (statute section, case name/citation, document) for every factual or legal claim.
- Flag ambiguity and conflicting authority explicitly rather than silently picking one interpretation.
- Distinguish holdings from dicta, and binding precedent from persuasive precedent, when citing case law.
Common pitfalls
- Skipping straight to case-law search without first defining the legal question precisely.
- Treating a single favorable case as dispositive without checking for controlling or conflicting authority.
- Presenting analysis as more certain than the underlying law supports.
- Failing to note jurisdictional differences that change which authority applies.
Tools & techniques
- Issue-spotting checklist: enumerate every claim/element and map available facts and authority against each.
- Citation hierarchy pass: rank sources by binding vs. persuasive weight before drawing conclusions.
- Fact-to-law matrix: a simple table linking each key fact to the legal standard it satisfies or undermines.
- Gap/risk log: a running list of unresolved factual disputes, weak evidentiary links, and unsettled legal questions.
04 同仓库更多 Skills
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.
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.
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.
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.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
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.