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

64%

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code and concrete gotchas, and it uses progressive disclosure well with a verified one-level reference. Its main weaknesses are repetition that hurts conciseness and an implicit rather than explicit validation workflow.

Suggestions

Consolidate the repeated accessKey/getLoginState warning into one canonical spot and cross-reference it, removing the duplicate prose from the Parameter map and Quick Start.

Add a short numbered implementation workflow (check providers -> init SDK -> wire sign-in -> guard routes with getSession) with an explicit validation checkpoint after each risky step.

Trim the Supabase-compatibility callout to the essential API-shape differences, since Claude already knows supabase-js patterns.

DimensionReasoningScore

Conciseness

The body is dense and mostly assumes Claude's competence, but it repeats the accessKey/getLoginState caveat across the Common mistakes, Parameter map, and Quick Start sections, and the Supabase-compatibility block is somewhat expansive; it could be tightened.

2 / 3

Actionability

Provides fully executable init/auth code plus specific method signatures, exact parameter names ('phone' not 'phone_number'), and concrete MCP actions like queryAppAuth(action="listProviders"), giving copy-paste-ready guidance.

3 / 3

Workflow Clarity

The Activation Contract sequences provider checks before frontend code, but the actual login implementation is not laid out as an explicit numbered sequence with validation checkpoints; validation appears as scattered gotchas rather than a clear validate-fix-retry loop.

2 / 3

Progressive Disclosure

SKILL.md acts as a concise overview that points to a single one-level-deep reference (references/extended-guide.md, verified to exist) with a clear reference index, giving easy navigation.

3 / 3

Total

10

/

12

Passed

Description

57%

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 is specific enough to its niche and unlikely to conflict, but it omits an explicit 'Use when...' trigger and lacks common natural trigger terms a user would say. Tightening the action list and adding a clear trigger clause would raise it.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when building Web login, registration, session, or protected-route flows with @cloudbase/js-sdk') to satisfy the completeness 'when' requirement.

Replace the generic 'complete user management' with concrete actions like 'sign in, sign up, session handling, and protected-route guards'.

Add natural user-facing terms such as 'login page', 'sign in', 'session', and 'auth flow' alongside the existing technical terms.

DimensionReasoningScore

Specificity

Names the domain ('Web authentication') and some actions ('multiple login methods', 'complete user management') but these are not as concrete as listing multiple specific actions, and 'complete user management' leans toward an over-claim.

2 / 3

Completeness

States what it does ('Provides... Web authentication solutions with multiple login methods and complete user management') but lacks an explicit 'Use when...' trigger clause; the 'when' is only implied via 'after auth-tool has already been checked', which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes relevant terms ('Web Authentication', 'login methods', 'frontend integration', 'user management') but omits natural variations a user would actually say such as 'login page', 'sign in', 'auth flow', or 'session'.

2 / 3

Distinctiveness Conflict Risk

The narrow scope ('CloudBase Web Authentication', 'frontend integration', 'after auth-tool has already been checked') carves a clear niche with distinct triggers that is unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

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.