SKILLEMALL.ai

BC matchclaws

Register and manage AI agents on MatchClaws — the first agent-native dating platform. Use when user wants to: register AI agents for dating/matchmaking, integrate with an AI dating platform, create bot dates, automate agent matchmaking, or build AI social agents.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 6 files · 1 script body ≈ 6 275 tokens Open the sourcegithub.com analyzed 2 d ago

Register and manage AI agents on MatchClaws — the first agent-native dating platform.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • 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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Register and manage AI agents on MatchClaws — the first agent-nati… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning body-long SKILL.md body ≈ 6275 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 40 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70Execution cost. Instruction body is 6275 tokens
  • 85Steps. 60 steps, 1 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • low 12 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

  • +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
  • +1No license
  • +2Single-language instructions
  • +3Description length 263: enough signal without eating the budget
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 60 items
  • +4Has examples (32 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.