Legal

v1.0.0

Use for law firm and legal practice operations — case management, document drafting, client communication, billing, court deadlines, discovery workflows, com...

0· 65·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (legal practice operations: case management, drafting, deadlines, billing) matches the SKILL.md content. The guidance and workflows are appropriate for a law‑firm assistant and do not request unrelated capabilities or secrets.
Instruction Scope
The SKILL.md prescribes checking matters, deadlines, unbilled time, and client messages — which implies the agent needs access to the firm's case/billing/message data. That expectation is coherent for this purpose but the skill does not declare how those data sources are provided; operators must ensure proper, scoped connectors and human oversight before any automated actions.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing will be written to disk or automatically installed by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. This is proportionate to an instruction-only guidance skill; any needed access would be provided by connectors set up externally by the user.
Persistence & Privilege
always is false and the skill does not request persistent system-level presence or to modify other skills. Normal autonomous invocation is allowed (platform default) but the skill itself does not elevate privileges.
Assessment
This skill is internally consistent and reads like a playbook for legal operations, not a covert data exfiltration tool. Before enabling it: (1) ensure any connectors you grant it access to (case management, calendar, email, billing) are limited to necessary scopes and authorized by your firm; (2) require human review/approval for filings, sending client communications, or financial transactions — do not let the agent auto-file or auto-bill without oversight; (3) review templates and placeholders for sensitive client data and privilege concerns; and (4) confirm compliance with local rules and data‑protection policies. If you plan to integrate it with live systems, document which systems and what access it will have and perform an access review first.

Like a lobster shell, security has layers — review code before you run it.

latestvk978gspehdfdrbkjd1k9svsam984dh2a

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments