sumsub · Agent Skills
28 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.
sumsub-analyze-regulation
Analyze a regulation document (PDF or text) and produce a Sumsub configuration plan — mapping regulatory requirements to Sumsub entities (levels, questionnaires, PoA presets, TM rules, workflows, AML resolution rules). TRIGGER when the user provides a regulation PDF, legal act, or compliance requirement document and wants to know what to configure in Sumsub. Acts as the entry point before invoking sumsub-create-level, sumsub-create-questionnaire, sumsub-create-poa-preset, sumsub-create-workflow,
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-api-auth
Authenticate to the Sumsub API with an App Token + secret key (HMAC-SHA256 request signing). TRIGGER when the user asks to "call / sign / authenticate Sumsub API requests", debugs 401 Unauthorized / signature errors against api.sumsub.com, or needs a working request example with X-App-Token / X-App-Access-Sig / X-App-Access-Ts headers. SKIP only when a more specific skill in this repo (questionnaire/level/workflow/POA-preset/generic) already covers the user's actual task — those skills sign requ
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-api-generic
Catch-all fallback for any Sumsub API task that does NOT match a more specific skill (e.g. create-sumsub-level, sumsub-create-questionnaire, sumsub-api-auth). TRIGGER when the user wants to call, inspect, or debug a Sumsub API endpoint not otherwise covered — fetching applicants, listing levels, reviewing AML hits, exporting data, generating SDK tokens, anything against api.sumsub.com. The procedure — locate the right endpoint in the OpenAPI schema, read its request/response shape, build the pay
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-check-databases
Discover the Databases (check-sources) Sumsub offers for a country, whether each is enabled for the tenant, and how database / non-document (eKYC) verification fits into a verification level. Use WHEN a user asks which database / non-document check-sources are available for a country, whether they're enabled, or how to add database validation / non-doc identity / non-doc address verification to a level. Also called by sumsub-create-level before placing those sources. Do NOT use for document-only
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-check-permissions
Fetch the current tenant's allowed entitlements (BackgroundCheckTarget list). Returns JSON {"allowedChecks":{key:label}} — a map whose keys are the enabled entitlement keys. Called by sumsub-create-level (and other create- skills) before building a payload to gate entitlement-required features.
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-check-skills-version
Verify that the locally installed Sumsub agent-skills package is compatible with the published version before doing any Sumsub work. TRIGGER at the start of any task that touches Sumsub — Sumsub Dev MCP tools (mcpSumsubDev), KYC/AML workflows, applicants, checks, transactions, verification levels, verification links, questionnaires, fraud network, VASP lists, or anything Sumsub-related — so the user is warned before a stale skills package produces wrong results. Also use this skill when the user
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-conformance
Check whether a tenant's DEPLOYED Sumsub config actually satisfies a regulation/policy document — tracing each requirement to where it is collected, scored, and ENFORCED, and flagging "collected-but-not-enforced" gaps. TRIGGER when the user has a regulation/policy/requirements doc (PDF or text) and wants to verify the live config matches it, audit a client's setup against compliance rules, "does my config satisfy this regulation", "check conformance / gap analysis", or close the loop after confi
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-aml-resolution-rules
Create, edit, reorder, delete, and publish Sumsub AML Resolution Rules (the AML Resolution Rule Chain) that auto-review AML screening hits. TRIGGER when the user wants to auto-clear false positives, auto-confirm true positives, carry over previous AML reviews, tag AML hits, or set up / inspect / publish the AML rule chain. SKIP for transaction-monitoring (KYT) rules, workflow routing, or AML check settings on a level (separate skills cover those).
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-cross-check-preset
Create or update a Sumsub cross-check preset (name/address comparison rules between POI and POA documents) via POST/PATCH /resources/api/agent/crossCheckPresets and GET /resources/api/agent/crossCheckPresets/{id}. TRIGGER ONLY when the user EXPLICITLY asks to override how cross-checks compare names or addresses — e.g. "switch name match to strict", "allow fuzzy address match", "ignore middle-name mismatch", "create a custom cross-check preset". SKIP by default — Sumsub ships sensible defaults tu
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-kyt-rules
Configure KYT transaction monitoring rules with tags, applicant risk scoring and risk levels. TRIGGER when the user says "create / add / set up KYT rules / TM rules", "configure transaction monitoring", describes scoring logic (flag/block/hold transactions by amount, country, direction, peer, or other conditions), wants to "update / change / edit an existing rule" (by name or title), asks to "configure applicant scoring / risk scoring / assessment", "set up tags", "define risk levels / threshold
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-level
Create or update a Sumsub applicant level. POST /resources/applicants/-/levels to create new, PATCH same path to update (id in body), GET /resources/applicants/-/levels/{id} to read one back. TRIGGER when the user asks to "create / add / build / update / edit a Sumsub level", supplies a list of required steps for an applicant flow (identity / selfie / proof-of-residence / questionnaire / payment methods / email or phone verification / KYB / e-sign), or wants a level wired to a specific questionn
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-poa-preset
Create or update a Sumsub Proof-of-Address (POA) preset. POST /resources/api/agent/poaStepSettings to create new, PATCH same path to update (id in body), GET /resources/api/agent/poaStepSettings/{id} to read one back. TRIGGER when the user asks to "create / add / build / configure / update / edit a POA preset" or "PoA step settings", configure which proof-of-address document types are accepted (utility bills, bank statements, tax bills, etc.), set validity periods per provider type, enable POI-a
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-questionnaire
Create or update a Sumsub KYC questionnaire definition. POST /resources/api/agent/questionnaires to create new (fails 409 if id exists), PATCH same path to update (fails 404 if id is unknown), GET /resources/api/agent/questionnaires/{id} to read one back. TRIGGER when the user asks to "create / add / build / update / edit a Sumsub questionnaire", or supplies a list of questions / sections meant for a Sumsub applicant flow, or references a questionnaire id / definition to be POSTed or PATCHed. SK
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-transaction
Submit a transaction to Sumsub Transaction Monitoring (KYT) via the ApplicantResource API. TRIGGER when the user asks to "submit / create / send / record a transaction", "test a KYT rule with a transaction", post a fiat or crypto payment for monitoring, attach Travel Rule data to a transfer, log a user-platform event (signup / login / password-reset / 2FA-reset) for monitoring, or submit a transaction for an applicant that does not exist yet (the request creates them). SKIP for editing arbitrary
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-create-workflow
Create a Sumsub applicant workflow — verification routing (levels, branches, country/age rules, final-rejection or manual-review steps) or an action workflow (post-verification tagging, notes, source-key changes). TRIGGER on requests to create/build/add a workflow or a flowchart-style routing description. Builds, validates, and saves a draft, then publishes it — gated by live traffic — automatically when the workflow's traffic is low, only after explicit confirmation when it's high. Publishing c
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-integrate-dint-standalone
Add Sumsub Device Intelligence (the Fisherman JS module) to your own web pages where there is NO Sumsub verification widget — login, signup, password reset, 2FA, checkout, or any high-value action you want fraud-screened. TRIGGER when the user asks to "add device intelligence to login / signup", "fingerprint the device on a custom page", "use Fisherman standalone / self-hosted", "ongoing monitoring of platform events", "pre-KYC device check", "detect multi-accounting at signup", or "send a finan
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-integrate-dint-websdk
Add Sumsub Device Intelligence (the Fisherman module) to a web project that already verifies users with the Sumsub WebSDK. TRIGGER when the user asks to "add device intelligence", "enable device capture / fingerprinting in the WebSDK", "turn on Fisherman", "detect device fraud / multi-accounting in the verification flow", or asks how device risk labels get onto an applicant verified through the WebSDK. Covers the whole loop — enabling Capture device data on the level, the automatic in-SDK Fisher
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-integrate-id-connect
End-to-end recipe for integrating Sumsub ID Connect — the OIDC-based "Verify with Sumsub ID" flow that lets a user share previously-verified identity claims with your app. TRIGGER when the user asks to "integrate Sumsub ID Connect", "add Verify-with-Sumsub-ID button", "reuse Sumsub KYC via OIDC", "exchange the Sumsub authorization code", "mint a Sumsub ID share token", or asks how to wire up @sumsub/id-connect, the OIDC code → accesstoken exchange (/api/snsId/oauth/token), the share-token / part
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-integrate-msdk
Integrate the Sumsub Mobile SDK (IdensicMobileSDK / SNSMobileSDK) into a native iOS or Android app — even when the user doesn't name the SDK (e.g. "add Sumsub/KYC to my iPhone app", "add KYC to my Android app", "show the verification screen", "launch Sumsub from a view controller / activity"). Detects the platform from the project (iOS Xcode/Swift vs Android Gradle/Kotlin) and follows the matching track. Covers install, permissions, init, token refresh, and presenting / launching the flow. SKIP
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-integrate-travel-rule
End-to-end recipe for integrating Sumsub Travel Rule — deciding which of the three exchange flows applies, identifying the counterparty VASP, submitting the transfer, reading the exchange status, finalising or cancelling it, answering requests other VASPs send you, handling the unhosted-wallet path when no VASP is attributed, and finding existing transactions (deduplication before after-settlement exchanges). TRIGGER when the user asks to "integrate / add / implement Travel Rule", "send Travel R
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-integrate-websdk
End-to-end recipe for adding Sumsub KYC to a website or web app via the Sumsub WebSDK. TRIGGER when the user asks to "integrate / embed / add Sumsub", "show the KYC widget", "add WebSDK", "verify users with Sumsub on the frontend", supplies an existing levelName they want to plug into a page, or asks how to wire up access tokens / lifecycle events / webhooks for Sumsub verification in an arbitrary project. Covers the whole loop — level setup, server-side access-token signing, snsWebSdk init (van
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-manage-applicant-tags
Add, replace, or remove tags on a Sumsub applicant profile via the public API — POST /resources/applicants/{applicantId}/tags/add (additive), POST .../tags (overwrite the full set), DELETE .../tags (remove), read-back via GET .../one. TRIGGER when the user asks to "tag / untag an applicant", "add / remove / clear applicant tags", "label an applicant profile", or "replace an applicant's tag set". SKIP for transaction tags, tag definitions with scoring weights, or applicant risk assessment (use su
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-manage-client-lists
Create and populate Sumsub client lists — the named sets of keys that workflow conditions and KYT rules match against (clientLists. ). TRIGGER when the user wants to build a high-risk country list, add or remove entries, check whether a key is in a list, resolve a list name to its id, or un-blocklist an applicant. SKIP for blocklisting an applicant (that is POST /resources/applicants/{id}/blacklist, not a list write) and for writing the rules that reference a list (sumsub-create-kyt-rules, sumsu
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30
sumsub-resolve-currency
Resolve and validate the currency fields Sumsub expects on a transaction — info.currencyCode, info.currencyType, info.cryptoParams.cryptoChain and the amountInDefaultCurrency / defaultCurrencyCode pair. Reads the catalogue from GET /resources/kyt/currency?type=crypto|fiat and resolves a (symbol, chain, contract) triple to exactly one asset, normalising chain aliases and refusing ambiguous input rather than guessing. TRIGGER when the user asks "which currency codes / chains does Sumsub support",
- 1h installs
- 2
- GitHub stars
- 7
- Updated
- Oct 30