CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

65%

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

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.

The body is a well-structured, actionable overview with clean progressive disclosure to a real extended-guide reference, though it loses some conciseness to repeated gotcha cautions and would benefit from a more explicit validate/retry feedback loop.

Suggestions

Consolidate the repeated accessKey/getLoginState/getSession cautions into one canonical location and cross-reference it instead of restating verbatim in the activation contract, parameter map, and quick-start comments.

Add a concrete, runnable signInAnonymously() example (not just commented-out code) for the NoSQL CRUD pre-auth step.

Make the validation feedback loop explicit (e.g., call queryAppAuth/listProviders -> if provider On != TRUE, enable via manageAppAuth -> re-verify before writing sign-in code).

DimensionReasoningScore

Conciseness

The body is mostly efficient and action-oriented, but the 'Common mistakes / gotchas' section repeats the accessKey/getLoginState/getSession cautions nearly verbatim across the activation contract, parameter map, and quick-start comments, adding padding that could be consolidated.

3 / 5

Actionability

It provides a concrete, executable init snippet with import and config fields plus specific MCP action calls (queryAppAuth, manageAppAuth) and method signatures, with only minor gaps (e.g., the signInAnonymously block is commented out rather than a runnable example).

4 / 5

Workflow Clarity

The activation contract gives a clear sequenced flow (check auth-tool first, then return here) with explicit provider-readiness checkpoints before writing code; it lacks a fully explicit validate-then-retry feedback loop, keeping it just below 5.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview that clearly signals a single one-level-deep reference (references/extended-guide.md) which exists and is well-organized, with an explicit reference index — matching the top anchor.

5 / 5

Total

16

/

20

Passed

Description

58%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 clearly names a specific niche and concrete capability areas, but it omits an explicit 'Use when...' trigger clause and lacks natural user-facing trigger synonyms, leaving completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause naming the concrete trigger phrases (e.g., 'Use when building CloudBase Web login, sign-up, session, or protected-route flows with @cloudbase/js-sdk').

Include natural user-facing terms and synonyms such as 'sign in', 'sign-up', 'OTP', 'OAuth', and 'session handling' alongside 'login methods'.

Enumerate the specific login methods (phone OTP, email, username/password, anonymous, OAuth) instead of the generic 'multiple login methods'.

DimensionReasoningScore

Specificity

Names the domain (CloudBase Web Authentication) and several concrete actions — 'multiple login methods' and 'complete user management' — but the actions are slightly generic rather than enumerating specific operations like OTP/password/OAuth.

4 / 5

Completeness

It has a clear 'what' but no explicit 'Use when...' trigger clause — the 'when' is only weakly implied by 'after auth-tool has already been checked', which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Includes relevant terms ('Web authentication', 'login methods', 'user management', 'frontend integration') but lacks the natural variations and concrete synonyms a user would say (e.g., 'sign in', 'sign-up', 'auth', 'session').

3 / 5

Distinctiveness Conflict Risk

The 'CloudBase Web Authentication' niche and 'frontend integration after auth-tool' qualifier make it mostly distinct from sibling skills, with only minor overlap risk against the related auth-tool-cloudbase skill.

4 / 5

Total

14

/

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.