SKILLEMALL.ai
GitHub ↗ RU Sign in

BF kanban-guru

Diagnose Kanban flow problems and design board operating models. Load this when your team is struggling with throughput, cycle times are unpredictable, multiple stakeholders compete for the same engineers, or you're wondering if Kanban is right for you. Do not use this skill for unrelated requests; route to the nearest named specialist.

magnus919/agent-skills Agent Skills author: magnus919 MIT 10 files body ≈ 2 344 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Diagnose Kanban flow problems and design board operating models.

As a process F 42/100 · Will not run — References files that are not bundled: ../technical-project-management/SKILL.md

AnalyzerOperations 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
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
F
42/100
Will not run
References files that are not bundled: ../technical-project-management/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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
  • 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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../technical-project-management/SKILL.md

Process rating: all ten parameters 42/100

Will not run. References files that are not bundled: ../technical-project-management/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../technical-project-management/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 9 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2344 tokens
  • 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
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 338: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 25 items
  • +4Reference files are cited in the instructions (7 of 7)

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