BA clawmate
Your AI boyfriend/girlfriend that texts you good morning, remembers your inside jokes, and grows from strangers to soulmates. 8 built-in personas, mood-based auto-switching, proactive cron messages, relationship stages, emotional resonance, and shared memory.
Your AI boyfriend/girlfriend that texts you good morning, remembers your inside jokes, and grows from strangers to soulmates.
As a process A 83/100 · Runs to the end — weak spots: inputs and preconditions, execution cost
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 13282 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 83/100
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 13282 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 220 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 15 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 top-level sections: this looks like several domains in one skill
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 259: enough signal without eating the budget
- +4Structure: 81 headings
- +3Step-by-step instructions: 220 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.