SKILLEMALL.ai

AC auth-nodejs-cloudbase

Complete guide for CloudBase Auth using the CloudBase Node SDK – caller identity, user lookup, custom login tickets, and server-side best practices.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 1 file body ≈ 3 689 tokens Open the sourcegithub.com analyzed 20 h ago

Complete guide for CloudBase Auth using the CloudBase Node SDK – caller identity, user lookup, custom login tickets, and server-side best practices.

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

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
53/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

    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

    • note frontmatter-key unknown frontmatter key "alwaysApply"

    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
    • 30Running it twice. 5 mutating operations with no state check
    • 40Consistency. Frontmatter name (auth-nodejs-cloudbase) differs from the folder (auth-nodejs)
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (node) that frontmatter does not declare
    • 85Steps. 87 steps, 1 vague phrases
    • 100When it triggers. States when to use and when not to
    • 100Execution cost. Instruction body is 3689 tokens
    • 100Progress reporting. Reports progress

    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
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 148: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 87 items
    • +4Has examples (9 code blocks)

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