BC people-directory
Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end dates, status. Use for people records.
Promises an employee directory: name, ID, department, job title, grade, manager, employment type, contact and emergency info, access role, hire and end dates, status. Single file, no scripts. Checks show no critical or high-severity bugs, quality at 79%, process at 64%. Security scores perfectly, but process lagged—likely documentation or schema gaps.
Works for basic personnel record handling. Install if you need a template for your own data and don't mind finishing what the process checklist missed.
Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end…
As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 195 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "source_repo"
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 4612 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 38 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 195: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.