CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-model-nodejs

Use this skill for Node.js backend AI via @cloudbase/node-sdk (>=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration. The only SDK supporting image generation (ai.createImageModel + generateImage). Text via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*; model ids (e.g. deepseek-v4-flash, glm-5, kimi-k2.6) go in the `model` field of generateText/streamText. MUST run two-step preflight before code — see body. NOT for browser/Web (use ai-model-web) or Mini Program (use ai-model-wechat).

76

Quality

96%

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

The canonical home for this skill is ai-model-nodejs in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-engineered skill body: executable code and exact API contracts, a sequenced preflight with real validation checkpoints and feedback loops, and clean progressive disclosure to two real reference files. The only weakness is moderate redundancy — the createModel-three-values rule and preflight are restated across the STOP, Available Providers, and Best Practices sections.

Suggestions

Collapse the 'createModel accepts exactly three values' guidance into one authoritative location (the STOP section) and have Best Practices #3 and the Available Providers section cross-reference it instead of restating it, to cut ~20-30 lines of repetition.

Trim Best Practices #1 to a one-line pointer ('Run the two-step preflight above before business code') rather than re-narrating the full eligibility + group-readiness sequence already covered in the Preflight section.

Move the per-provider model SKU lists (Hunyuan/DeepSeek/GLM/Kimi/MiniMax enumerations) into references/api-reference.md, keeping only the 'discover at runtime, do not hard-code' rule inline.

DimensionReasoningScore

Conciseness

The body is information-dense with genuinely non-obvious CloudBase contract details Claude would not know (preflight actions, PascalCase params, full-replacement Models), but the 'createModel accepts exactly three values' rule is restated in the STOP table, Available Providers, and Best Practices #3, and the preflight is detailed then re-summarized in Best Practices #1 — minor redundancy that could be trimmed. Not a 5 because the repetition exceeds 'every token earns its place'; not a 3 because the content is specialized, not padded explanations of concepts Claude already knows.

4 / 5

Actionability

Fully executable throughout: exact `npm install`/`tcb.init` code, concrete `ai.createModel('cloudbase')` + `model.generateText({ model: 'deepseek-v4-flash' })` patterns, precise `callCloudApi(service='tcb', action=..., params={...})` signatures, a complete `UpdateAIModel` payload, and numeric timeout ranges — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

The mandatory two-step preflight is a clearly sequenced checklist (Step 0 env id → ① eligibility → ② group readiness) with explicit pass/fail checkpoints, stop conditions ('stop writing code and surface this to the user'), and a feedback loop (DescribeAIModels → if missing → DescribeManagedAIModelList → UpdateAIModel → verify); the destructive full-replacement Models operation is explicitly safeguarded, so the batch/destructive cap does not apply.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview and offloads bulk detail to verified one-level-deep references — [api-reference.md](references/api-reference.md) for generateText/streamText/generateImage examples and types, [custom-onboarding.md](references/custom-onboarding.md) for CreateAIModel onboarding — with a closing Reference index; both referenced files exist, links are well-signaled, and navigation is easy.

5 / 5

Total

19

/

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 exceptionally strong description: it states concrete capabilities, names natural trigger terms, explicitly covers both what and when, and sharply distinguishes itself from sibling skills via explicit routing. The only minor risk is density — the API-mechanics detail (GroupName, model field) edges toward reference content — but everything present earns its place for triggering.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities and entry points — 'image generation (ai.createImageModel + generateImage)', 'Text via ai.createModel', 'run two-step preflight before code' — alongside concrete runtimes (cloud functions, CloudRun, Express/Koa/NestJS), giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both: what ('Node.js backend AI via @cloudbase/node-sdk', image + text generation, preflight) and when ('Use this skill for ... cloud functions, CloudRun, ... scheduled jobs, LLM proxies, agent orchestration'; 'NOT for browser/Web ... or Mini Program').

5 / 5

Trigger Term Quality

Dense with natural phrases users actually say — 'Node.js backend AI', 'cloud functions', 'CloudRun', 'serverless APIs', 'scheduled jobs', 'LLM proxies', 'agent orchestration', 'image generation' — plus framework synonyms and explicit negative triggers (browser/Web, Mini Program).

5 / 5

Distinctiveness Conflict Risk

Niche is sharply scoped to Node.js backend via @cloudbase/node-sdk (>=3.16.0) and explicitly routes conflicts away — 'NOT for browser/Web (use ai-model-web) or Mini Program (use ai-model-wechat)' — 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.

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.