AB value-chain-analysis
Activate when: user asks 'where does our competitive advantage come from', 'why are our margins lower than competitors', 'which activities create value', 'how is the competitor doing it cheaper', 'cost structure analysis', 'make vs. buy decision', 'which activities should we outsource', or is evaluating an acquisition for synergies or designing competitive strategy. Do NOT activate when: the business is a platform/multisided market (use network effects analysis instead); the question is industry-level rather than firm-level (use Porter's Five Forces instead). More: deciqai.com/c/value-chain-analysis
As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2159 tokens
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 606: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 21 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: 91.