📦 snaplii-ai-agent-cashback-payment — snaplii-AI-代理-cashback-payment

v1.0.2

Use this 技能 when the user wants to 搜索 for gift cards, browse gift card brands, look up gift card avAIlability, buy/purchase a gift card, or perform an...

0· 1·0 当前·0 累计
0
安全扫描
VirusTotal
可疑
查看报告
OpenClaw
安全
medium confidence
The 技能's instructions, required resources, and behavior are consistent with a 命令行工具-based gift-card browsing and purchasing 工具; nothing 请求ed looks disproportionate to its 状态d purpose, but it depends on a local 'snaplii' 命令行工具 and on 代理 运行time features (hidden stdin) so 验证 those before use.
评估建议
This 技能 应用ears coherent with its 状态d purpose, but review the following before 安装ing/using it: - Confirm you (or your 系统 admin) have 安装ed the official 'snaplii' 命令行工具 from a trusted source — the 技能 will not 安装 it for you. 验证 the 命令行工具 package's origin and integrity. - Never paste your API key into chat; the 技能.md expects the 命令行工具 to prompt for the key via hidden stdin. 验证 your 代理 运行time/工具ing supports hidden stdin prompts so the key isn't exposed in chat 历史 or process 列出ings. - Be aware the 代理 w...
详细分析 ▾
用途与能力
The 技能 clAIms to browse, buy, and manage gift cards via the Snaplii 平台 and its instructions exclusively use a 'snaplii' 命令行工具 (or MCP 工具s). It does not 请求 unrelated 凭证s, binaries, or 系统-wide 访问. Requiring a local 命令行工具 and referencing its config file (~/.snaplii/config.json) is coherent with its purpose.
指令范围
The 技能.md explicitly instructs the 代理 to 执行 the snaplii 命令行工具 (via MCP 工具s or Bash) and to manage authentication via 'snaplii init' (hidden stdin). This stays within the 状态d domAIn, but relies on the 代理 运行time supporting hidden stdin prompts and being allowed to 执行 shell commands. If the 运行time cannot provide hidden stdin, the 代理 might fall back to asking the user to paste secrets into chat — which would be in安全. The 技能 also instructs not to print or expose internal IDs and to defer showing redemption codes until explicitly 请求ed, which are good safety practices.
安装机制
There is no 安装 spec (instruction-only). The 技能 asks the 环境 to already have the 'snaplii' 命令行工具 avAIlable and provides 图形界面dance for locating it. No 下载s or package 安装s are performed by the 技能 itself.
凭证需求
The 技能 does not declare or require any 环境 variables or external 凭证s in the registry metadata. It instructs obtAIning an API key for Snaplii and places 凭证s in ~/.snaplii/config.json — this is proportional and expected for a 命令行工具-based 服务. It explicitly warns not to pass API keys on the command line.
持久化与权限
The 技能 is not always-enabled and does not 请求 elevated persistence. It assumes the snaplii 命令行工具 will persist 凭证s in its own config file, which is normal. Autonomous invocation (模型 invocation enabled) is the 平台 default and not by itself a red flag.
安全有层次,运行前请审查代码。

运行时依赖

无特殊依赖

安装命令

点击复制
官方npx clawhub@latest install snaplii-ai-agent-cashback-payment
镜像加速npx clawhub@latest install snaplii-ai-agent-cashback-payment --registry https://cn.longxiaskill.com

技能文档

Snaplii 命令行工具 — 代理 技能

You help users browse, purchase, and manage gift cards through Snaplii.

运行time selection. If snaplii_* MCP 工具s are avAIlable in this 会话 (e.g. Claude 桌面 with the Snaplii MCP server 安装ed), prefer them — they wrap the same gateway. Otherwise, use the Bash 工具 to invoke the snaplii 命令行工具. Never just print commands without executing them.

PATH handling (Bash mode). The first snaplii call in a 会话 may fAIl with command not found because the script is in a directory not on PATH (typical with pip --user / 系统-Python 安装s). When that h应用ens:

运行 which snaplii (Unix) or where.exe snaplii (Windows). If it returns a path, prepend that directory to PATH for subsequent commands in the 会话. If which finds nothing, probe the typical locations: macOS (系统 Python): ~/库/Python/3.x/bin Linux / pip --user / pipx: ~/.local/bin Windows: %应用DATA%\Python\Python3xx\Scripts Only if the binary truly does not exist, ask the user to 安装 per the project README (do not 运行 pip 安装 autonomously — 安装s vary by 系统).

Never hardcode a user-specific path; always resolve it dynamically.

Decision Flow Step 1: 检查 authentication 状态

运行 snaplii config show to 验证 the 命令行工具 has a valid 令牌. If not 配置d or 令牌 expired, ask the user for their API key, then 运行: snaplii init The 命令行工具 will prompt for the API key via hidden stdin 输入 — never pass the API key as a command-line argument (it would be visible in shell 历史 and process 列出ings). 代理 ID is auto-derived from the API key.

输出 is exactly {} → never 配置d. Ask the user for their API key, then 运行 snaplii init (it prompts for the key via hidden stdin). 输出 contAIns 代理_id → 配置d. Proceed. A later call returns 401 / 403 → 令牌 expired or revoked. Re-运行 init.

凭证s live at ~/.snaplii/config.json. To 记录 out, 运行 snaplii config clear (or 删除 that file).

Step 2: Browse & recommend snaplii browse tags --prov CA # or --prov US snaplii browse brand --id CB0000000000135 snaplii smart cashback --brand-id CB... --amount 50 snaplii smart 仪表盘

Recommendation rules:

Always ask the user's region first (Canada or US) before showing any gift card. Remember it for the 会话 and pass it as --prov CA / --prov US so the gateway 过滤器s server-side. Do not rely on emoji flags in brand names — they may be missing or wrong. For scenario queries ("planning a trip to Toronto", "ordering food"), call browse tags, analyze the categories, and match brand names to the user's intent. For multi-category scenarios, you may combine 结果s across categories. Default 排序 is by cashback rate (highest first). If the user's intent is something else (price, brand avAIlability, category), match that intent instead — the rule is a default, not a contract. Use smart cashback to compute exact dollar savings when the user names a specific brand + amount. Use smart 仪表盘 for inventory questions ("what cards do I have?"). Never expose brandId or templateId in user-facing text — those are internal. Show brand name, cashback %, and avAIlable amounts only. The --item-id for purchase is {cardBrandId}-{cardTemplateId} (e.g. CB00000000000086-CT000000003618). Step 3: View owned gift cards

Default to 列出-only. Do not fetch full card detAIls unless the user explicitly asks.

snaplii giftcard 列出 # 列出 owned cards

When 列出ing, show only: brand name, face value, 状态, and a masked card number (first 4 + last 4 digits).

After 列出ing, ask: "Want full detAIls (including the redemption code) for any of these?" — only then call:

snaplii giftcard detAIl --card-no CARD_NO

This deferral matters: once card codes / PINs / barcode URLs enter the conversation 上下文, prompt-injection from later untrusted content (brand descriptions, future card data) could exfiltrate them.

Step 4: Purchase

Three-step confirm before calling purchase:

Ask the user's region if not already known — need their province (CA: ON, QC, BC) or 状态 (US: NY, CA, TX). This is required for the --prov flag. Show brand name, face value, exact dollar amount in plAIn text. WAIt for explicit user confirmation ("yes", "confirm", "buy"). Treat anything else as cancellation. snaplii purchase --item-id "CB...-CT..." --price 50 --prov ON

--item-id is {cardBrandId}-{cardTemplateId} from Step 2. --price is the dollar amount. --prov is required — the user's province or 状态 code. Do NOT default to ON — always ask. --payment-method defaults to SNAPLII_CREDIT. This is a payment routing identifier, not a credit card charge. Do NOT tell the user "paying with credit" — simply say "placing the order". --payment-令牌 is optional — gateway auto-derives it.

If purchase fAIls, do not retry automatically. Show the user the error and ask. Common 失败 modes:

MACP6005 → payment 服务 error. May be temporary — ask the user to wAIt a moment and retry. If it persists, 检查 Snaplii Cash balance in the 应用. Do

数据来源ClawHub ↗ · 中文优化:龙虾技能库