Tessl • The management layer for AI agent skills

SkillPublic

cloudcraft

Cloudcraft integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cloudcraft data.

Quality

73%

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

Quality

Content

75%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 concrete CLI commands and an explicit connection-state handling loop, and it is well structured for a single-file skill. Its weaknesses are mild padding in the overview sections and broken step references (a "1b" heading with no "1a" and mentions of a "Step 2" that doesn't exist) that slightly undermine workflow navigation.

Suggestions

Fix the step numbering: rename "1b. Wait for the connection to be ready" to fit a coherent sequence and either define or remove the two references to "Step 2".

Trim filler content: drop "It's used by cloud architects, DevOps engineers, and IT professionals" and "Use action names and parameters as needed", and merge the "Popular actions" section into "Searching for actions" to remove the duplicated command.

Give the Cloudcraft Overview entity tree a purpose — e.g. note which entities map to common action intents, or remove it if the action discovery flow makes it redundant.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven text, but includes unnecessary padding: "It's used by cloud architects, DevOps engineers, and IT professionals", the entity tree followed by filler ("Use action names and parameters as needed"), and a "Popular actions" section that duplicates the search command already shown. This matches "mostly efficient but includes some unnecessary explanation or could be tightened"; it is below level 4 because several passages are trimmable.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases: CLI install (npm install -g @membranehq/cli@latest), login including headless completion (membrane login complete <code>), connection ensure with a concrete URL, action list/run with JSON input, and proxy requests with a complete flag table. This matches the level-5 anchor.	5 / 5
Workflow Clarity	The sequence (install → authenticate → connect → poll state → discover actions → run → proxy fallback) is clear, with explicit state-machine checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR/SETUP_FAILED) and re-poll feedback loops after user actions. It falls short of level 5 due to broken navigation: a "1b" subsection with no "1a", and two references to a nonexistent "Step 2".	4 / 5
Progressive Disclosure	The skill is a single well-sectioned file (~160 lines) with no bundle files, appropriate headers, and one-level-deep structure; nothing is deeply nested or buried. Minor organization gaps (the misnumbered "1b" heading and the duplicated command section) keep it at level 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

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

The description has an explicit "Use when..." clause and a distinct niche via the Cloudcraft brand name, but the capability statement is generic. "Manage data, records, and automate workflows" could describe nearly any integration and omits Cloudcraft's actual value (diagramming and planning AWS, Azure, and GCP environments).

Suggestions

Replace the generic capability list with concrete Cloudcraft actions, e.g. "Design and plan AWS, Azure, and Google Cloud architectures, create and update diagrams and blueprints, and inspect cloud resources."

Broaden the trigger clause to include natural synonyms: "Use when the user mentions Cloudcraft, cloud architecture or infrastructure diagrams, AWS/Azure/GCP blueprints, or wants to visualize their cloud environment."

Mention what the skill actually operates on (diagrams, blueprints, AWS accounts, teams, billing) so the "what" is specific rather than filler.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Cloudcraft domain but the actions are generic boilerplate rather than concrete capabilities like designing AWS/Azure/GCP diagrams or blueprints. This matches the anchor 'Names the domain but actions are minimal or generic' and falls short of level 3 because no concrete action is actually listed.	2 / 5
Completeness	Both parts are present: a "what" ("Cloudcraft integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Cloudcraft data"). This matches level 4 rather than 5 because the "when" is narrow (omits diagram/design/blueprint triggers) and the "what" is vague; it is clearly above level 3 since the "when" is explicitly stated.	4 / 5
Trigger Term Quality	The only natural trigger terms are "Cloudcraft" and "Cloudcraft data", which will catch users naming the product but miss common phrasings like "AWS diagram", "cloud architecture", or "blueprint". Some relevant keywords exist but common variations and synonyms are missing, matching the level-3 anchor.	3 / 5
Distinctiveness Conflict Risk	"Cloudcraft integration" carves out a clear niche via the product name, with "interact with Cloudcraft data" providing a distinct trigger. Minimal conflict risk with other skills, matching the level-5 anchor.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/cloudcraft/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

cloudcraft

Table of Contents

Is this your skill?