License key generation
Skills for coding agents to add license verification to your application, implement licensing models and integrate Devolens with other services, supporting Claude Code, Codex and other agents.
npx -y skills add Cryptolens/skills --skill license-key-generationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Help with Devolens/Cryptolens backend license key creation, CreateKey API usage, license templates, server-side access-token scope, payment-success license delivery, customer-linked licenses, product IDs, periods, features, maximum machines, and license provisioning workflows.
SKILL.md
1.8 KB, as published. Nobody here has run it
License Key Generation
Use this skill for creating license keys from a backend, payment flow, admin tool, migration script, CRM workflow, or external automation.
Start with cryptolens-sdk-common for shared licensing assumptions, then route based on where key creation happens:
- backend or unsupported language: use Web API 3 over HTTPS and avoid inventing SDK APIs
- .NET backend or SDK repo task:
cryptolens-dotnet - Python backend or SDK repo task:
cryptolens-python - Java backend or SDK repo task:
cryptolens-java - no platform chosen yet: stay in
cryptolens-sdk-commonuntil the backend, payment provider, or automation platform is clear
Use these product docs and canonical inputs for key-generation decisions:
https://help.cryptolens.io/examples/key-generationhttps://help.cryptolens.io/payments/thirdparty/external-providershttps://app.cryptolens.io/docs/api/v3/CreateKeyhttps://app.cryptolens.io/docs/api/v3/llms-full.txthttps://help.cryptolens.io/llms-full.txt
Never put a CreateKey access token in distributed client code. Treat key generation as a server-side or trusted-automation workflow, and ask how the generated key should be delivered and stored.
Before implementing, identify product id, period/expiry behavior, feature flags or template, maximum machines, customer association, payment/order id mapping, and access-token permissions.
Keep this skill thin. Use Web API docs for endpoint parameters and the canonical skills for any app-side verification that consumes the generated license key.