BF ens
Resolve ENS names (.eth) to Ethereum addresses and vice versa. Use when a user provides an .eth name (e.g. "send to vitalik.eth"), when displaying addresses (show ENS names), looking up ENS profiles, or helping users register, renew, or manage .eth names.
As a process F 40/100 · Will not run — References files that are not bundled: ...
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:182High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| ENS Registry | `0x00…e1e` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:183High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| ETH Registrar Controller | `0x25…03b` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:184High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Public Resolver | `0x23…E63` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:185High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Reverse Registrar | `0xa5…7Cb` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:186High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Name Wrapper | `0xD4…401` |
table
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ... - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 40/100
Will not run. References files that are not bundled: ...
- 0Tools and files. 1 referenced file(s) missing: ...
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 40Consistency. Frontmatter name (ens) differs from the folder (ens-skill)
- 100Steps. 61 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Execution cost. Instruction body is 2931 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- +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 255: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 61 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: suspicious
This ENS skill is coherent, but it needs review because it silently sends wallet/name lookups to third parties, stores ENS identity data, and includes an unsafe command example.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026