BC kanban-workflow
Kanban Workflow is a TypeScript skill for a stage-based agentic co-worker that integrates PM platforms via CLI-auth adapters only (no direct HTTP auth). It provides setup + verbs (show/next/start/update/ask/complete/create) around a canonical stage set (backlog/blocked/in-progress/in-review), plus polling/diffing foundations and automation hooks.
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:143High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…QYA+ISs0/2l3T9/kj42…aQT/dfNXWX/ZZCQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:398High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-6+gjmF…uh8+uw3mnrvgs+dSPQ…dZG+D4garKg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:415High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…DUr+vOv8…A8A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:585High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Q8E+t5Jh…rfX+bKrFe+Xp5Y…DAA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:848High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…MTY+V2C7…JBA==",
detector
Files scanned: 34. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1064 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 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
- +4No input/output examples
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 348: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 37 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.