CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auth-nodejs-cloudbase

CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets. This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system into CloudBase; not when configuring providers or building client login UI.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is auth-nodejs-cloudbase in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content: every scenario is executable copy-paste TypeScript grounded in exact SDK shapes, and the routing/workflow structure is clear for an agent. The main cost is token efficiency — near-duplicate scope sections and repeated init boilerplate inflate the file — and the single-file layout forgoes reference-file splitting despite the body's length.

Suggestions

Collapse the near-duplicate scope guidance in "Activation Contract", "When to use this skill", and "Summary" into a single routing section to remove roughly 60 lines of redundancy.

State the SDK init pattern once (as the canonical shape) and strip the repeated import/init boilerplate from each of the nine scenario code blocks.

Move the scenario catalog or the full API reference into a bundled reference file (e.g. SCENARIOS.md) linked from SKILL.md, keeping the overview and routing in the main file.

DimensionReasoningScore

Conciseness

The scenario and API sections are dense and free of known-concept over-explanation, but scope guidance is triplicated across "Activation Contract", "When to use this skill", and "Summary", and the identical 4-line SDK init boilerplate repeats in all nine scenarios, so roughly a quarter of the file could be trimmed.

3 / 5

Actionability

All nine scenarios provide complete, copy-paste-ready TypeScript with real SDK method calls and parameter shapes (e.g. auth.queryUserInfo({ platform: "PHONE", platformId: "+86 13800000000" })), plus concrete constraints like the customUserId length and allowed-character rules.

5 / 5

Workflow Clarity

The "How to use this skill" section gives a clear five-step agent workflow with explicit scenario routing and a fallback for unlisted APIs ("treat it as suspect and avoid using it"), but there are no explicit validate-then-retry checkpoints, keeping it below the top anchor.

4 / 5

Progressive Disclosure

Sections are well organized with clearly labeled scenario routing and clearly signaled sibling-skill references, but the ~435-line monolithic body keeps the full API list and nine-scenario catalog inline when a reference file split would aid progressive disclosure.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities, gives explicit when-to-use triggers with concrete phrases, and adds negative triggers that sharply delineate it from sibling skills. The only weakness is slightly incomplete keyword coverage (missing the SDK package name and cloud-function phrasing) and omission of the client-IP capability.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("server-side identity, user lookup, and custom login tickets", "read caller identity, inspect end users, or bridge an existing user system"), but omits client-IP retrieval covered by the skill, leaving a minor coverage gap.

4 / 5

Completeness

Explicitly answers both what ("CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets") and when ("This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system") with concrete trigger phrases, matching the top anchor's example pattern.

5 / 5

Trigger Term Quality

Good natural-phrased triggers such as "Node.js code must read caller identity" and "custom login tickets", though it omits terms users would naturally say like the package name "@cloudbase/node-sdk" or cloud-function/云函数 phrasing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Node SDK server-side identity) with explicit negative triggers ("not when configuring providers or building client login UI") that disambiguate it from sibling provider-setup and web-login skills, minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

connectors/cloudbase-intl/skills/references/auth-nodejs-cloudbase/SKILL.md

Revision

78c7128

Reviewed

Table of Contents

DiscoveryImplementationValidation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill