← ClaudeAtlas

integrate-licenselisted

Integrate PowerSoftware (powersoftware.app / powersoftware.cn) license codes into a client software product — machine-code binding, trial claim, activation, edition gating, purchase-page redirect, in-app issuance/upgrade (HMAC), and update checking — using the official zero-dependency powersoftware-license-sdk (Node.js / Python / Java). Use when adding license or paywall verification to a desktop/CLI product, when the user mentions 授权 / 授权码 / 激活 / 试用 / 幂栈 / licenseCode / activationToken / claimTrial / verifyCached, or is wiring the product published via the publish-license-product skill.
powersoftware-app/powersoftware-agent-skills · ★ 0 · AI & Automation · score 60
Install: claude install-skill powersoftware-app/powersoftware-agent-skills
# Integrate PowerSoftware License (client software) Teaches the agent to wire a **client software product** into the PowerSoftware license system correctly in one pass. The SDK is a *library* (source-copy, zero dependency, three languages); this skill is the *knowledge* — which scenario applies, which calls go where, and the rules that are easy to get wrong. SDK source is fetched at runtime from its authoritative repo (see Step 2); **never copy SDK code from this skill — there is none here on purpose.** Companion skill: [`publish-license-product`](../publish-license-product/SKILL.md) publishes the product first and yields the `productUniqueCode` used here. ## Step 0 — Pick the scenario (decide this before writing any code) | | **Scenario A — platform full funnel (TRIAL_FIRST)** | **Scenario B — orders off-platform** | |---|---|---| | Who charges | PowerSoftware (Alipay / PayPal) | The developer's own payment | | Who issues codes | Platform automatically after payment | Your **server** calls the API (HMAC-signed) | | Needs `apiSecret`? | ❌ No | ✅ Yes — server-side **only** | | Needs your own server? | ❌ No, pure client | ✅ Yes | | Trial (`claimTrial`) | ✅ Supported | ❌ None | | Platform purchase page | ✅ SDK one-liner redirect | ❌ Developer handles UX | - Indie dev / small team without a backend → **A**. - Already has own payment, just wants platform issuance + verification → **B**. Ask the user which one if their product setup doesn't make it obvious. ## Prerequisites