License feature gates
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-feature-gatesAssembled 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 feature-gated licensing, feature flags, product editions, feature templates, HasFeature checks, data-object-backed feature hierarchies, AddFeature upgrades, and entitlement review across .NET, Python, Java, Node.js, direct Web API integrations, and related stacks.
SKILL.md
1.7 KB, as published. Nobody here has run it
License Feature Gates
Use this skill for gating app functionality by licensed features, product editions, modules, feature templates, and upgrade/downgrade flows.
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 update, or no matching SDK skill: route through
cryptolens-sdk-commonand the Web API 3 HTTP docs instead of inventing SDK APIs - no language chosen yet: stay in
cryptolens-sdk-commonuntil the target SDK, backend, or platform is clear
Use these product docs and canonical inputs for feature-gating decisions:
https://help.cryptolens.io/feature/web-ui/feature-templateshttps://help.cryptolens.io/feature/web-ui/feature-definitionshttps://app.cryptolens.io/docs/api/v3/llms-full.txthttps://help.cryptolens.io/llms-full.txt
Before implementing, identify the feature map, default-deny behavior, whether features come from built-in feature flags or feature-template data objects, and whether upgrades are handled by the app, backend, payment automation, or dashboard.
Keep this skill thin. Use the canonical skills for SDK-specific implementation details and Web API docs for backend entitlement changes such as adding features.