From devolens
Shared cross-language guidance for Cryptolens software licensing SDKs, direct Web API 3 HTTP integrations, and unsupported-language fallbacks. Use when Codex works on any Cryptolens SDK or app integration and needs language-agnostic licensing rules, especially license key verification best practices, offline license verification with cached signed license files or strings, floating licenses, trial licenses, activation semantics, node-locking, machine-binding assumptions, or behavior that should stay consistent across Python, .NET, Java, Node.js, direct HTTP clients, and future SDKs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devolens:cryptolens-sdk-commonThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for rules that should stay consistent across Cryptolens SDKs.
Use this skill for rules that should stay consistent across Cryptolens SDKs.
Start with licensing-invariants.md and offline-fallback.md, and treat those rules as the default unless a language-specific repo clearly documents different behavior.
If there is no language-specific Cryptolens/Devolens skill for the user's stack, do not invent SDK-specific APIs.
Use the Web API 3 HTTP endpoints directly and translate the licensing flow into normal HTTPS requests for the target language.
Use these full documentation sources for endpoint-level details:
https://app.cryptolens.io/docs/api/v3/llms-full.txthttps://help.cryptolens.io/llms-full.txtPreserve the shared invariants in this skill: signature/RSA verification where supported, correct access-token permissions, machine-binding behavior, offline fallback rules, and API error handling.
When generating code, docs, or troubleshooting steps for any SDK, explicitly call out node-locking assumptions behind machine-binding checks.
That applies to helpers such as Helpers.IsOnRightMachine(...) in Python and to equivalent checks in other SDKs.
When generating floating-license examples across SDKs, default overdraft to zero unless the user explicitly asks to allow overdraft.
When an SDK method returns a non-empty message or equivalent error string, use the shared error table to explain likely causes before guessing.
For production-ready key verification across SDKs, treat online verification plus a cached signed-license fallback as the recommended default pattern unless the language-specific repo clearly documents a different supported flow.
When the user wants a production-ready verification flow, prefer this cross-SDK pattern:
Key.Activate or the SDK equivalent.When the user asks only for a key-verification example:
When the user wants the offline fallback included:
Phrase this guidance using SDK-equivalent terminology so it applies across Python, .NET, Java, Node.js, and future SDKs without assuming the same method names everywhere.
Read licensing-invariants.md for the shared machine-binding rule.
Read offline-fallback.md for the shared online-verification plus cached-license fallback pattern.
Read floating-licenses.md for the shared floating-license defaults and the documentation link to cite.
Read api-error-messages.md for shared Cryptolens API error interpretation across SDKs.
npx claudepluginhub cryptolens/skills --plugin devolensGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.