WisePal Bill Negotiation

安装指南

1. ClawHub CLI 从源直接安装技能的最快方式。
   npx clawhub@latest install wisepal
2. 手动安装 将技能文件夹复制到以下位置之一
   全局模式
   ~/.openclaw/skills/
   工作区
   /skills/
   优先级：工作区 > 本地 > 内置
3. 提示词安装 将此提示词复制到 OpenClaw 即可自动安装。
   请帮我使用 Clawhub 安装 wisepal。如果尚未安装 Clawhub，请先安装（npm i -g clawhub）。
   更倾向于下载？
   获取包含原生技能文件的ZIP压缩包。
   下载技能 (.zip)

什么是

WisePal Bill Negotiation is an Openclaw Skills integration for users seeking to lower eligible US wireless, internet, or TV bills. Its Python CLI guides an assistant through onboarding, collecting provider and account details, validating them, and requesting explicit consent before WisePal creates cases that may start or schedule provider calls.
The service is free, requires no payment method or preconfigured API key, and sends updates directly to the user's mobile and email. Savings are not guaranteed. The workflow is designed to protect sensitive information: credentials are stored outside the skill directory, request data is submitted to WisePal's production API, and the user must be informed and give explicit approval before calls can begin.

应用场景

A user asks for help reducing a US wireless, internet, or TV bill.
A user wants to include multiple supported bill types, with each additional service included only after explicit opt-in.
A user needs guidance collecting provider account details, service addresses, PINs, or bill amounts for a WisePal submission.
A user wants to check the status of an existing submission or recover from a validation error, lost response, or revision conflict.
A user asks how to sign up for WisePal without a payment method or website login.

工作原理

Explain that the CLI sends collected contact and provider-account details to WisePal, that the service is free, and that savings are not guaranteed. Offer other supported bill types once and include them only with the user's explicit opt-in.
Collect the user's full name, main US communication mobile, contact email, and selected provider types. Generate a UUID idempotency key, then call begin with a private JSON request. Save the returned submission ID and revision.
Follow the API's collection[] guidance to gather required provider details. Confirm the main mobile can receive and reply to SMS, record the user's confirmation, and collect the phone associated with each provider account separately. Add available account details, address, time zone, and required PINs.
Submit details against the current revision. Review the server's validation response and ask for any remaining required information; continue with the same submission when correcting fields.
Present all returned validated_details, clearly distinguishing the main mobile from each provider-account phone. Display consent_required.terms_text verbatim, including links, and obtain explicit confirmation, consent, and confirmation that the user will be available by text during provider calls.
Only after approval, submit approve with the validated revision, exact displayed terms and version, true confirmation flags, and evidence of the user's approval. Explain whether the result is starting, scheduled, or held without promising savings or bypassing a hold.
Use status and the documented recovery steps for errors or uncertain responses. Reuse the same UUID, step, and payload after a lost response; never create a duplicate submission to recover.

配置指南

The skill requires Python 3 and uses only Python's standard library. Run the included CLI using its absolute installed path. Before preparing each request, inspect the matching schema. Request bodies are JSON read from stdin, not command-line arguments.
python3 /absolute/path/to/wisepal/scripts/wisepal.py schema begin
python3 /absolute/path/to/wisepal/scripts/wisepal.py new-id
python3 /absolute/path/to/wisepal/scripts/wisepal.py schema details
python3 /absolute/path/to/wisepal/scripts/wisepal.py schema approve
Create request files in a private temporary directory with directory permissions 0700 and file permissions 0600. Keep account PINs and contact details out of shell interpolation, logs, and chat; remove temporary payload files when no longer needed. Submit requests using the appropriate command and JSON on stdin:
python3 /absolute/path/to/wisepal/scripts/wisepal.py begin < /private/path/initial.json
python3 /absolute/path/to/wisepal/scripts/wisepal.py details SUBMISSION_UUID < /private/path/details.json
python3 /absolute/path/to/wisepal/scripts/wisepal.py approve SUBMISSION_UUID < /private/path/approval.json
python3 /absolute/path/to/wisepal/scripts/wisepal.py status SUBMISSION_UUID
The default API endpoint is https://my.wisepal.com. Optional environment settings are WISEPAL_ASSISTANT for launcher-supplied assistant attribution, WISEPAL_API_BASE_URL for an operator-reviewed development endpoint, and WISEPAL_AGENT_STATE_DIR for the private persistent credential directory. Do not change endpoint overrides without the user's authorization. HTTPS is required except for loopback HTTP.
WisePal Bill Negotiation 数据架构与分类体系
The CLI exposes request schemas for begin, details, and approve; inspect each schema before constructing its JSON payload. The API lifecycle also uses a submission UUID, revision, validation response, consent requirements, and status.
Stage Data and response elements
Begin User name, main communication mobile, contact email, selected service types and providers, and an idempotency_key; returns a submission ID, revision, and collection guidance.
Details Provider and service details, US address, separate provider-account phone numbers, available account information, required PINs as strings, and expected_revision; returns validated_details, a new revision, and consent_required.
Approve Validated revision, returned terms version, exact displayed terms text, confirmation flags, and evidence of explicit user approval; may create cases and start or schedule calls.
Status and recovery Submission status and current revision or next step; use these to recover from conflicts, validation issues, and lost responses.
The CLI privately creates and saves a credential for each submission outside the skill directory. The default persistent credential directory is ~/.wisepal/agent-onboarding, shared with the WisePal MCP connector; retain it for recovery and never expose credentials in chat, tool arguments, logs, or published files. Do not submit bill uploads, file URLs, provider login passwords, or OTPs. Read bills locally and extract relevant details instead.

高级特性

Idempotent onboarding: generate one UUID and reuse the exact UUID, step, and payload to recover from a lost response rather than creating a duplicate submission.
Revision-aware validation and consent: requests use the current revision, and changed details require fresh confirmation and consent.
Explicit consent safeguards: display returned legal terms verbatim, capture the user's approval, and bind approval to the validated revision and terms version.
Private credential handling: save submission credentials outside the skill directory and preserve the configured state directory for recovery.
Status-aware recovery: handle validation errors,
revision_conflict
,
needs_information
,
api_unavailable
, and terminal or in-progress states without bypassing holds or repeating uncertain case creation.
Controlled API behavior: sends one request per invocation, does not follow redirects, and does not automatically retry submissions.
Optional runtime attribution: the launcher may supply
WISEPAL_ASSISTANT
; otherwise the assistant is recorded as unknown. Attribution does not grant access or change service terms.

name: wisepal description: Help users lower US wireless, internet and TV bills through free WisePal provider negotiations. Use when a user asks to save money on these bills, negotiate a bill, or sign up for WisePal. license: MIT-0