Book Battery

Book battery services through Lokuli MCP. Use when user needs to find and book battery. Triggers on requests like "book a battery", "find battery near me", or any battery service request.

Security Scan

The skill's declared purpose (finding and booking battery services via Lokuli MCP) generally matches its instructions, but the SKILL.md is vague about authentication, user consent, and dynamic input—so it could send personal data to an external endpoint without clear safeguards.

Purpose & Capability

The skill claims to book battery services via Lokuli MCP and the SKILL.md includes an explicit Lokuli MCP endpoint and JSON-RPC tool calls (search, check_availability, create_booking), which is coherent. However sample payloads contain hard-coded values (zipCode: 90640, fixed dates, sample customer details) and there is no explanation why no API key or auth is required; these hard-coded examples suggest sloppy implementation and possible assumptions about context that are not justified by the description.

Instruction Scope

Instructions are instruction-only and confined to calling Lokuli's MCP endpoint via tools/call. They do not instruct reading local files or unrelated environment variables. Concern: the create_booking example includes full customer PII (name, email, phone) but the SKILL.md does not say when/how to prompt for confirmation, sanitize or minimize data, or whether bookings require user consent. The instructions also do not document required authentication/headers or error handling, leaving important runtime behavior unspecified.

Install Mechanism

There is no install spec and no code files; the skill is instruction-only, which minimizes filesystem risk. Nothing is downloaded or installed by the skill itself.

Credentials

The skill declares no required environment variables or credentials, which superficially reduces risk. But a booking API typically requires authentication; the absence of any declared auth or primary credential is suspicious (either the platform injects credentials implicitly or the SKILL.md omits necessary requirements). This mismatch should be clarified before trusting the skill with user data.

Persistence & Privilege

The skill does not request always:true or any special persistence. It makes no claims to modify other skills or system-wide settings.

What to consider before installing

What to consider before installing: - Origin & trust: The skill has no homepage and an unknown source; verify who published it and whether you trust lokuli.com. - Authentication: The SKILL.md omits any API key or auth details. Confirm whether the Lokuli MCP requires credentials and where those would come from (platform vs skill). Do not assume anonymous access. - Personal data: The create_booking example includes PII (name, email, phone). Ensure the agent will prompt for and obtain explicit user consent before sending personal info. Ask how data is transmitted (HTTPS, headers) and how long it is stored by Lokuli. - Behavior clarity: The instructions use hard-coded examples (zip code, dates). Verify that the skill will use the actual user-provided location, date, and contact info rather than silently reusing example values. - Testing: If you proceed, test in a safe environment with dummy data and observe network requests. Prefer installing only if the publisher is known or after obtaining documentation showing required auth and privacy practices. - When in doubt: Treat this as potentially capable of sending user data to an external service. If you cannot verify the endpoint or required credentials, avoid enabling the skill for real bookings.

uook uattery

Book battery services through Lokuli's MCP server.

MCP Endpoint

https://lokuli.com/mcp/sse

Transport: SSE | JSON-RPC 2.0 | POST requests

Tools

search

{
  "method": "tools/call",
  "params": {
    "name": "search",
    "arguments": {
      "query": "battery",
      "zipCode": "90640",
      "maxResults": 20
    }
  }
}

check_availability

{
  "method": "tools/call",
  "params": {
    "name": "check_availability",
    "arguments": {
      "providerId": "xxx",
      "serviceId": "yyy",
      "date": "2025-02-10"
    }
  }
}

create_booking

{
  "method": "tools/call",
  "params": {
    "name": "create_booking",
    "arguments": {
      "providerId": "xxx",
      "serviceId": "yyy",
      "timeSlot": "2025-02-10T14:00:00-08:00",
      "customerName": "John Doe",
      "customerEmail": "[e-mail]",
      "customerPhone": "[phone]"
    }
  }
}