SKILLEMALL.ai
GitHub ↗ RU Sign in

CC pm-skill-creator

Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.

deanpeters/Product-Manager-Skills Claude Code author: deanpeters NOASSERTION 1 file body ≈ 3 944 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Design a new PM skill through guided conversation.

As a process C 50/100 · Has gaps — References files that are not bundled: ../workshop-facilitation/SKILL.md, ../skill-authoring-workflow/SKILL.md, scripts/build-a-skill.sh

ProcedureWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
95
Quality 40%
69
Run on models
none yet
Process rating
C
50/100
Has gaps
References files that are not bundled: ../workshop-facilitation/SKILL.md, ../skill-authoring-workflow/SKILL.md, scripts/build-a-skill.sh
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Dangerous commands cmd-autorun-instruction SKILL.md:298
    Instructs the agent to auto-run a script on every session
    **Fix:** Always run `check-skill-metadata.py` and `check-skill-triggers.py` before considering the skill done. No exceptions.

Files scanned: 1. 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
  • warning missing-ref reference to a missing file: ../skill-authoring-workflow/SKILL.md
  • warning missing-ref reference to a missing file: scripts/build-a-skill.sh
  • warning missing-ref reference to a missing file: scripts/add-a-skill.sh
  • warning missing-ref reference to a missing file: scripts/check-skill-metadata.py
  • warning missing-ref reference to a missing file: scripts/check-skill-triggers.py
  • warning missing-ref reference to a missing file: scripts/test-a-skill.sh
  • warning missing-ref reference to a missing file: scripts/find-a-skill.sh
  • 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 50/100

Will not run. References files that are not bundled: ../workshop-facilitation/SKILL.md, ../skill-authoring-workflow/SKILL.md, scripts/build-a-skill.sh
  • 0Tools and files. 8 referenced file(s) missing: ../workshop-facilitation/SKILL.md, ../skill-authoring-workflow/SKILL.md, scripts/build-a-skill.sh
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 78 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3944 tokens
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (4 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 136: enough signal without eating the budget
  • +4Structure: 29 headings
  • +3Step-by-step instructions: 78 items
  • +4Has examples (0 code blocks)

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