cloud-functions

CloudBase function runtime guide for building, deploying, and debugging your own Event Functions or HTTP Functions. This skill should be used when users need application runtime code on CloudBase, not when they are merely calling CloudBase official platform APIs.

Quality

76%

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-functions/SKILL.md

Quality

Content

73%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 thorough, highly actionable skill body with excellent workflow validation for deployments and well-organized real reference files. Its main weakness is verbosity from duplicated guidance (polling workflow, credentials) repeated across sections.

Suggestions

De-duplicate the MCP image-deployment polling workflow: keep the full version in its dedicated section and reduce the 'Common mistakes' entry to a one-line pointer.

Consolidate the repeated HTTP-function credential guidance into a single canonical statement that points to references/http-function-credentials.md.

Consider moving the extended CLS query-string example catalog into references/operations-and-config.md to slim the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	Mostly assumes Claude's competence (no basic concept explanations) and stays technical, but suffers noticeable redundancy — the MCP image-deployment polling workflow is restated in both the 'Common mistakes' list and its own section, and credential guidance recurs several times.	3 / 5
Actionability	Provides copy-paste-ready executable code skeletons for both Event and HTTP hello-world functions plus concrete MCP action/parameter calls; minor gaps where advanced flows (custom image, credentials, operations) route to reference files rather than being inline.	4 / 5
Workflow Clarity	The deployment-polling workflow has an explicit sequence with validation checkpoints and feedback loops (wait=false, poll getFunctionDeployStatus until succeeded/failed, handle expired via getFunctionDetail, report diagnostics), and the 'How to use this skill' section gives a clear numbered sequence gated by the Change Safety / Deployment Gate protocols.	5 / 5
Progressive Disclosure	Good structure with clear section headers, a reference index, and one-level-deep references that all resolve to real files in references/; however SKILL.md itself is dense and inlines substantial material (gotchas, tool maps, log-query examples) that could arguably live in references.	4 / 5
	Total	16 / 20 Passed

Description

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

A strong, third-person description that clearly defines its niche and gives an explicit use-when clause with a negative boundary. It could be sharpened by adding concrete trigger phrases (function logs, scf_bootstrap, gateway exposure) directly in the description rather than only in the body.

Suggestions

Add concrete trigger phrases to the description (e.g. 'when the user mentions function runtime, function logs, scf_bootstrap, or function gateway exposure') so the 'when' matches the body's activation contract.

Expand the action list slightly (e.g. add 'inspecting' or 'configuring') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('CloudBase function runtime') and several concrete actions ('building, deploying, and debugging') tied to two specific function types, but the actions remain somewhat high-level rather than enumerating a comprehensive set.	4 / 5
Completeness	Explicitly answers both what ('guide for building, deploying, and debugging... Event Functions or HTTP Functions') and when ('This skill should be used when users need application runtime code on CloudBase'), plus a negative boundary, but the 'when' trigger is somewhat abstract rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('Event Functions', 'HTTP Functions', 'CloudBase', 'application runtime code', 'platform APIs') with good coverage, though a few common variations (e.g. 'function logs', 'scf_bootstrap') appear only in the body, not the description.	4 / 5
Distinctiveness Conflict Risk	Clear niche (CloudBase Event/HTTP Functions) with an explicit negative boundary ('not when they are merely calling CloudBase official platform APIs'), giving minimal conflict risk with sibling skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: TencentCloudBase/CloudBase-AI-Toolkit
Path: config/source/skills/cloud-functions/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.