AA dotld
Search domain name availability and registration prices. Use when the user mentions domains, TLDs, domain registration, domain availability, or wants to find, check, or brainstorm domain names. Runs the dotld CLI to query the Dynadot API for real-time pricing and availability.
As a process A 85/100 · Runs to the end — weak spots: progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:27Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/tedstonne/dotld/main/scripts/install.sh | bash
Files scanned: 3. 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 85/100
- 0Progress reporting. Says nothing while it works
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 6 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 879 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (3 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)
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 277: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 6 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.