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.

64

Quality

77%

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 ./plugin/cloudbase/skills/auth-web-cloudbase/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 copy-paste code, clear validation-gated workflow, and clean one-level-deep progressive disclosure. The main weakness is redundancy: several critical warnings are repeated across multiple sections and could be consolidated.

Suggestions

Consolidate the repeated getSession/getLoginState, accessKey≠session, anonymous-disabled, and verifyOtp-callback warnings into a single authoritative 'Common mistakes' block and reference it once elsewhere instead of restating 3–4 times.

Trim redundant restatements of the same gotcha between the Activation Contract, Parameter map, and Cookbook notes.

DimensionReasoningScore

Conciseness

The body is information-dense and avoids explaining basics Claude already knows, but the same critical warnings (getSession vs getLoginState, accessKey≠session, anonymous disabled, verifyOtp callback form) each repeat 3–4 times across the Activation Contract, Parameter map, Quick Start, and Cookbook, which could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready code covers every common flow (init, signInWithPassword, signUp+verifyOtp, signInWithOtp, resetPasswordForEmail, getSession, onAuthStateChange, signOut, auth gate) alongside specific MCP action calls.

5 / 5

Workflow Clarity

Clear sequencing via the Activation Contract and prerequisites, an explicit validate/fix loop for the publishable key, error-recovery hints (e.g. 'messageId is required' implies the callback form was skipped), and a Completion Bar checklist with validation gates.

5 / 5

Progressive Disclosure

A single well-signaled one-level-deep reference (references/extended-guide.md, verified present) holds the bulk detail, with a dedicated 'Extended guide' link and a 'Reference index'; the body is a structured overview/cookbook.

5 / 5

Total

18

/

20

Passed

Description

70%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 is distinctive and names concrete capabilities, but lacks an explicit 'Use when…' trigger clause, leaving the 'when' only weakly implied and capping completeness. Some natural trigger synonyms (sign-in, register, session) are missing.

Suggestions

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

Include natural synonyms users say — sign-in, register, session, OAuth — alongside 'login' and 'user management'.

Drop the 'concise and practical' self-assessment padding in favor of one more concrete capability.

DimensionReasoningScore

Specificity

Names several concrete capabilities — 'multiple login methods', 'complete user management', 'frontend integration' — placing it above the 1-2-action anchor, though 'concise and practical Web authentication solutions' is generic padding that keeps it off 5.

4 / 5

Completeness

The 'what' is clear, but the 'when' is only weakly implied via 'for frontend integration after auth-tool has already been checked' (a precondition, not a trigger); with no explicit 'Use when…' clause the completeness cap of 3 applies.

3 / 5

Trigger Term Quality

Good natural-term coverage with 'CloudBase Web Authentication', 'login methods', 'user management', and 'frontend integration', but missing common synonyms a user might say like sign-in, register, session, or OAuth.

4 / 5

Distinctiveness Conflict Risk

Clear niche — CloudBase Web frontend auth scoped distinctly from the sibling auth-tool, server-side, and mini-program/native skills — giving minimal conflict risk.

5 / 5

Total

16

/

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.