SKILLEMALL.ai
RU Sign in

BC product-manager-skills

PM skill for Claude Code, Codex, Cursor, and Windsurf. Diagnoses SaaS metrics, critiques PRDs, plans roadmaps, runs discovery, coaches PM career transitions, and pressure-tests AI product decisions. Six knowledge domains, 12 templates, 30+ frameworks, and an opinionated interaction style that labels assumptions and names tradeoffs.

ClawHub Agent Skills author: Gene Dai v1.3.1 MIT-0 27 files body ≈ 3 539 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

AnalyzerSoftware developmentData and analyticsAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
67
Run on models
none yet
Process rating
C
64/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security README.md:196
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - No privilege escalation

Files scanned: 27. 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")
  • note frontmatter-key unknown frontmatter key "type"

Process rating: all ten parameters 64/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 40Consistency. Frontmatter name (product-manager-skills) differs from the folder (pm-agent)
  • 70When it triggers. States when to use, but not when not to
  • 70Failures and branches. 17 branches
  • 100Tools and files. No external tools needed
  • 100Steps. 42 steps
  • 100Execution cost. Instruction body is 3539 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)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 333: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 42 items

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

External checks

ClawHub: clean
This is a readable Markdown-only product-management skill with no evidence of hidden execution, credential use, persistence, or data exfiltration.
LLM: benign (high) · VirusTotal: · 29 May 2026