SKILLEMALL.ai

AB data-quality-frameworks

Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 370 tokens Open the sourcegithub.com analyzed 18 h ago

Implement data quality validation with Great Expectations, dbt tests, and data contracts.

As a process B 75/100 · Nearly there — weak spots: result and completion, progress reporting

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
B
75/100
Nearly there
Progress reporting w 2
0
Result and completion w 14
40
When it triggers w 12
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: data-quality-frameworks (sickn33/agentic-awesome-skills)

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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 75/100

    • 0Progress reporting. Says nothing while it works
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 20 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 370 tokens
    • 100Running it twice. No mutating operations
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 194: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 20 items

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