License key generation

Skill Cryptolens/skills/skills/license-key-generation

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.From its SKILL.md

Install

npx -y skills add Cryptolens/skills --skill license-key-generation

Assembled 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.

SKILL.md

1.8 KB, 347 tokens by cl100k_base, 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-common until 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-generation
https://help.cryptolens.io/payments/thirdparty/external-providers
https://app.cryptolens.io/docs/api/v3/CreateKey
https://app.cryptolens.io/docs/api/v3/llms-full.txt
https://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.

What ships with it: 1 file

301 B alongside SKILL.md

agents/

openai.yaml301 B

Gives 0 of the 12 instructions most data backend skills give in 347 tokens

Counted across 258 of the 277 authors here whose files we hold, read 2026-09-06

Centralize error handling in one handlerin 38 of 258, across 20 files
Select only needed columns in queriesin 36 of 258, across 18 files
Check cache before querying the databasein 36 of 258, across 19 files
Wrap multi-step writes in transactionsin 36 of 258, across 18 files
Retry failed requests with exponential backoffin 36 of 258, across 18 files
Batch fetch related records to avoid N+1 queriesin 34 of 258, across 16 files
Use resource-based URLs for REST endpointsin 31 of 258, across 13 files
Separate business logic into a service layerin 29 of 258, across 17 files
Queue background jobs instead of blocking requestsin 29 of 258, across 14 files
Abstract data access behind repository interfacesin 25 of 258, across 13 files
Log structured JSON with request contextin 15 of 258, across 7 files
Use a shared store for rate limitingin 14 of 258, across 6 files

Said here and by no other author read

Start with the shared licensing skill, then route by platform
Use Web API 3 for backend or unsupported languages
Use canonical product docs for key-generation decisions
Treat key generation as a server-side workflow
Ask how generated keys are delivered and stored
Identify product id, period, features, and machine limits before implementing

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.