Book Appliance Repair

v1.0.1

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

0· 1.3k·0 current·0 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the runtime instructions: the SKILL.md defines search, check_availability, and create_booking RPC calls against Lokuli's MCP endpoint, which is coherent for a booking skill.
Instruction Scope
The instructions are narrowly scoped to the Lokuli MCP endpoint and three tool calls. They do include example/hard-coded parameters (zipCode 90640, example dates, placeholder provider/service ids, and example customer PII). The doc also mentions "Transport: SSE | JSON-RPC 2.0 | POST requests" (SSE vs POST is a minor protocol inconsistency). The instructions do not direct the agent to access local files or unrelated env vars, but they implicitly expect a tool/runtime that implements the tools/call mechanism to perform network operations.
Install Mechanism
Instruction-only skill with no install spec or code files; nothing will be written to disk or downloaded during install. This is the lowest-risk install model.
Credentials
The skill declares no required environment variables or credentials. In practice, booking APIs usually require authentication; the absence of any auth/token requirement is unexplained and likely means the agent's execution environment (the platform tools) must supply credentials. Confirm where and how authentication is handled before sending customer data.
Persistence & Privilege
Default flags (always: false, user-invocable, model-invocation enabled). The skill does not request persistent/system-wide privileges or modify other skill configs.
Assessment
This skill appears to do what it claims (search and create bookings via Lokuli's MCP), but verify a few things before enabling it: 1) Authentication — the SKILL.md does not specify any API key or token; confirm how the booking tool will authenticate and where credentials are stored. 2) Data handling — the examples include customer PII; ensure you consent to sending real names/emails/phone numbers and confirm Lokuli's privacy policy. 3) Endpoint trust — verify the domain (https://lokuli.com) is legitimate for your use case. 4) Protocol details — the doc mixes SSE and POST/JSON-RPC; ask the publisher for exact transport expectations. 5) Test with non-sensitive/demo data first to confirm behavior. If you cannot get answers about auth or endpoint provenance, treat the integration as risky for real bookings or PII.

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

latestvk9767vdcw0mk1p1k5b8cn9vrrn80maqc
1.3kdownloads
0stars
2versions
Updated 1mo ago
v1.0.1
MIT-0

uook appliance repair

Book appliance-repair 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": "appliance-repair",
      "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": "john@example.com",
      "customerPhone": "+13105551234"
    }
  }
}

Comments

Loading comments...