AB relationship-chat-analysis
Use this skill only when the user explicitly provides, uploads, pastes, or identifies specific relationship chat records and asks for evidence-based analysis of those records. It handles long, messy exports from LINE, WhatsApp, Telegram, iMessage, Messenger, Discord, SMS, or similar platforms by cleaning noise, segmenting episodes, and analyzing communication patterns, conflict cycles, emotional bids, repair attempts, avoidance, boundaries, effort balance, intimacy signals, safety concerns, and blind spots. Do not trigger for ordinary relationship advice, short sentiment checks, or broad questions unless the user has intentionally supplied chat data for analysis.
Use this skill only when the user explicitly provides, uploads, pastes, or identifies specific relationship chat records and asks for evidence-based analysis…
As a process B 74/100 · Nearly there — weak spots: failures and branches, 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: 10. 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 74/100
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (relationship-chat-analysis) differs from the folder (relationship-chat-analysis-skill)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1300 tokens
- 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 671: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.