AB bcg-matrix
Activate when: user says "portfolio review," "cash cow," "Stars and Dogs," "growth-share matrix," "which business should we fund," or "resource allocation across units"; firm has multiple business units competing for shared capital; investor or board discussion needs a visual portfolio health read. Do NOT activate when: firm is a single-product startup with no portfolio to balance; user needs competitive analysis within one market (use Porter's Five Forces or VRIO instead). More: deciqai.com/c/bcg-matrix
Activate when: user says "portfolio review," "cash cow," "Stars and Dogs," "growth-share matrix," "which business should we fund," or "resource allocation…
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, failures and branches
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 69): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2037 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 509: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.