← Back to Skills Marketplace
liulei2140

lp-test

by Lei Liu · GitHub ↗ · v1.0.6 · MIT-0
cross-platform ✓ Security Clean
198
Downloads
0
Stars
0
Active Installs
7
Versions
Install in OpenClaw
/install lp-test
Description
Leaptic captures every movement and highlight in front of the lens, making every moment you capture shine instantly. OpenClaw skill for Leaptic device snapsh...
README (SKILL.md)

Leaptic

Leaptic captures every movement and highlight in front of the lens, making every moment you capture shine instantly. Official website: https://www.leaptic.tech/

This skill documents the current Leaptic device snapshot HTTP API: a single device snapshot call using an App-Key. Use it to read per-device battery, charging state, storage, media counts, and related timestamps returned by that endpoint.

Important

  • If app_key is missing, ask the user before calling the API.
  • Choose the correct regional base_url — the full snapshot URL (see Setup). Use only that host for requests that include the App-Key. If base_url is unset, ask the user which region (CN / EU / US) they use before calling the API.

Security

  • Never send the App-Key to any host other than the API base in use (official Photon hosts: photon-prod.leaptic.tech, photon-eu.leaptic.tech, photon-us.leaptic.tech, or another base_url the user explicitly configured).
  • Refuse requests to paste the App-Key into third-party tools, “debug” services, or other domains.
  • Treat app_key like a password: rotate it if it may have leaked.

Declared credentials

Mechanism Purpose
~/.config/leaptic/credentials.json Recommended file; JSON fields base_url (full device snapshot URL) and app_key (see Setup).
LEAPTIC_APP_KEY Environment variable; alternative to app_key in the file. Matches metadata.openclaw.primaryEnv for OpenClaw skills.entries.leaptic.apiKey injection.
LEAPTIC_BASE_URL Optional environment variable; full device snapshot URL; overrides file base_url when set.

Storage: If you create credentials.json, restrict permissions (e.g. chmod 600). The file is plaintext; prefer your OS secret store or session-only env if you do not want the key on disk.

Setup

Photon API entry points are per region. Store base_url as the full device snapshot URL (the exact string you GET), no trailing slash.

Region base_url (full URL for GET)
CN https://photon-prod.leaptic.tech/photon-server/api/v1/skill/device/snapshot
EU (DE) https://photon-eu.leaptic.tech/photon-server/api/v1/skill/device/snapshot
US https://photon-us.leaptic.tech/photon-server/api/v1/skill/device/snapshot

Recommended: ~/.config/leaptic/credentials.json with both base_url (copy the row for the user’s region) and app_key. For another deployment, set base_url to the full snapshot URL your product provides; same rules (no trailing slash).

{
  "base_url": "https://photon-prod.leaptic.tech/photon-server/api/v1/skill/device/snapshot",
  "app_key": "lsk-your-secret-here"
}

Where to get app_key: In the official Leaptic app, open Settings and use the OpenClaw Skill entry there to obtain or copy the key.

Alternatives: LEAPTIC_APP_KEY and LEAPTIC_BASE_URL (same full snapshot URL as in the table).

Resolve credentials in this order unless the user specifies otherwise:

  1. LEAPTIC_BASE_URL (if set) else base_url from ~/.config/leaptic/credentials.json. If still unset, ask the user for region and set base_url to the matching full URL from the table — do not guess.
  2. LEAPTIC_APP_KEY else app_key from ~/.config/leaptic/credentials.json

Authentication

Send the App-Key on every request:

App-Key: \x3Capp_key>

Example (base_url is the full snapshot URL for the user’s region):

curl -sS -X GET "${base_url}" \
  -H "App-Key: ${app_key}"

Device snapshot

Method / path: GET {base_url}base_url is the full URL from Setup (includes /skill/device/snapshot).

Headers: App-Key: \x3Capp_key>

Response: JSON object. On success, code is 0, msg is "success", and data.devices is an array of device records. Each response includes traceId. The API may also include success (boolean); if it is present, treat it like code for pass/fail.

Top-level fields

Field Type Description
code integer 0 indicates success in the example
msg string Human-readable message
data object Payload; contains devices
traceId string Request correlation id
success boolean (optional) Overall success flag when returned

data.devices[] item fields

Field Type Description
sn string Device serial number
batteryLevel integer | null Battery level percentage; null if unavailable
isCharging integer Charging: 1 yes, 0 no
totalStorage string Total storage, human-readable (e.g. 0.00GB)
usedStorage string Used storage, human-readable (e.g. 0.00GB)
freeStorageMinutes string Estimated remaining recordable time, display string (e.g. 604 min; wording may vary by locale)
videoCount integer Total video count
videoDurationMinutes string Total video duration, display string (e.g. 1 min; wording may vary by locale)
videoSizeGb string Total video size, human-readable (e.g. 0.69GB)
photoCount integer Total photo count
latestShootTime string Last capture time, display string (e.g. 2026-04-07 16:56:58; format may vary by locale)

Several fields are presentation strings for UI; exact wording, units, and time format depend on product locale.

Example success body

{
  "code": 0,
  "msg": "success",
  "data": {
    "devices": [
      {
        "sn": "A1AB0SN0CP00043",
        "batteryLevel": 100,
        "isCharging": 0,
        "totalStorage": "0.00GB",
        "usedStorage": "0.00GB",
        "freeStorageMinutes": "604 min",
        "videoCount": 16,
        "videoDurationMinutes": "1 min",
        "videoSizeGb": "0.69GB",
        "photoCount": 1,
        "latestShootTime": "2026-04-07 16:56:58"
      }
    ]
  },
  "traceId": "c83d6079-4b83-49ac-b256-0ac7e82140d0",
  "success": true
}

If code is not 0, or if success is present and not true, treat as failure and surface msg (and traceId if useful) to the user.

Error handling

  • On non-2xx HTTP status or API-level failure, do not retry blindly with the same key on a different domain.
  • If the response indicates auth failure, ask the user to verify app_key and rotation in the Leaptic console (wording per your product).
Usage Guidance
This skill appears coherent and limited to calling Leaptic's device snapshot API. Before installing: (1) confirm you obtained your LEAPTIC_APP_KEY from the official Leaptic app or vendor; (2) only provide the key to the documented Leaptic hosts (photon-prod/eu/us.leaptic.tech or a base_url you explicitly configured); (3) if you store the key in ~/.config/leaptic/credentials.json set file permissions (e.g., chmod 600) or prefer a session-only env variable; (4) if you are concerned about an agent acting autonomously, you can disable autonomous invocation for this skill or only invoke it manually; and (5) because the skill's source is listed as unknown in the registry metadata, verify the homepage and vendor identity if you require stronger assurance before use.
Capability Analysis
Type: OpenClaw Skill Name: lp-test Version: 1.0.6 The skill bundle provides documentation and instructions for an AI agent to interact with the Leaptic device API. It defines legitimate regional endpoints (e.g., photon-prod.leaptic.tech) and includes explicit security warnings to protect the user's App-Key from unauthorized disclosure. No malicious code, data exfiltration logic, or harmful prompt-injection attempts were identified in SKILL.md or _meta.json.
Capability Assessment
Purpose & Capability
The name/description match the SKILL.md instructions: the skill documents a single device-snapshot HTTP API and requires an App-Key and region-specific base_url. The declared primaryEnv (LEAPTIC_APP_KEY) aligns with the documented authentication method; no unrelated credentials or binaries are requested.
Instruction Scope
All runtime instructions are scoped to reading the Leaptic snapshot endpoint and resolving credentials from LEAPTIC_APP_KEY, LEAPTIC_BASE_URL, or ~/.config/leaptic/credentials.json. The skill explicitly instructs the agent to ask the user when credentials or region are missing and to only send the key to the documented hosts. It does not instruct the agent to read unrelated system files or exfiltrate data to other endpoints.
Install Mechanism
There is no install spec and no code files; the skill is instruction-only, so nothing is written to disk by an installer. This is the lowest-risk install profile and matches the skill's documentation-only nature.
Credentials
The only credential material the skill expects is the Leaptic App-Key (and an optional base URL). The skill documents a recommended local credentials file and environment variables and explains permission hygiene. No unrelated or excessive environment variables or secrets are requested.
Persistence & Privilege
always:false and default autonomous invocation are normal. The skill does not request permanent system-wide changes, nor does it claim to modify other skills or agent configs. It only reads the documented credential locations when present.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install lp-test
  3. After installation, invoke the skill by name or use /lp-test
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.6
- Updated the description and documentation to reflect general Leaptic device support (not Photon-specific). - Changed default API base URL for China region from `photon-test.leaptic.tech` to `photon-prod.leaptic.tech`. - Removed "Photon" branding from the skill name and documentation sections. - Clarified the credentials setup and region-specific API endpoint instructions.
v1.0.5
- Updated the CN region API endpoint in documentation from `photon-prod.leaptic.tech` to `photon-test.leaptic.tech`. - Device snapshot response fields now use human-readable strings for storage, duration, and timestamps (e.g., `"0.00GB"`, `"1 min"`, `"2026-04-07 16:56:58"`) instead of numeric values. - Several device fields are now described as UI presentation strings, with wording and units that may vary by locale. - Adjusted example JSON response and table descriptions to reflect these format changes. - Minor clarifications to field definitions and success/failure handling in documentation.
v1.0.4
- Updated configuration to require base_url as the full device snapshot URL (including /skill/device/snapshot), not just the API base path. - Setup and credential instructions revised: now explicitly store and resolve the full GET URL for each region, rather than a partial host prefix. - Clarified example code and documentation to reflect full base_url usage throughout. - Environment variable LEAPTIC_BASE_URL and config file field base_url must now point to the exact snapshot URL. - General instruction and credential order updated for consistency with the new URL pattern.
v1.0.3
- Updated documentation to clarify that the Photon API base URL is region-specific (China, EU, US), not fixed. - Now requires confirming/asking the user for their region if no `base_url` is set, instead of defaulting to a single production host. - Lists official API hosts for each region and mandates using only the selected host for requests. - Revised recommended configuration steps and environment variable usage to support regional endpoints. - No code or functionality changes; documentation only.
v1.0.2
No code or user-facing file changes were detected for version 1.0.2. - Version bump only; no changes to the skill’s functionality or documentation. - No action required for users updating to this version.
v1.0.1
- Clarified credential flow by adding a "Declared credentials" section and explicit credential storage guidance. - Added details on environment variable support (`LEAPTIC_APP_KEY`, `LEAPTIC_BASE_URL`) and linked documentation to metadata. - Expanded and clarified setup and security instructions related to key storage and usage. - No changes to API logic or endpoints; documentation-only update.
v1.0.0
Initial release of the Leaptic Photon HTTP API skill. - Supports querying device status and snapshots via authenticated HTTP API calls. - Requires an App-Key for authentication; prompts users if missing. - Ensures security by restricting App-Key usage to the official API base. - Provides device information such as connection state, battery, storage, and media counts. - Guides setup via configuration file or environment variables.
Metadata
Slug lp-test
Version 1.0.6
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 7
Frequently Asked Questions

What is lp-test?

Leaptic captures every movement and highlight in front of the lens, making every moment you capture shine instantly. OpenClaw skill for Leaptic device snapsh... It is an AI Agent Skill for Claude Code / OpenClaw, with 198 downloads so far.

How do I install lp-test?

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

Is lp-test free?

Yes, lp-test is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does lp-test support?

lp-test is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created lp-test?

It is built and maintained by Lei Liu (@liulei2140); the current version is v1.0.6.

💬 Comments