Sumsub check permissions

Skill SumSubstance/agent-skills/skills/sumsub-check-permissions

Agent Skills for the Sumsub API

Install

npx -y skills add SumSubstance/agent-skills --skill sumsub-check-permissions

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.
4 stars4 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

Fetch the current tenant's allowed entitlements (BackgroundCheckTarget list). Returns JSON with `allowed` (array of permission keys) and `descriptions` (map of key → human-readable label). Called by sumsub-create-level (and other create-* skills) before building a payload to gate entitlement-required features.

SKILL.md

2.2 KB, as published. Nobody here has run it

Check Permissions

Returns the tenant's allowed entitlements so callers can gate features before making any API writes.

Usage

Run the script and parse the result:

bash ${CLAUDE_SKILL_DIR}/scripts/check_permissions.sh

Output: raw Sumsub response body followed by HTTP <code>.

Success (HTTP 200):

{"allowedChecks": {"REUSABLE_KYC_SDK": "Reusable KYC via API/SDK: ...", "VIDEO_IDENT": "Video Identification: ..."}}
HTTP 200

Error (non-200):

{"description":"Unauthorized","errorName":"...","correlationId":"..."}
HTTP 401

allowedChecks — map of permission key → human-readable label for all entitlements enabled for this tenant.
Permission keys present as keys of allowedChecks are the allowed entitlements.

How callers should use this

If the HTTP status is not 200, stop immediately — show the error body to the user and do not proceed.

After a successful response, check whether the required BackgroundCheckTarget key is present in allowedChecks. If it is not, stop immediately — do not build or POST the payload. Tell the user which entitlement is missing and that they need to contact their CSM or Sumsub Support to get it enabled.

Entitlement → feature mapping (key examples):