CtrlK
BlogDocsLog inGet started
Tessl Logo

kyc-doc-parse

Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable, well-sequenced extraction workflow that assumes Claude's competence and adds a justified untrusted-input warning. It fully satisfies conciseness, actionability, workflow, and disclosure for a skill of this size.

DimensionReasoningScore

Conciseness

The body is lean and functional — an inventory table, an exact JSON schema, and gap-flagging rules — with no padding explaining what KYC, a passport, or source-of-funds means. It is not level 2 because there is no unnecessary explanation to trim.

3 / 3

Actionability

It gives a copy-paste-ready JSON record with concrete field names and types, explicit guidance ("Use null for any field not found — do not guess"), and a clear gap-checklist with thresholds ("address proof older than 3 months"). It is not level 2 because the guidance is complete and executable, not pseudocode.

3 / 3

Workflow Clarity

The three steps are explicitly sequenced (inventory → extract → flag gaps) with a verification checkpoint in Step 3 that checks expiry and age before handing to the rules engine. It is not level 2 because a checkpoint with explicit pass/fail criteria is present; the operation is read-only extraction so the destructive-operation cap does not apply.

3 / 3

Progressive Disclosure

A single-purpose skill under 50 lines with no bundle files, organized into clearly headed sections and an input-safety note — matching the rubric's allowance for simple skills to score 3 on good organization alone. It is not level 2 because the structure is well-organized with no nested or missing references.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities, includes natural trigger terms, and explicitly pairs what-it-does with when-to-use-it. No notable weaknesses for a frontmatter description.

DimensionReasoningScore

Specificity

It enumerates multiple concrete extraction targets — "identity, ownership, control, source of funds, and document inventory" — matching the top anchor for listing several specific concrete actions. It is not level 2 because it goes beyond naming a domain plus a few actions.

3 / 3

Completeness

It answers both what ("Parse an investor or client onboarding packet into structured KYC fields") and when ("Use as the first step of KYC screening") with an explicit trigger clause, satisfying the top anchor. The "Use as..." clause avoids the level-2 cap for missing trigger guidance.

3 / 3

Trigger Term Quality

Natural domain terms a user would say — "investor or client onboarding packet", "KYC fields", "KYC screening" — are present with good coverage. It is not level 2 because the keywords are natural and varied rather than sparse or jargon-only.

3 / 3

Distinctiveness Conflict Risk

It carves a clear KYC onboarding niche with distinct triggers unlikely to fire for unrelated skills. It is not level 2 because the domain and triggers are specific rather than merely "somewhat specific".

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/financial-services
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.