SKILLEMALL.ai

BC Offer Letter Generator

Create formal employment offer letters with compensation and terms

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 575 tokens Open the sourcegithub.com analyzed 2 d ago

Create formal employment offer letters with compensation and terms

As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

GeneratorWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
C
61/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "models"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 61/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (Offer Letter Generator) differs from the folder (offer-letter)
  • 50When it triggers. No condition that starts the skill
  • 85Steps. 34 steps, 2 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Result and completion. Output format and completion criterion are stated
  • 100Execution cost. Instruction body is 1575 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)
  • +3Description length 66: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 34 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.