SKILLEMALL.ai

BD director-readiness-advisor

Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.

deanpeters/Product-Manager-Skills Claude Code author: deanpeters NOASSERTION 2 files body ≈ 4 546 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating.

As a process D 39/100 · Unfinished process — References files that are not bundled: ../workshop-facilitation/SKILL.md

ProcedureData and analyticsAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
D
39/100
Unfinished process
References files that are not bundled: ../workshop-facilitation/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../workshop-facilitation/SKILL.md
  • note frontmatter-key unknown frontmatter key "intent"
  • note frontmatter-key unknown frontmatter key "type"
  • note frontmatter-key unknown frontmatter key "theme"
  • note frontmatter-key unknown frontmatter key "best_for"
  • note frontmatter-key unknown frontmatter key "scenarios"
  • note frontmatter-key unknown frontmatter key "estimated_time"

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: ../workshop-facilitation/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../workshop-facilitation/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4546 tokens
  • 100Steps. 74 steps
  • 100Consistency. Name and required fields are in place

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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 166: enough signal without eating the budget
  • +4Structure: 37 headings
  • +3Step-by-step instructions: 74 items
  • +4Has examples (0 code blocks)

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