License subscriptions

Skill Cryptolens/skills/skills/license-subscriptions

Help with Devolens/Cryptolens subscription licensing, expiry checks, renewal logic, grace periods, ExtendLicense renewals, BlockKey cancellation handling, Stripe webhook flows, and subscription access review across .NET, Python, Java, Node.js, direct Web API integrations, and related stacks.From its SKILL.md

Install

npx -y skills add Cryptolens/skills --skill license-subscriptions

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, 326 tokens by cl100k_base, as published. Nobody here has run it

License Subscriptions

Use this skill for subscription-backed licensing, expiration checks, renewal handling, cancellation handling, support/update entitlement, and billing-webhook-driven license updates.

Start with cryptolens-sdk-common for shared licensing assumptions, then route to the language-specific skill that matches the task:

.NET: cryptolens-dotnet
Python: cryptolens-python
Java: cryptolens-java
unsupported language, backend-only renewal flow, or no matching SDK skill: route through cryptolens-sdk-common and the Web API 3 HTTP docs instead of inventing SDK APIs
no language chosen yet: stay in cryptolens-sdk-common until the target SDK, backend, or payment provider is clear

Use these product docs and canonical inputs for subscription decisions:

https://help.cryptolens.io/licensing-models/subscription
https://help.cryptolens.io/payments/thirdparty/external-providers
https://app.cryptolens.io/docs/api/v3/llms-full.txt
https://help.cryptolens.io/llms-full.txt

Before implementing, identify whether the subscription gates product access, updates, support, or specific features; how much grace period to allow; which payment event extends the license; and which cancellation or failed-payment event blocks or downgrades the license.

Keep this skill thin. Use the language skills for in-app expiry checks and the Web API docs for backend methods such as ExtendLicense, BlockKey, and related payment-provider automation.

What ships with it: 1 file

361 B alongside SKILL.md

agents/

openai.yaml361 B

Gives 0 of the 12 instructions most pricing monetisation skills give in 326 tokens

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

Read product marketing context before asking questionsin 39 of 324, across 16 files
Demonstrate paid feature value with previewsin 21 of 324, across 8 files
Choose a value metric that scales with customer valuein 21 of 324, across 14 files
Verify webhook signatures on every eventin 19 of 324
Send trial expiration warnings earlyin 16 of 324, across 6 files
Minimize steps from paywall to paymentin 15 of 324, across 5 files
Price between next best alternative and perceived valuein 15 of 324, across 7 files
Grandfather existing customers when raising pricesin 14 of 324, across 10 files
Understand upgrade context, product model, and user journey firstin 14 of 324, across 5 files
Show paywalls only after users experience valuein 13 of 324, across 6 files
Include an escape hatch on every paywallin 12 of 324, across 4 files
A/B test paywall variationsin 11 of 324, across 3 files

Said here and by no other author read

Start with cryptolens-sdk-common for shared licensing assumptions
Route to the language-specific skill matching the task
Use the canonical product docs for subscription decisions
Identify what the subscription gates before implementing
Determine grace period, extending payment event, and blocking event
Use language skills for in-app expiry checks

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.