BB new-job-first-week-admin-board
Create a first-week new-job admin board for access requests, forms, equipment, meetings, questions, deadlines, blockers, and follow-ups while avoiding passwords, identity numbers, payroll details, and sensitive HR data.
As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "triggerKeywords" - note
frontmatter-keyunknown frontmatter key "language" - note
frontmatter-keyunknown frontmatter key "hasExecutableCode" - note
frontmatter-keyunknown frontmatter key "promptOnly" - note
frontmatter-keyunknown frontmatter key "execution"
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2086 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +2Single-language instructions
- +3Description length 219: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 33 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: clean
This prompt-only skill creates a new-job onboarding checklist and clearly avoids collecting passwords, IDs, payroll, banking, medical, or other sensitive HR data.
LLM: benign (high) · VirusTotal: benign · 13 May 2026