BC performance-management
Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development plan. Use for performance reviews.
The skill promises a performance review register: review type, period, employee and reviewer, KPI, OKR, behaviour scores, overall rating, PIP and promotion flags, development plan. In reality, it's a single file at 3966 tokens with no critical errors—lint is clean, safety at 100. Quality score 79 means the structure is readable but not polished. Process score 66 signals the logic works, though optimization lags.
No model runs, no sandbox tests. This means actual behaviour on Claude or Hermes stays unknown. The skill handles data systematization for reviews, but install it only if you need a register without analysis automation.
Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development…
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 191 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 4092 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 191: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.