cloud-storage-web

Complete guide for CloudBase cloud storage using Web SDK (@cloudbase/js-sdk) - upload, download, temporary URLs, file management, and best practices.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./config/source/skills/cloud-storage-web/SKILL.md

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 content is highly actionable with executable code, complete SQL, and well-sequenced validation feedback loops for storage workflows. Its main weaknesses are repetition of the bucket-existence prerequisite across several sections and the absence of a reference bundle to hold the detailed PG-mode and RLS material.

Suggestions

Consolidate the repeated bucket-existence / pgstore prerequisite into one authoritative section and reference it from the others to reduce token cost.

Move the detailed PG-mode return-shape tables and the RLS SQL into a references/ file (e.g. references/storage-pg.md) and link to it from SKILL.md to improve progressive disclosure.

Reorder so the core workflow (init -> ensure bucket -> configure RLS/security domains -> upload -> resolve URL) appears as one linear sequence before the edge-case digressions.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, actionable domain knowledge Claude would not already know, but the bucket-existence / pgstore / STORAGE_BUCKET_NOT_FOUND message is repeated across the common mistakes, minimal checklist, dedicated prerequisite section, and upload rules, which could be consolidated.	3 / 5
Actionability	Provides fully executable, copy-paste-ready code for upload, getTempFileURL, deleteFile, downloadFile, PG-mode storage calls, complete RLS SQL, and MCP tool invocations with explicit action parameters covering the common cases.	5 / 5
Workflow Clarity	Multi-step recipes (Local dev recipe, Bucket existence prerequisite, Post-bucket RLS) are clearly sequenced with feedback loops (STORAGE_NOT_EXIST -> fix env -> retry; STORAGE_PERMISSION_DENIED -> configure RLS), though the workflows are scattered and somewhat redundant across sections.	4 / 5
Progressive Disclosure	No bundle files exist; detailed PG-mode comparison tables and the full RLS SQL are inlined in SKILL.md rather than split into reference files, though section headers and cross-skill/external doc references are signaled.	3 / 5
	Total	15 / 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 clearly names the domain and several concrete capabilities and is highly distinct, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause naming frontend upload/download scenarios would lift the completeness and trigger-term scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a browser/Web app must upload, download, or manage CloudBase storage objects via @cloudbase/js-sdk.'

Replace the generic 'file management' and 'best practices' with more concrete actions (e.g. 'delete files', 'generate temporary download URLs') to reach comprehensive specificity.

Include natural synonyms users might say (e.g. 'temp URLs', 'signed URLs', 'frontend file upload') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('upload, download, temporary URLs, file management') though 'file management' and 'best practices' are slightly generic, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural keywords users would say are present (CloudBase cloud storage, Web SDK, @cloudbase/js-sdk, upload, download, temporary URLs), but synonyms and common variations are limited.	4 / 5
Distinctiveness Conflict Risk	The CloudBase Web SDK storage niche is specific with distinct triggers (@cloudbase/js-sdk, CloudBase cloud storage) and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/source/skills/cloud-storage-web/SKILL.md
Commit: ef9f182

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.