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.

67

Quality

81%

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

71%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, executable content with a clear scenario-selection workflow and well-signaled sibling references. The main weaknesses are preamble redundancy that inflates token cost and a monolithic structure that inlines reference-grade material rather than splitting it out.

Suggestions

Collapse the redundant preamble: merge "Activation Contract" and "When to use this skill" into a single Use-when / Do-not-use-for block so the triggering guidance is stated once.

Move the per-scenario tcb.init boilerplate into a shared setup snippet referenced once, instead of repeating it verbatim in all nine scenarios.

Extract the "Node Auth APIs covered" reference and the scenario catalog into a references/ file (e.g. node-auth-apis.md), leaving SKILL.md as a concise overview that links one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient per-example code, but the three overlapping preamble sections ("Activation Contract", "When to use this skill", "How to use this skill") restate the same triggering guidance, and the init boilerplate repeats across nine scenarios.

3 / 5

Actionability

Every scenario is complete, executable TypeScript against @cloudbase/node-sdk with real method calls, parameters, and error handling — copy-paste ready and covering the common cases (identity, lookup, query, IP, custom tickets).

5 / 5

Workflow Clarity

The "How to use this skill" section gives a clear numbered sequence (clarify runtime → confirm env/SDK → pick scenario → follow API shapes → handle uncertainty) and scenarios are organized by responsibility, with only minor gaps.

4 / 5

Progressive Disclosure

Well-organized with clear headers and one-level-deep sibling-skill references, but the ~400-line file inlines the full API reference and nine-scenario catalog that, for a skill this size, could live in separate reference files to keep SKILL.md a leaner overview.

3 / 5

Total

15

/

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, well-scoped description that states concrete capabilities, gives explicit use-when triggers with a clear negative boundary, and is highly distinguishable from sibling CloudBase auth skills. Only minor keyword-synonym breadth keeps trigger quality from a perfect score.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "server-side identity", "user lookup", and "custom login tickets" — giving comprehensive coverage of the skill's scope, matching the multi-action anchor.

5 / 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...") with concrete trigger phrases plus a negative boundary.

5 / 5

Trigger Term Quality

Good natural-term coverage ("Node.js code", "caller identity", "inspect end users", "custom login tickets") that a CloudBase developer would say, but missing some synonyms/common variations, so just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Carves a clear Node server-side-auth niche and explicitly excludes adjacent work ("not when configuring providers or building client login UI"), minimizing conflict 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.