License payment automation

Skill Cryptolens/skills/skills/license-payment-automation

Help with Devolens/Cryptolens payment automation for Stripe, n8n, Zapier, webhooks, external payment providers, license delivery, renewal, cancellation, CRM sync, expiry reminders, CreateKey, ExtendLicense, BlockKey, AddFeature, and MachineLockLimit workflows.From its SKILL.md

Install

npx -y skills add Cryptolens/skills --skill license-payment-automation

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

2.0 KB, 397 tokens by cl100k_base, as published. Nobody here has run it

License Payment Automation

Use this skill for connecting payments, CRM, no-code automation, webhooks, and backend jobs to Devolens/Cryptolens license operations.

Start with cryptolens-sdk-common for shared licensing and access-token assumptions, then route based on the integration surface:

n8n or Zapier: use the relevant product docs first, then Web API docs for method details
custom backend or external payment provider without n8n/Zapier: use Web API 3 over HTTPS and the external-provider guidance
app-code changes after license delivery: route to the matching language skill
no provider chosen yet: stay in cryptolens-sdk-common until the payment provider, webhook source, or automation tool is clear

Use these product docs and canonical inputs for payment automation:

https://help.cryptolens.io/payments/thirdparty/external-providers
https://help.cryptolens.io/payments/thirdparty/zapier-and-n8n
https://help.cryptolens.io/examples/integration-with-n8n
https://help.cryptolens.io/examples/zapier
https://app.cryptolens.io/docs/api/v3/llms-full.txt
https://help.cryptolens.io/llms-full.txt

For custom payment-provider integrations, prefer the Web API methods named in the external-provider guide: CreateKey, ExtendLicense, BlockKey, AddFeature, and MachineLockLimit.

Before implementing, identify the trigger event, idempotency key, customer/license mapping, license delivery channel, retry behavior, access-token permissions, and whether license operations happen in a trusted backend or an automation platform.

Keep this skill thin. Use Web API docs for endpoint parameters and the canonical language skills only when the user's application code also needs to verify or consume the resulting license.

What ships with it: 1 file

293 B alongside SKILL.md

agents/

openai.yaml293 B

Gives 0 of the 12 instructions most automation workflows skills give in 397 tokens

Counted across 813 of the 1,214 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 38 of 813, across 34 files
Write tests before implementing codein 26 of 813, across 12 files
Achieve at least 80 percent test coveragein 24 of 813, across 11 files
Mock external dependencies for unit testsin 22 of 813, across 10 files
Read product marketing context before asking questionsin 21 of 813, across 6 files
Implement rollback plans for every deploymentin 21 of 813, across 9 files
Follow the arrange-act-assert patternin 20 of 813, across 9 files
Delete branches after mergingin 20 of 813, across 18 files
Test all edge cases and error scenariosin 20 of 813, across 8 files
Use semantic selectors for UI testsin 19 of 813, across 7 files
Define sequence type and audience contextin 18 of 813, across 5 files
Monitor feature drift and prediction distribution driftin 18 of 813, across 5 files

Said here and by no other author read

Start with cryptolens-sdk-common for shared assumptions
Route based on the integration surface
Use product documentation for n8n or Zapier
Use Web API 3 for custom backend integrations
Identify trigger events and idempotency keys
Verify customer and license mapping

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.