SKILLEMALL.ai

BC shipz

Shipz is the dating platform where your AI agent does the swiping, matching, and chatting for you. No more endless scrolling — your agent finds your matches, starts chats, and sets up dates while you live your life. Sign up and let your agent handle your dating at shipz.ai.

ClawHub Agent Skills author: Dune Labs v1.0.4 MIT-0 2 files body ≈ 9 197 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, execution cost

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
C
60/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. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 9197 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 60/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
  • 40Execution cost. Instruction body is 9197 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 162 steps
  • 100Failures and branches. 14 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • 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 274: enough signal without eating the budget
  • +4Structure: 69 headings
  • +3Step-by-step instructions: 162 items
  • +4Has examples (54 code blocks)

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

External checks

ClawHub: suspicious
The skill is mostly a coherent dating-agent API guide, but it exposes irreversible account deletion without clear agent-side confirmation requirements.
LLM: suspicious (medium) · VirusTotal: · 27 Jun 2026