Book Detailing
v1.0.1Book detailing services through Lokuli MCP. Use when user needs to find and book detailing. Triggers on requests like "book a detailing", "find detailing near me", or any detailing service request.
⭐ 0· 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
Benign
high confidencePurpose & Capability
Name and description match the instructions: the SKILL.md shows JSON-RPC calls (search, check_availability, create_booking) against Lokuli's MCP endpoint. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
Instructions are narrowly scoped to calling the MCP endpoint via JSON-RPC and do not ask the agent to read local files or unrelated environment variables. The SKILL.md uses example customer data and a sample zip code but does not specify how real customer contact/payment/auth data should be provided or obtained—this is a clarity gap rather than an integrity issue.
Install Mechanism
No install spec or code is provided (instruction-only). This minimizes risk from arbitrary downloads or disk writes.
Credentials
The skill declares no required environment variables or credentials. That is coherent for an instruction-only skill, but in practice Lokuli's MCP may require authentication or API keys; the SKILL.md does not document any credential flow, which is a minor omission to verify before use.
Persistence & Privilege
Flags are default (always: false, user-invocable, agent invocation allowed). The skill does not request persistent presence or system-wide configuration changes.
Assessment
This skill appears coherent and limited to calling Lokuli's MCP API, but before installing: (1) verify the lokuli.com endpoint is legitimate for your environment and that you trust that service; (2) confirm how authentication is handled (the skill does not declare any API keys or tokens); (3) understand what customer data (name, email, phone, payment info) will be transmitted and ensure you consent before the agent sends it; (4) ask whether payments are handled through the platform or require entering card details elsewhere; and (5) test with dummy data first to confirm behavior. If any of these are unclear, ask the skill author for details or decline until authentication/privacy flows are documented.Like a lobster shell, security has layers — review code before you run it.
latestvk9786mzjkyahrktc2htmvznr6h80nd8d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.