SKILLEMALL.ai

BF erp-integration-analysis

Analyze ERP system integration for construction data flows. Map and optimize data flows between ERP modules

ClawHub Agent Skills author: datadrivenconstruction v2.1.0 4 files body ≈ 6 166 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 34/100 · Will not run — References files that are not bundled: ../data-silo-detection/SKILL.md, ../../Chapter-4.2/etl-pipeline/SKILL.md, ../../Chapter-3.5/interoperability-analyzer/SKILL.md

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
78/100
safety, quality, tests
Safety 60%
100
Quality 40%
46
Run on models
none yet
Process rating
F
34/100
Will not run
References files that are not bundled: ../data-silo-detection/SKILL.md, ../../Chapter-4.2/etl-pipeline/SKILL.md, ../../Chapter-3.5/interoperability-analyzer/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 6166 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../data-silo-detection/SKILL.md
  • warning missing-ref reference to a missing file: ../../Chapter-4.2/etl-pipeline/SKILL.md
  • warning missing-ref reference to a missing file: ../../Chapter-3.5/interoperability-analyzer/SKILL.md
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 34/100

Will not run. References files that are not bundled: ../data-silo-detection/SKILL.md, ../../Chapter-4.2/etl-pipeline/SKILL.md, ../../Chapter-3.5/interoperability-analyzer/SKILL.md
  • 0Tools and files. 3 referenced file(s) missing: ../data-silo-detection/SKILL.md, ../../Chapter-4.2/etl-pipeline/SKILL.md, ../../Chapter-3.5/interoperability-analyzer/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 70Execution cost. Instruction body is 6166 tokens
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 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)
  • +3Description length 107: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (4 code blocks)

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

External checks

ClawHub: suspicious
The skill appears to be a local ERP analysis helper, but it requests network access without a documented need while handling potentially sensitive business data.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026