Luckee Skill

Install and operate the luckee-tool OpenClaw plugin for querying Lingxing data. Use when the user mentions luckee, Lingxing, ASIN lookup, product data querie...

Security Scan

Instructions and requirements are internally consistent with a plugin that integrates the Luckee CLI and Lingxing data via OpenClaw; the skill fetches a GitHub-hosted plugin and (optionally) auto-installs a PyPI CLI, so users should verify those external packages/repos before proceeding.

Purpose & Capability

Name/description (Luckee/Lingxing ASIN queries) matches the actions the skill instructs: registering an OpenClaw plugin, using the luckee CLI, and managing tokens. No unrelated credentials or binaries are requested.

Instruction Scope

Runtime instructions are scoped to installing the plugin via `openclaw plugins install`, running the `luckee` CLI login, and configuring tokens in OpenClaw. The skill tells the agent to fetch/install software from GitHub and (if needed) run the luckee CLI or pip to install luckee-cli. It also reads/writes plugin configuration and a token store under the user's OpenClaw home config — expected for this purpose but worth noting because tokens are persisted locally.

Install Mechanism

No built-in install spec (instruction-only). The install flow delegates to OpenClaw to pull a GitHub repo and may auto-install `luckee-cli` via pip using a constrained version range. Fetching code from GitHub and PyPI is expected here but carries the usual risk of executing upstream code; the instructions correctly tell the agent to use OpenClaw's installer rather than doing manual git/npm steps.

Credentials

The skill declares no required env vars and doesn't demand unrelated credentials. It will persist tokens in the OpenClaw token store and can use existing OpenClaw channel credentials (e.g., Feishu appId/appSecret) if those are already configured — this is optional and explained in the docs. Users should be aware that existing channel credentials in OpenClaw may be used for optional features (native Feishu card updates).

Persistence & Privilege

The skill is not marked always:true, does not request elevated system-wide privileges, and persists only its plugin config and token file under the user's OpenClaw config (~/.openclaw). This is proportionate for a plugin that needs stored tokens and config.

Assessment

This skill appears to do what it says: register a Luckee OpenClaw plugin, use the luckee CLI, and store tokens in OpenClaw. Before installing, verify the upstream sources: check the GitHub repository (https://github.com/motse-ai/luckee-openclaw-plugin) and inspect the PyPI package `luckee-cli` (version range referenced) so you know what code will run on your machine. Understand that the plugin may auto-install the CLI via pip if not present, and that tokens you set will be persisted under ~/.openclaw (token file described). The plugin can optionally use existing OpenClaw channel credentials (e.g., Feishu) if those are already configured; it does not request those credentials itself but will use them for optional features. If you need higher assurance, review the plugin code on the GitHub repo before proceeding or install the CLI manually and set config.binaryPath to a vetted binary.

Pre-flight

Before doing anything, check whether the plugin is already installed:

openclaw plugins list

If luckee-tool appears and shows as enabled, skip straight to Usage. Otherwise, follow Install below.

Install

Before installing, ask the user for confirmation: explain that the plugin will be fetched from its GitHub repository and registered with OpenClaw.

1. Register the plugin with OpenClaw

openclaw plugins install https://github.com/motse-ai/luckee-openclaw-plugin

This single command fetches the plugin and installs its dependencies. Do not run git clone or npm install manually.

2. Authenticate with Luckee

Run:

luckee login

This command opens a browser auth page. Ask the user to complete authorization in the web page, then continue in terminal once login finishes. Running regular luckee commands also checks login status and will prompt the same web authorization flow if the user is not logged in.

3. Restart and verify

openclaw gateway restart
openclaw plugins info luckee-tool
openclaw health

Confirm the plugin shows as loaded and the gateway is healthy. Do not ask the user for API URL, User ID, or Lingxing account details.

Usage

Chat command

/luckee <query>

Example: /luckee 查一下 asin B0DPJMTH4N 的信息 用skills

Set a token

/luckee token <token>

Set a token and run a query in one go:

/luckee token sk_xxx 查一下 asin B0DPJMTH4N 的信息

AI tool invocation

Call the luckee_query tool with:

{
  "query": "查一下 asin B0DPJMTH4N 的信息 用skills",
  "token": "sk_optional_override",
  "language": "CN",
  "timeout": 90
}

Only query is required. Auth context is handled by CLI/session state (via luckee login or the auto-login prompt when running luckee commands).

Token Management

• Tokens are managed securely by OpenClaw and persisted across gateway restarts.
• Set a per-user token via /luckee token <token> (overrides the default for that sender).
• Set a default token via config: openclaw config set plugins.entries.luckee-tool.config.defaultToken "<token>".
• See reference.md for advanced token store details.

Troubleshooting

Binary not found

The plugin auto-installs luckee-cli via pip when autoInstallCli is true (default). If that fails:

pip install --upgrade 'luckee-cli>=0.1.2026031307,<0.2.0'
openclaw gateway restart

Or set the path explicitly:

openclaw config set plugins.entries.luckee-tool.config.binaryPath "/path/to/luckee-cli"

Not logged in / auth expired

If queries fail with auth/login errors, re-run:

luckee login

Then retry the query. You can also retry with a normal luckee command; if not logged in, Luckee will prompt for web authorization automatically.

Timeout

Increase the default timeout (seconds):

openclaw config set plugins.entries.luckee-tool.config.defaultTimeout 180

Plugin ID mismatch warning

If you see "plugin id mismatch (manifest uses luckee-tool, entry hints luckee-openclaw-plugin)":

openclaw config unset plugins.entries.luckee-openclaw-plugin
openclaw gateway restart

Safety Rules

• Never log or display full tokens. Always redact to sk_x***xx format.
• All install/config operations are idempotent — safe to re-run.
• Do not overwrite unrelated config keys when setting luckee-tool config.
• Never request API URL, User ID, or Lingxing account credentials from users during normal setup/query flows.

Reference

For detailed config schema, channel list, token store format, and error catalog, see reference.md.