Name: cloudcraft
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

cloudcraft

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

Quality

63%

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

65%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, executable membrane commands and a clear connection-state workflow, but it is held back by a redundant actions section, missing validation checkpoints around destructive proxy/action operations, and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Remove the redundant 'Popular actions' section (it restates the 'Searching for actions' command) and tighten or cut the vague 'Cloudcraft Overview' bullet filler.

Add an explicit validation/verification step before destructive proxy requests (e.g. GET-then-confirm before DELETE) and after action runs, and fix the dangling 'Step 2' reference by labeling the workflow steps consistently.

Split the bulkier reference material (full proxy flag table, action-discovery details, client-action state machine) into a references/ file referenced one level deep from SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command-driven sections, but the 'Popular actions' section duplicates the earlier 'Searching for actions' guidance and the 'Cloudcraft Overview' bullet list with 'Use action names and parameters as needed' is vague filler that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready membrane commands across install, auth, connection setup, action discovery, action execution with JSON input, and proxy requests, plus a flags table covering the common cases — fully executable guidance.	5 / 5
Workflow Clarity	There is a sequenced install→auth→connect→poll→act flow with a polling feedback loop for client actions, but destructive operations (proxy DELETE, action runs) lack validation/verification checkpoints, which caps workflow clarity at 3 per the rubric guideline; the dangling 'Step 2' reference also breaks sequencing.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and all content is inlined in a single >50-line SKILL.md with no external file references; section headers provide structure but API-style content (action discovery, proxy flags) that could be split remains inline.	3 / 5
	Total	14 / 20 Passed

Description

62%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 clearly identifies the Cloudcraft niche and includes an explicit 'Use when' trigger, but its action list is generic ('manage data, records, automate workflows') rather than naming concrete capabilities. It is solid but could be sharpened with specific actions and richer trigger synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Cloudcraft capabilities such as 'design AWS/Azure/GCP diagrams, browse resources, and inspect account settings'.

Add natural trigger synonyms and surface terms users actually say, e.g. 'Use when the user wants to design, view, or edit Cloudcraft diagrams or cloud infrastructure plans.'

Mention specific objects (diagrams, resources, AWS accounts, teams, billing) that the skill exposes to boost specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('Cloudcraft integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage data') rather than concrete, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Provides both a 'what' (Cloudcraft integration, manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Cloudcraft data'), though the 'what' is somewhat generic rather than fully concrete.	4 / 5
Trigger Term Quality	Includes the natural trigger phrase 'interact with Cloudcraft data' and the product name, but lacks common variations or synonyms, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	'Cloudcraft' is a specific named product giving it a clear niche with minimal conflict risk, but the generic action terms ('manage data, records') introduce minor overlap risk with adjacent integration skills.	4 / 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
Commit: f484c82

Reviewed: ~12 hours 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.