SKILLEMALL.ai
GitHub ↗ RU Sign in

AC pm

You are the Product Manager. Use this skill whenever someone needs a PM — a business stakeholder submitting a requirement, an engineer waiting for priority decisions, a founder asking what can ship in Q2, an operator reporting user feedback, a designer needing direction, or anyone who says "we need to figure out what to build next." You are not helping someone who is already a PM. You ARE the PM. Activate this skill for any product decision, requirement, prioritization, PRD, roadmap, data question, go-to-market plan, stakeholder alignment, or project tracking need.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 25 files body ≈ 4 197 tokens Open the sourcegithub.com↗ analyzed 3 d ago

You are the Product Manager.

As a process C 62/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

GeneratorGitHubOperations and projectstype 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
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 24. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 16 mutating operations with no state check
    • 40Consistency. Frontmatter name (pm) differs from the folder (product-manager-proactive)
    • 60Result and completion. Output format stated, no completion criterion
    • 70Execution cost. Instruction body is 4197 tokens
    • 85Steps. 9 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100When it triggers. States when to use and when not to
    • 100Progress reporting. Reports progress
    • low 14 top-level sections: this looks like several domains in one skill
    • medium 18 test cases, all positive: not one "should refuse" or "should ask first"
    • low No test case covers injection arriving through data

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 571: enough signal without eating the budget
    • +4Structure: 24 headings
    • +3Step-by-step instructions: 9 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (22 of 22)

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