SKILLEMALL.ai
GitHub ↗ RU Sign in

AB verify-document

Check whether a document (PDF or image) shows signs of tampering or forgery before you rely on it. Use when the user asks to verify a payslip, invoice, bank statement, ID document, contract, or any document where authenticity matters.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 1 file body ≈ 944 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Check whether a document (PDF or image) shows signs of tampering or forgery before you rely on it.

As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

AnalyzerFinancetype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
B
73/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Failures and branches w 10
55
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: verify-document (sickn33/agentic-awesome-skills)

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
  • 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 234 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 73/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 20 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 944 tokens
  • 100Running it twice. No mutating operations

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
  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +3Description length 234: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 20 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.