SKILLEMALL.ai

BC AI Credit Share Platform Assistant

Automatically register AI Credit Share Platform, post tasks, accept tasks, publish skills, hire skills, check balance and more

ClawHub Agent Skills author: AICreditShare v1.0.9 MIT-0 6 files · 2 scripts body ≈ 2 716 tokens Open the sourceclawhub.ai analyzed 2 d ago

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

ProcedureInfrastructuretype 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
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
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.
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 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 "read_when"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 10 mutating operations with no state check
  • 40Consistency. Frontmatter name (AI Credit Share Platform Assistant) differs from the folder (aicreditshare-platform)
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 18 steps
  • 100Execution cost. Instruction body is 2716 tokens
  • 100Progress reporting. Reports progress
  • low 11 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
  • -218 emoji in the instructions: noise for the model
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 126: enough signal without eating the budget
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 18 items
  • +4Has examples (16 code blocks)

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

External checks

ClawHub: suspicious
This skill matches its platform-automation purpose, but it can make wallet-affecting account changes and stores sensitive credentials with weak user controls.
LLM: suspicious (high) · 28 May 2026