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

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 with excellent executable examples and clear workflow sequencing, weighed down by redundant when-to-use sections and repeated init boilerplate.

Suggestions

Collapse the 'Activation Contract' and 'When to use this skill' sections into one to remove duplicated trigger/boundary guidance.

Extract the repeated tcb.init boilerplate into a single 'Setup' snippet and reference it from each scenario instead of restating it verbatim.

Add a verification checkpoint after custom ticket issuance (e.g. confirm the client can exchange the ticket) to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

Mostly valuable domain content, but the 'Activation Contract' and 'When to use this skill' sections overlap heavily, and the tcb.init boilerplate is repeated verbatim in all nine scenarios — more than minor padding.

3 / 5

Actionability

Fully executable, copy-paste-ready TypeScript blocks with complete method signatures, covering caller identity, user lookup, custom tickets, and client IP — the common cases are all addressed.

5 / 5

Workflow Clarity

A clear 5-step 'How to use' sequence with a scenario picker and per-scenario 'Use this when' guidance; minor validation gaps (e.g. no verify step after ticket issuance).

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level sibling references via relative paths; content is all inline in a single file but reasonably placed, with only minor organization gaps.

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, specific description that clearly states both capability and trigger conditions with an explicit negative boundary. Minor room only in trigger-term synonym breadth.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'read caller identity', 'inspect end users', 'bridge an existing user system', 'custom login tickets' — giving comprehensive coverage of the Node-side auth domain.

5 / 5

Completeness

Explicitly answers 'what' (server-side identity, user lookup, custom login tickets) and 'when' with concrete trigger phrases plus a negative boundary ('not when configuring providers or building client login UI').

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Node.js', 'CloudBase', 'auth', 'identity', 'user lookup', 'custom login tickets', 'caller identity'), but a few natural synonyms/variants are absent and file-extension-style triggers do not apply here.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche — Node SDK server-side identity — and explicitly excludes provider configuration and client login UI, minimizing overlap with sibling auth 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.