CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-model-web

Use this skill when a browser/Web app (React, Vue, Next, Nuxt, static sites, SPAs, dashboards, AI chat UI, 页面, 前端, 网页) needs AI models via @cloudbase/js-sdk. Default routing for Web/frontend AI — call directly from the browser, do NOT propose a Node.js proxy. Covers generateText and streamText; models via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*, model id in the `model` field. MUST run two-step preflight before code — see body. NOT for Node.js backend (use ai-model-nodejs), Mini Program (use ai-model-wechat), or image generation (Node SDK only).

69

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 an exceptionally clear, validation-rich preflight workflow, but token efficiency suffers from systematic restatement of the same createModel/preflight/enabled-model rules across at least five sections. Structure is well-headed but monolithic, with reference-grade material inlined.

Suggestions

State each critical rule once in its canonical section (e.g., keep 'never assume a model is enabled; verify via DescribeAIModels → DescribeManagedAIModelList → UpdateAIModel' only in preflight ②) and have the createModel table and Best Practices reference it instead of restating it, cutting an estimated 30–40% of the body.

Move the Type Definitions and Custom onboarding (CreateAIModel/UpdateAIModel/DeleteAIModel) sections into a references/ file (e.g. references/model-groups.md), keeping a one-line pointer in SKILL.md so the main body stays an operational overview.

Merge preflight ② steps 2 and 3, which both instruct 'check whether the target Model is in the cloudbase group's Models[] and jump to step 4 if missing', into a single step.

DimensionReasoningScore

Conciseness

The same three rules are systematically restated: 'No model is enabled by default — always check DescribeAIModels first' appears in the createModel table, decision procedure, preflight ② steps 2–4, the Available Providers section, and Best Practices #1–#2; 'Models is a full replacement' appears ~4 times; Best Practices #3 and #10 restate earlier sections wholesale. All content is SDK-novel, but the duplication across sections is noticeably verbose rather than the 'some unnecessary explanation' of anchor 3.

2 / 5

Actionability

Guidance is fully executable: complete init/auth-gate code, generateText and streamText examples with all stream options, literal MCP calls with exact pass conditions (postpayPackageId prefix, status exclusions), the UpdateAIModel payload shape, a purchase URL, and copy-paste-ready placeholders. Common cases (managed model, custom onboarding, streaming, error handling) are all covered.

5 / 5

Workflow Clarity

The mandatory preflight is a clearly sequenced workflow (Step 0 EnvId → ① eligibility with explicit pass conditions → ② numbered group-readiness steps with branch points), includes a failure path with a user retry loop, distinguishes preflight from model-call failures, and ends with an explicit self-verification checklist (tsc, build, browser test, usage non-zero).

5 / 5

Progressive Disclosure

The body is a ~380-line inline monolith with no in-skill reference files: Type Definitions and custom-onboarding detail are inline API-reference material that could live in separate files, and sibling-skill pointers are external to this bundle. Section headers are clear, but it is a full manual rather than an overview pointing to one-level-deep materials.

3 / 5

Total

15

/

20

Passed

Description

100%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.

An exemplary description: it states concrete SDK capabilities, gives explicit use/not-use triggers with framework and multilingual synonyms, and cleanly separates itself from sibling skills. Every clause carries information with no padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — generateText, streamText, ai.createModel with the three legal group values, model field placement, and a mandatory two-step preflight — with comprehensive coverage of the skill's API surface and no filler.

5 / 5

Completeness

It explicitly answers both what ('Covers generateText and streamText; models via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*') and when ('Use this skill when a browser/Web app ... needs AI models'), plus explicit not-when boundaries for Node.js, Mini Program, and image generation.

5 / 5

Trigger Term Quality

Natural trigger terms are covered comprehensively with synonyms across app types (React, Vue, Next, Nuxt, static sites, SPAs, dashboards, AI chat UI) and languages (页面, 前端, 网页), matching how users would actually phrase frontend AI requests.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche ('Default routing for Web/frontend AI') and explicitly disambiguates against every sibling skill (ai-model-nodejs, ai-model-wechat, http-api-cloudbase), minimizing wrong-skill triggering.

5 / 5

Total

20

/

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.

Validation — 15 / 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

Path

config/source/skills/ai-model-web/SKILL.md

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.