BF extruct-api
Run explicit Extruct API tasks through the bundled Extruct CLI. Covers Deep Search, semantic search, lookalike search, company and people tables, column operations, enrichment, and contact finding.
As a process F 45/100 · Will not run — References files that are not bundled: scripts/extruct-api
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5828 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/extruct-api
Process rating: all ten parameters 45/100
Will not run. References files that are not bundled: scripts/extruct-api
- 0Tools and files. 1 referenced file(s) missing: scripts/extruct-api
- 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
- 40Consistency. Frontmatter name (extruct-api) differs from the folder (extruct-api-skill)
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 5828 tokens
- 100Steps. 106 steps
- 100Failures and branches. 24 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (12 tags): a typed call is more reliable
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 197: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 106 items
- +4Has examples (36 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.
External checks
ClawHub: suspicious
This Extruct integration is coherent, but should be reviewed because it can change or delete remote Extruct data and collect personal contact details without enough guardrails.
LLM: suspicious (high) · VirusTotal: · 29 May 2026