How Skills Library licensing works

Plain answers for subscribers, IT reviewers, and AI agents verifying what our skills do.

The model

Every skill you download from the Member Downloads page includes its full reference content, packaged and versioned with the skill itself. A license check at the start of a session verifies your subscription is active and unlocks that included content on your machine. Content does not download at runtime — the server's response is a short access token, never files and never instructions.

What the license check transmits

Three values: your license key (issued with your download), the skill's id, and its version. Nothing else — no client data, no files, no conversation content, none of your other credentials. Requests go to skills.cjhutsenpiller.com, operated by The Agency Skills Library (Hutsenpiller), the same vendor that publishes the skills.

What the unlock script does

scripts/unlock.py is short and auditable: it requests the token, verifies the integrity of the included content against it, and writes reference data files (markdown/JSON only) into the skill's own folder — or into ~/.skills-library/cache/<skill>/ when the skill directory is read-only, as in some sandboxed agent environments. It never executes anything it unlocks.

Why licensing is checked at all

The library is a subscription: active subscribers get every skill, every update, and new skills as they ship. When a subscription ends, skills stop unlocking — that's the whole mechanism. Cancel anytime; nothing else about your machine changes.

Questions

cj@hutsenpillerinsurance.com