Book Lawyer
v1.0.1Book lawyer services through Lokuli MCP. Use when user needs to find and book lawyer. Triggers on requests like "book a lawyer", "find lawyer near me", or any lawyer service request.
⭐ 1· 1.3k·0 current·0 all-time
byLokuli@edwardrodriguez703-design
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description match the instructions (calls to Lokuli MCP search/check_availability/create_booking). However, the skill declares no credentials or config while referencing an external MCP endpoint that in practice typically requires authentication — this gap reduces coherence.
Instruction Scope
SKILL.md shows concrete JSON-RPC payloads for searching and creating bookings (including customer name/email/phone). That is appropriate for booking functionality, but the doc does not describe how to obtain user consent, handle or store PII, or how to authenticate to the Lokuli endpoint. The presence of hard-coded example fields (zipCode, dates) may be only examples but could lead to misuse if not handled carefully.
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install risk. Nothing is downloaded or written to disk by an installer.
Credentials
The skill requests no environment variables or credentials despite instructing the agent to call an external MCP endpoint. Realistic integration usually needs an API key or auth token; absence of declared auth is either incomplete documentation or implies the platform must supply credentials implicitly — this mismatch is a red flag.
Persistence & Privilege
always is false and the skill is user-invocable with normal model invocation. It does not request elevated or persistent platform privileges.
What to consider before installing
This skill appears to implement booking calls to Lokuli's MCP endpoint, which aligns with its stated purpose, but there are important unknowns. Before installing: verify the Lokuli endpoint and the publisher (no homepage or trusted source listed); confirm how authentication is provided (the skill declares no API key or token but will need one to call an external service); understand how the skill will handle user PII (names, emails, phone numbers are part of the payloads shown)—ask for a privacy policy or data handling statement; and consider testing in a limited, revocable environment. If you cannot confirm the endpoint and authentication mechanism, treat the skill as untrusted and avoid sending real personal data through it.Like a lobster shell, security has layers — review code before you run it.
latestvk979n4ceaxgrw23b6qkhkx04ah80md8j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.