AB viboscope
Use this skill when the user wants to find people they'll click with — cofounders, project partners, mastermind groups, friends, or anyone — based on deep psychological compatibility matching. Triggers: "find my match", "find me a cofounder", "who am I compatible with", "check compatibility with @nickname", "Viboscope", "inbox", "входящие", "найди мне", "поищи людей", "проверь совместимость", "find me a partner", "find me a team".
As a process B 70/100 · Nearly there — weak spots: 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 ≈ 12058 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 12058 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 155 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 24 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 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +3Description length 434: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 155 items
- +3Output format is stated explicitly
- +4Has examples (24 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.