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.

61

Quality

73%

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

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 well-structured with executable guidance, clear pre-flight checkpoints, and clean one-level progressive disclosure, but it repeats several warnings and analogies that could be tightened for token efficiency.

Suggestions

Consolidate the repeated accessKey/signInAnonymously/getSession warnings into one canonical note instead of restating them in Common mistakes, the parameter map, and the Quick Start comments.

Trim the Supabase analogy to the essential differences, moving the extended comparison into the extended guide.

Add a brief end-to-end runnable sign-in example inline so the body is self-sufficient for the common case.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code, but the accessKey/signInAnonymously/getSession warnings and the Supabase analogy are restated at length across the body (and again in the extended guide), adding avoidable tokens.

3 / 5

Actionability

Provides executable init code plus specific method calls and concrete MCP actions (e.g. queryAppAuth(action="getLoginConfig"), auth.signInWithPassword), with only minor gaps left to the extended guide.

4 / 5

Workflow Clarity

Clear sequencing via "Read before writing code if", "Then also read", and explicit pre-check checkpoints (verify provider On: TRUE, confirm SMTP), with only minor validation gaps.

4 / 5

Progressive Disclosure

The body is an overview that points to a single real one-level-deep reference (references/extended-guide.md) with a clearly signaled reference index, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

75%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 specific and clearly distinct, naming multiple concrete auth capabilities, but it lacks an explicit "Use when..." trigger phrase and misses several natural user-facing keywords, limiting its trigger and completeness scores.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user needs a Web login, registration, session handling, or protected route built with @cloudbase/js-sdk".

Include natural synonyms users actually say ("login", "sign in", "auth", "Web auth") to improve trigger term coverage.

Drop the dependency caveat ("after auth-tool has already been checked") from the description and keep it in the body to avoid diluting the trigger.

DimensionReasoningScore

Specificity

Names the domain plus multiple concrete capabilities ("Web authentication solutions", "multiple login methods", "complete user management", "frontend integration"), giving comprehensive coverage of actions.

5 / 5

Completeness

The "what" is clear, but there is no explicit "Use when..." trigger clause — the "when" ("after auth-tool has already been checked", "for frontend integration") is only weakly implied, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes relevant terms like "Web authentication", "login methods", "user management", and "frontend integration", but omits common natural synonyms such as "login", "sign in", or "auth" that users would actually say.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to CloudBase Web auth with a distinct niche (frontend integration after provider setup), minimizing overlap with mini-program, native, or server-side auth skills.

5 / 5

Total

17

/

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.