SKILLEMALL.ai

CB start-3-5

Module 3.5: Go Live. Deploys the quiz project to Vercel.

The skillemall take

The skill promises to deploy a quiz project to Vercel—standard course material for PM training. One module file with 2195 tokens of deployment instructions. Checks returned grade C: quality 69, process 71. No critical errors, but mid-level issues present. No model has run the skill, sandbox untested.

Worth installing if you're following the course and need basic Vercel deployment guidance. Skip it if you want a ready-made solution or automation. Grade C suggests the instructions work, just not polished.

carlvellotti/claude-code-pm-course Agent Skills author: carlvellotti 1 file body ≈ 2 195 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Module 3.5: Go Live. Deploys the quiz project to Vercel.

As a process B 71/100 · Nearly there — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGitHubLearningSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
B
71/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
20
Result and completion w 14
40
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 description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 71/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 100Tools and files. No external tools needed
  • 100Steps. 28 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2195 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress

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 56: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 28 items
  • +4Has examples (8 code blocks)

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