CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auth-web-cloudbase

CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./config/.claude/skills/auth-web-cloudbase/SKILL.md

The canonical home for this skill is auth-web-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 complete executable v3 API code and strong provider-readiness validation gates, and it uses progressive disclosure correctly with one well-signaled reference file. Its main weakness is redundancy — several critical warnings are restated three to four times across sections, inflating token cost without adding guidance.

Suggestions

State each gotcha once in a canonical location (e.g. the Common mistakes section) and reference it elsewhere, cutting the repeated getSession()/getLoginState(), accessKey-vs-session, and data.verifyOtp warnings from 3-4 occurrences to 1.

Present the implementation flow as one ordered sequence (check providers → resolve env + publishable key → init SDK → implement flows → run Completion Bar) instead of distributing it across Activation Contract, Prerequisites, and Parameter map.

Move the longest Common mistakes bullets (e.g. the multi-paragraph accessKey/session and OTP-closure explanations) into references/extended-guide.md, keeping one-line summaries inline.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious CloudBase-specific gotchas rather than concepts Claude already knows, but the same warnings repeat 3-4 times (getSession() vs getLoginState(), accessKey alone not being a session, the data.verifyOtp callback form, anonymous-login caveats), which could be consolidated.

3 / 5

Actionability

The cookbook provides copy-paste-ready executable code for every common flow (signInWithPassword, signUp + data.verifyOtp, signInWithOtp, resetPasswordForEmail, getSession, onAuthStateChange, signOut, auth gate) plus exact MCP calls like queryAppAuth(action="listProviders") with expected results.

5 / 5

Workflow Clarity

Pre-code verification gates (confirm provider enabled, retrieve publishable key, resolve env ID) and a Completion Bar checklist provide explicit checkpoints, but the sequence is scattered across Activation Contract, Prerequisites, Parameter map, and Cookbook sections rather than one ordered flow.

4 / 5

Progressive Disclosure

The single one-level-deep reference (references/extended-guide.md, verified to exist) is clearly signaled in both the Extended guide section and a Reference index, and detailed login-method examples are appropriately split out; however, the very long inline Common mistakes bullets overlap content with the reference file and could be partly moved.

4 / 5

Total

16

/

20

Passed

Description

53%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.

The description identifies a clear niche and explicitly sequences itself after the sibling auth-tool skill, but it lacks an explicit "Use when..." trigger clause and natural user-facing trigger synonyms. Capabilities are described at category level rather than with concrete named methods.

Suggestions

Add an explicit trigger clause, e.g. "Use when building Web login, registration, session, or protected-route flows with @cloudbase/js-sdk".

Replace "Provides concise and practical Web authentication solutions" with concrete named capabilities such as "password sign-in, email/phone OTP, OAuth sign-in, session management, and route guards".

Include natural synonyms users would say ("sign in", "sign up", "register", "session check") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and a few action areas ("frontend integration", "multiple login methods", "complete user management") but phrases like "Provides concise and practical Web authentication solutions" stay generic rather than listing concrete login methods, matching the 1-2-concrete-actions anchor.

3 / 5

Completeness

The "what" is clear (Web authentication solutions with login methods and user management), but the only "when" is the sequencing condition "after auth-tool has already been checked" — there is no explicit "Use when..." trigger clause, which caps completeness at 3.

3 / 5

Trigger Term Quality

"CloudBase", "Web authentication", and "login methods" are relevant keywords, but common natural phrases users would say ("sign in", "sign up", "registration", "session") are missing, matching the some-keywords-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

"CloudBase Web Authentication" carves a clear niche and the "after auth-tool has already been checked" clause explicitly disambiguates from the sibling provider-setup skill; only minor overlap risk with that closely related sibling remains.

4 / 5

Total

13

/

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

config/.claude/skills/auth-web-cloudbase/SKILL.md

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.