AB huawei-cloud-cloudrobo-workspace
Manage CloudRobo workspaces — create, list, show, update, delete workspaces; manage workspace members (add, list, update role, delete); view workspace overview statistics (capacity, used, available, member count); switch active workspace context for use by other cloudrobo skills (dataset, train, eval, infer, etc.). Workspace is the foundational resource container — all other CloudRobo operations require a valid workspace_id. Triggers include: workspace management, workspace member management, workspace switching, workspace overview, workspace configuration, default workspace, 工作空间管理, 工作空间成员, 工作空间切换, 工作空间概览, 工作空间配置, 默认工作空间.
Manage CloudRobo workspaces — create, list, show, update, delete workspaces; manage workspace members (add, list, update role, delete); view workspace…
As a process B 69/100 · Nearly there — weak spots: when it triggers, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4356 tokens
- 85Steps. 65 steps, 2 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (6 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 630: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 65 items
- +3Output format is stated explicitly
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.