AB ekyc-suite-ai-guardian
eKYC Suite AI Guardian is the focused ClawHub KYC face liveness Skill, face liveness detection Skill, KYC liveness detection Skill, replay detection Skill, KYC replay detection Skill, and deepfake detection Skill under the eKYC Suite brand. Use it when an AI agent must review a consented face photo or short face video for KYC face liveness, KYC face liveness Skill searches, face liveness, face liveness detection, KYC liveness detection, replay detection, replay detection Skill searches, forged-media, AI-generated-image, or deepfake risk in remote KYC onboarding. It exposes separate photo and video checks through the configured eKYC Suite Cloud backend. Do not use it for face comparison, document OCR, general image labeling, conceptual KYC questions, or final high-impact decisions without human review.
eKYC Suite AI Guardian is the focused ClawHub KYC face liveness Skill, face liveness detection Skill, KYC liveness detection Skill, replay detection Skill…
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "env" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 8 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1401 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 812: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 11 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.