AB data-generator-programming-and-web
Data Generator - Programming and Web: Generate random data: UUIDs (v1/v4), strings, integers, hex, bytes, passwords, API keys, JWT secrets, colors, emails, IPs, Lorem Ipsum, timestamps. Use when an agent needs data generator programming and web, data generator programming and web, uuid generation, unique identifier creation, uuid v4 random, uuid v1 timestamp, api key, length through AgentPMT-hosted remote tool calls. Discovery terms: data generator programming and web, uuid generation.
Data Generator - Programming and Web: Generate random data: UUIDs (v1/v4), strings, integers, hex, bytes, passwords, API keys, JWT secrets, colors, emails…
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, running it twice
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 · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 87 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3774 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 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 490: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 87 items
- +3Output format is stated explicitly
- +4Has examples (23 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.