Token导航 LogoToken导航TokenDH.com
开发敏感数据clawhub未标认证来源可访问clear审计通过

lp-testLP 测试

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

5,715

周安装

243

GitHub Stars

公开资料未说明

下载量

2,002
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:lp-test(LP 测试)
来源仓库:https://github.com/liulei2140/lp-test
安装命令:
openclaw skills install lp-test
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install lp-test

简介

Leaptic设备快照的OpenClaw技能,捕捉动作亮点瞬间。

  • 适用于运动摄影、直播回放分析或设备性能测试辅助。
  • 支持关键帧标记与高光时刻导出功能。lp-test 属于开发类 Skill,可作为该场景下的辅助能力补充。
  • 需连接Leaptic硬件并授权数据访问权限。
  • 输出为本地文件,建议命名规范便于归档查找。

SKILL.md

name
leaptic
description
Leaptic captures every movement and highlight in front of the lens, making every moment you capture shine instantly. OpenClaw skill for Leaptic device snapshot and status access.
version
0.1.0
homepage
https://www.leaptic.tech/
metadata
{ "leaptic": { "category": "hardware" }, "openclaw": { "primaryEnv": "LEAPTIC_APP_KEY", "homepage": "https://www.leaptic.tech/" } }

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

MechanismPurpose
~/.config/leaptic/credentials.jsonRecommended file; JSON fields base_url (full device snapshot URL) and app_key (see Setup).
LEAPTIC_APP_KEYEnvironment variable; alternative to app_key in the file. Matches metadata.openclaw.primaryEnv for OpenClaw skills.entries.leaptic.apiKey injection.
LEAPTIC_BASE_URLOptional 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.

Regionbase_url (full URL for GET)
CNhttps://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
UShttps://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: <app_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: <app_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

FieldTypeDescription
codeinteger0 indicates success in the example
msgstringHuman-readable message
dataobjectPayload; contains devices
traceIdstringRequest correlation id
successboolean (optional)Overall success flag when returned

data.devices[] item fields

FieldTypeDescription
snstringDevice serial number
batteryLevelinteger \nullBattery level percentage; null if unavailable
isChargingintegerCharging: 1 yes, 0 no
totalStoragestringTotal storage, human-readable (e.g. 0.00GB)
usedStoragestringUsed storage, human-readable (e.g. 0.00GB)
freeStorageMinutesstringEstimated remaining recordable time, display string (e.g. 604 min; wording may vary by locale)
videoCountintegerTotal video count
videoDurationMinutesstringTotal video duration, display string (e.g. 1 min; wording may vary by locale)
videoSizeGbstringTotal video size, human-readable (e.g. 0.69GB)
photoCountintegerTotal photo count
latestShootTimestringLast 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).

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

78.36%
按下载量换算1,569

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills