SKILLEMALL.ai

CC wearables_comms

Required for wearable-originated calls and text messages: resolve recipients for new calls and messages, and immediately answer, decline, or cancel calls on the originating wearable instead of silently switching to a paired phone.

asgeirtj/system_prompts_leaks Agent Skills author: asgeirtj CC0-1.0 1 file body ≈ 3 394 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Required for wearable-originated calls and text messages: resolve recipients for new calls and messages, and immediately answer, decline, or cancel calls on…

As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "title"

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 8 mutating operations with no state check
  • 40Consistency. Frontmatter name (wearables_comms) differs from the folder (wearables-comms)
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 7 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 3394 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 230: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (2 code blocks)

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