litigation response
v1.0.0解析起诉状内容，提炼争议焦点，制定系统化应诉策略；当收到原告起诉状需要梳理诉讼思路、分析法律关系或制定答辩方向时使用
⭐ 0· 103·0 current·0 all-time
by小与@xuleff
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, SKILL.md and included templates/references all align: the skill parses complaints, extracts facts/claims/evidence, and produces a response strategy using the provided template files. No unrelated capabilities or credentials are requested.
Instruction Scope
Runtime instructions ask the agent to extract detailed case data, including PII (names, ID numbers, addresses, contact info) and to prepare evidence/strategy per local rules. Collecting such sensitive information is appropriate for litigation analysis, but it is privacy-sensitive — the SKILL.md does not instruct any external transmission (good), and it includes a reminder to keep case secrets and follow professional ethics.
Install Mechanism
No install spec and no code files beyond static templates/references. Instruction-only skills have low installation risk because nothing is written or downloaded.
Credentials
The skill does not request environment variables, credentials, or config paths. All required resources are local text files (templates and references) consistent with the stated purpose.
Persistence & Privilege
Flags show no forced always-on presence. The skill is user-invocable and does not request elevated privileges or modification of other skills/configuration.
Assessment
This skill is internally coherent for preparing litigation response documents, but it will lead the agent to process sensitive personal and case data. Before installing/use: (1) ensure you are authorized to handle the complaint and its PII (attorney-client privilege, data-protection rules); (2) avoid pasting complaints containing extra secrets (passwords, unrelated tokens); (3) do not allow the agent to transmit documents to external services unless you trust and control them; (4) review and validate all generated legal analysis and filings with a licensed attorney before filing or relying on them; (5) consider disabling autonomous invocation or limiting access if you will process many confidential files, and confirm the templates/references align with your jurisdiction's procedural rules.Like a lobster shell, security has layers — review code before you run it.
latestvk97cvx6z3wytxqvs43ggk6hrk5837rgd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.