SKILLEMALL.ai

CB ocr-pipeline-and-quality

Xberg OCR backends, preprocessing, caching, page acceptance, hOCR, tables, cross-backend quality. Use for OCR behavior or A/B quality work.

xberg-io/xberg Agent Skills author: xberg-io MIT 2 files body ≈ 902 tokens Open the sourcegithub.com↗ analyzed 12 h ago

Xberg OCR backends, preprocessing, caching, page acceptance, hOCR, tables, cross-backend quality.

As a process B 70/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

ProcedureSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
50
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    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: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • error name-missing SKILL.md: frontmatter has no `name`
    • note frontmatter-key unknown frontmatter key "type"
    • note frontmatter-key unknown frontmatter key "title"
    • note frontmatter-key unknown frontmatter key "paths"
    • note frontmatter-key unknown frontmatter key "x-ai-rulez"

    Process rating: all ten parameters 70/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 19 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 902 tokens

    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)
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 139: enough signal without eating the budget
    • +4Structure: 5 headings
    • +3Step-by-step instructions: 19 items
    • +3Output format is stated explicitly

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