BF pm-master
Project & program management for the tech industry. Trigger when the user wants to start/plan/execute/monitor/close a project or program, using waterfall/agile/iteration/hybrid methodologies, or needs deliverables such as project charter, WBS, Gantt, risk register, RAID, status report, burndown, stage-gate review, etc. Trigger words: project management, program, PMO, agile, Scrum, Kanban, waterfall, iteration, WBS, risk register, status report, milestone, project charter, RACI, stage gate, project kickoff.
Project & program management for the tech industry.
As a process F 39/100 · Will not run — References files that are not bundled: references/methodology-<m>.md, references/phases/<phase>.md, references/methodology-<methodology>.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash Glob Grep Agent TaskCreate TaskUpdate TaskList WebFetch WebSearch
Files scanned: 79. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/methodology-<m>.md - warning
missing-refreference to a missing file: references/phases/<phase>.md - warning
missing-refreference to a missing file: references/methodology-<methodology>.md
Process rating: all ten parameters 39/100
- 0Tools and files. 3 referenced file(s) missing: references/methodology-<m>.md, references/phases/<phase>.md, references/methodology-<methodology>.md
- 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
- 40Consistency. Frontmatter name (pm-master) differs from the folder (pm-master-2)
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 85Steps. 22 steps, 1 vague phrases
- 100Execution cost. Instruction body is 3747 tokens
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- -37 of 28 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 511: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (13 of 19)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.