AC filed
Search and retrieve US business entity data (LLCs, corporations, partnerships) from official Secretary of State records via the Filed.dev API. Use when looking up a business, verifying a company exists, finding registered agents, checking entity status, searching by officer name, or doing business due diligence. Covers FL, NY, PA, CT, CO, OR, IA, AK (1.9M+ entities). Triggers on business lookup, company search, entity verification, KYB, registered agent lookup, or "is this company real."
As a process C 53/100 · Has gaps — weak spots: steps, inputs and preconditions, failures and branches
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-usescripts/filed.sh:68Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)[[ -z "$API_KEY" ]] && die "No API key. Set FILED_API_KEY or use --api-key. Get one free at https://filed.dev/register"
vendor-hostquoted
Files scanned: 4. 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 53/100
- 0Steps. Prose only: no discrete steps
- 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
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 407 tokens
- 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)
- +3No numbered steps or checklist
- +1No license
- +2Single-language instructions
- +3Description length 492: enough signal without eating the budget
- +4Structure: 7 headings
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.