CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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.

The body is highly actionable with copy-paste scenarios and a clear agent workflow, but it carries noticeable redundancy between the activation and usage-trigger sections plus repeated SDK init boilerplate. Consolidating those would materially improve token efficiency without losing guidance.

Suggestions

Merge the "Activation Contract" and "When to use this skill" sections into a single trigger block to remove the duplicated use/exclude guidance.

Extract the repeated `tcb.init({ env })` / `app.auth()` setup into one shared snippet referenced by each scenario instead of repeating it verbatim nine times.

Tighten the "Node auth architecture" narrative, which restates scenario responsibilities that the API list and scenarios already convey.

DimensionReasoningScore

Conciseness

Mostly efficient with no concept-padding, but the "Activation Contract" and "When to use this skill" sections substantially overlap and the `tcb.init`/`app.auth()` boilerplate repeats in nearly every scenario — tightening beyond minor would require de-duplicating these.

3 / 5

Actionability

Nine scenarios each ship complete, copy-paste TypeScript covering the common cases (caller identity, UID lookup, phone/email/custom query, client IP, custom ticket), with documented method signatures — fully executable.

5 / 5

Workflow Clarity

A clear 5-step sequenced workflow (clarify runtime → confirm env/SDK → pick scenario → follow API shapes → consult docs if unsure) with try/catch checkpoints in scenarios; minor validation gaps but no destructive/batch operation cap applies.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep, clearly signaled sibling-skill references in "Then also read"; no bundle files exist, and minor consolidation gaps (overlapping trigger sections) keep it just short of ideal.

4 / 5

Total

16

/

20

Passed

Description

92%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 that crisply states both capabilities and explicit usage triggers, with clear negative guidance to avoid mis-selection. Adding the SDK package name and a few more natural synonyms would push trigger-term quality to fully comprehensive.

Suggestions

Include the package identifier `@cloudbase/node-sdk` and a user-natural phrase like "who is calling" so trigger-term coverage reaches comprehensive.

Optionally name the runtime context ("in CloudBase 云函数 or Node backends") to sharpen the when-clause further.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — "server-side identity, user lookup, and custom login tickets" and "read caller identity, inspect end users, or bridge an existing user system into CloudBase" — giving comprehensive coverage of the skill's actions.

5 / 5

Completeness

Explicitly answers both what ("CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets") and when ("should be used when Node.js code must read caller identity… not when configuring providers or building client login UI") with concrete trigger phrases and exclusions.

5 / 5

Trigger Term Quality

Good coverage of natural terms ("Node.js code", "caller identity", "user lookup", "custom login tickets"), but omits the package name `@cloudbase/node-sdk` and common synonyms a user might say, stopping just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Carves a clear Node server-side identity niche and explicitly excludes adjacent concerns (provider configuration, client login UI), giving minimal conflict risk with sibling skills.

5 / 5

Total

19

/

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.

Validation15 / 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
Reviewed

Table of Contents

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.