Description

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

README (SKILL.md)

uook inspection

Name: Book Inspection
Author: edwardrodriguez703-design

Book inspection 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": "inspection",
      "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": "[email protected]",
      "customerPhone": "+13105551234"
    }
  }
}

Usage Guidance

This skill appears to do what it says (search/check/create bookings), but ask the provider or skill author two things before installing: (1) Does the Lokuli MCP endpoint require an API key or other auth, and if so where is it stored/declared? (2) How is user personal data (name, email, phone) handled, logged, or retained by lokuli.com? Also confirm the transport/protocol details (the SKILL.md's 'SSE + POST' claim is inconsistent). If you cannot verify the endpoint and data-handling practices, avoid sending real PII and consider testing with dummy data or asking for a trustworthy implementation.

Capability Analysis

Type: OpenClaw Skill Name: book-inspection Version: 1.0.1 The skill defines tools for searching, checking availability, and creating bookings for inspection services via the `https://lokuli.com/mcp/sse` endpoint. While it involves network calls and handling of customer PII (name, email, phone), these actions are explicitly aligned with the stated purpose of 'Book inspection services through Lokuli MCP' as described in `SKILL.md`. There is no evidence of unauthorized data exfiltration, malicious execution, persistence, obfuscation, or prompt injection attempts against the agent.

Capability Assessment

ℹ Purpose & Capability

The name/description align with the SKILL.md: it calls a Lokuli MCP endpoint to search, check availability, and create bookings. However, the SKILL.md lists 'SSE | JSON-RPC 2.0 | POST requests' which is technically inconsistent (SSE typically uses HTTP GET/text/event-stream, while JSON-RPC over POST is common); this discrepancy should be clarified. Also the document provides example arguments but does not document any authentication requirements even though a public booking API often requires credentials.

⚠ Instruction Scope

The runtime instructions show JSON-RPC payloads that include personal customer fields (name, email, phone) and will send them to https://lokuli.com/mcp/sse. That is coherent with booking functionality, but the skill does not specify where user PII comes from, how consent/logging is handled, or whether the endpoint requires or uses authentication. The instructions do not reference reading local files or unrelated system state (good), but they do instruct transmission of personal data to an external domain without describing privacy controls.

✓ Install Mechanism

Instruction-only skill with no install spec and no code files. This minimizes disk writes and third-party installs — low install risk.

ℹ Credentials

The skill declares no required environment variables or credentials, which is consistent with the metadata. However, most external booking APIs require some form of authentication or API key; absence of any declared credential is plausible if the platform mediates auth, but it is unexpected and should be confirmed before use.

✓ Persistence & Privilege

always is false and the skill is user-invocable with normal autonomous invocation permitted. Nothing requests permanent presence or elevated agent-wide privileges.

Version History

v1.0.1

Fixed display name

v1.0.0

Initial release

Metadata

Slug book-inspection

Version 1.0.1

License —

All-time Installs 0

Active Installs 0

Total Versions 2

Frequently Asked Questions

What is Book Inspection?

Book inspection services through Lokuli MCP. Use when user needs to find and book inspection. Triggers on requests like "book a inspection", "find inspection near me", or any inspection service request. It is an AI Agent Skill for Claude Code / OpenClaw, with 1388 downloads so far.

How do I install Book Inspection?

Run "/install book-inspection" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Book Inspection free?

Yes, Book Inspection is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Book Inspection support?

Book Inspection is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Book Inspection?

It is built and maintained by Lokuli (@edwardrodriguez703-design); the current version is v1.0.1.

More Skills

Book Inspection