AC agentic-osint-contact-base
Method for a verified B2B contact base — registry mapping, per-field proof, no guessed emails, GDPR. Use when building a lead list, finding a work email, or enriching contacts. Trigger on "build a lead list", "find their email", "enrich these contacts", "is this GDPR compliant".
Method for a verified B2B contact base — registry mapping, per-field proof, no guessed emails, GDPR.
As a process C 52/100 · Has gaps — weak spots: steps, inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5266 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 52/100
- 0Steps. Prose only: no discrete steps
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 20 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5266 tokens
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 279: enough signal without eating the budget
- +4Structure: 18 headings
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.