SKILLEMALL.ai

AC senior-data-engineer

Data engineering skill for building scalable data pipelines, ETL/ELT systems, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, and modern data stack. Includes data modeling, pipeline orchestration, data quality, and DataOps. Use when designing data architectures, building data pipelines, optimizing data workflows, implementing data governance, or troubleshooting data issues.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 10 files body ≈ 1 380 tokens Open the sourcegithub.com analyzed 2 d ago

Data engineering skill for building scalable data pipelines, ETL/ELT systems, and data infrastructure.

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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: 10. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 131): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 56/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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 51 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1380 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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 407: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 51 items
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)
    • +3All 3 scripts are documented

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