SKILLEMALL.ai

BB smb-client-onboarding

Local client onboarding tracker. Store client records, track onboarding steps, and generate reminder text via LLM. Use when user says 'track a new client', 'add client onboarding', 'show onboarding status', or 'onboarding checklist'.

ClawHub Agent Skills author: jzargona v1.0.1 MIT-0 5 files body ≈ 874 tokens Open the sourceclawhub.ai analyzed 25 h ago

Local client onboarding tracker.

As a process B 69/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting

ProcedureStripeSlackWhatsAppTrelloAI and agentsSales and CRMtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
B
69/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    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: 5. 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: Missing closing "quote at line 13, column 43: These integrations are planned for v1.1. ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
    • note frontmatter-key unknown frontmatter key "permissions"
    • note frontmatter-key unknown frontmatter key "privacy"

    Process rating: all ten parameters 69/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 28 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 874 tokens

    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
    • -213 emoji in the instructions: noise for the model
    • -42 reference files, but SKILL.md never points to them: the model will not open them
    • -31 of 1 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 233: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 28 items
    • +4Has examples (6 code blocks)

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

    External checks

    ClawHub: suspicious
    The skill mostly matches its onboarding-tracker purpose, but it sends client contact email data to an external LLM despite only disclosing client name and stuck-step context.
    LLM: suspicious (medium) · VirusTotal: · 2 Jul 2026