AC product-business
Comprehensive Product & Business skill covering product management, business analysis, marketing, sales, customer support, legal advisory, and technical support. Triggers when users ask about product strategy, business analysis, marketing content, sales automation, customer support, or legal documentation. Use PROACTIVELY for product planning, business metrics, marketing campaigns, sales sequences, support responses, legal documents, or industry research.
Comprehensive Product & Business skill covering product management, business analysis, marketing, sales, customer support, legal advisory, and technical…
As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 17111 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 10Execution cost. Instruction body is 17111 tokens: crowds the task out of the window
- 30Running it twice. 13 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 85Steps. 247 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 459: enough signal without eating the budget
- +4Structure: 78 headings
- +3Step-by-step instructions: 247 items
- +4Has examples (40 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.