SKILLEMALL.ai
GitHub ↗ RU Sign in

BC pm-prioritize

Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do NOT auto-trigger. Triggers on "/pm-prioritize", "/prioritize", "приоритизация", "ранжируй бэклог", "RICE-анализ", "prioritize requirements", "RICE", "ICE", "MoSCoW", "Kano", "rank backlog".

serejaris/personal-corp-os Agent Skills author: serejaris MIT 3 files body ≈ 2 191 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Built-in decision tree picks the right framework based on data availability and decision context.

As a process C 57/100 · Has gaps — References files that are not bundled: ../weekly-planning/, ../weekly-retro/

AnalyzerGitHubOperations and projectstype 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
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
57/100
Has gaps
References files that are not bundled: ../weekly-planning/, ../weekly-retro/
Tools and files w 18
0
Result and completion w 14
0
Running it twice w 4
30
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../weekly-planning/
  • warning missing-ref reference to a missing file: ../weekly-retro/

Process rating: all ten parameters 57/100

Will not run. References files that are not bundled: ../weekly-planning/, ../weekly-retro/
  • 0Tools and files. 2 referenced file(s) missing: ../weekly-planning/, ../weekly-retro/
  • 0Result and completion. Does not say what the result is
  • 30Running it twice. 2 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 29 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2191 tokens
  • 100Progress reporting. Reports progress
  • low 11 top-level sections: this looks like several domains in one skill

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

  • +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
  • +5Description quotes 8 example trigger phrases
  • +3Description length 506: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 29 items
  • +4Has examples (2 code blocks)

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