AB eonik-mcp-companion
Use eonik with Claude: brand notes, competitor research archive, own-ad facts, ad breakdowns, memory, and receipt-bound briefs. Agents read and draft; they never spend. You approve every cut. Activates when eonik tools are connected or the user asks about their ads, competitors, brand, or what to make next.
Use eonik with Claude: brand notes, competitor research archive, own-ad facts, ad breakdowns, memory, and receipt-bound briefs.
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, consistency, 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 12): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (eonik-mcp-companion) differs from the folder (eonik)
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Execution cost. Instruction body is 745 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)
- +4No input/output examples
- +2Single-language instructions
- +3Description length 308: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 9 items
- +3Output format is stated explicitly
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.