AC product-marketing-context
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'service context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'describe my service,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Works for products, services, or hybrid offerings — B2B and B2C. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for offering, audience, and positioning context.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (product-marketing-context) differs from the folder (abm-product-marketing-context)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Failures and branches. 9 branches
- 70Execution cost. Instruction body is 4638 tokens
- 100Steps. 93 steps
- 100When it triggers. States when to use and when not to
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -269 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 665: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 93 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.