CtrlK
BlogDocsLog inGet started
Tessl Logo

cloud-claw

Use this umbrella skill when the request spans multiple Cloud Claw user-facing domains, especially launching a new AltClaw or OpenClaw VM and then managing lifecycle, logs, renewal, or dashboard access through the local altllm cloud-claw-* commands in this repository.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./vendored/altlayer/cloud-claw/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A clean, well-structured dispatcher body that routes to focused skills and shared setup material without padding. Its main weakness is actionability: it points at command families rather than giving concrete executable command examples.

Suggestions

Include one or two concrete altllm command examples (e.g. `altllm cloud-claw-deployments list`, `altllm cloud-claw-logs <id>`) instead of only the 'cloud-claw-*' wildcard.

Remove the redundant restatement of the umbrella trigger between the opening line and Rule #2 to tighten the body.

Sharpen the umbrella-vs-focused boundary with a one-line decision rule (e.g. 'if only one domain, use the focused skill; if both deployment and management, use this umbrella').

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence with no concept explanations, but the umbrella-trigger sentence is restated in both the opening line and Rule #2, a minor redundancy that could be trimmed; not quite a 5.

4 / 5

Actionability

Gives concrete routing guidance (skill map, 'prefer altllm cloud-claw-* commands', shared setup files to read) but references commands only via the wildcard 'cloud-claw-*' with no actual executable examples, leaving key details to the referenced files.

3 / 5

Workflow Clarity

Clear sequenced dispatch flow (Shared Setup -> Skill Map selection via 'Use When' -> Rules) for a simple umbrella skill; no validation checkpoint is needed for routing, but the umbrella-vs-focused boundary, though addressed, could be sharper.

4 / 5

Progressive Disclosure

Well-organized overview under 50 lines with clearly signaled one-level-deep references (shared preflight/api-surface files and the real references/skill-map.md), a navigable skill-map table, and no nested reference chains.

5 / 5

Total

16

/

20

Passed

Description

83%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, specific description that clearly answers both what and when for a multi-domain umbrella skill. It is narrowly scoped to the Cloud Claw product, minimizing conflict with unrelated skills while acknowledging its dispatcher role.

DimensionReasoningScore

Specificity

Names several concrete actions ('launching a new AltClaw or OpenClaw VM', 'managing lifecycle, logs, renewal, or dashboard access') with only minor abstraction in 'lifecycle'; not a full 5 because that term is somewhat generic.

4 / 5

Completeness

Explicitly states both what (umbrella skill for multi-domain Cloud Claw workflows: launching VMs plus managing lifecycle/logs/renewal/dashboard) and when ('when the request spans multiple Cloud Claw user-facing domains') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural coverage within the product domain ('Cloud Claw', 'AltClaw', 'OpenClaw', 'VM', 'logs', 'renewal', 'dashboard'); a few generic synonyms are missing, and several terms lean product-jargon rather than universally natural.

4 / 5

Distinctiveness Conflict Risk

A clear niche scoped to Cloud Claw/altllm commands with a trigger condition ('spans multiple domains') that distinguishes the umbrella from focused skills, but inherent overlap with the launch-agent and manage-vm sub-skills keeps it just below 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
internet-court/internet-court-skill
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.