Name: cloud-convert
Rating: 58.4 (1 reviews)
Author: membranedev

cloud-convert

Cloud Convert integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Cloud Convert data.

Quality

67%

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

Quality

Content

67%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 mostly executable and well-sequenced with strong connection-state handling, but it opens with unnecessary explanatory padding and gives no validation guidance for its destructive task/job actions. Trimming the intro and adding a brief caution around delete operations would meaningfully improve it.

Suggestions

Remove or condense the opening "CloudConvert is an online file conversion tool…" paragraph and the obvious Input/Options/Output overview; Claude already knows what a file converter is.

Add a short validation/caution note before the destructive actions (delete-task, delete-job, cancel-task, delete-webhook), e.g. confirm the ID and state before deleting.

Include one complete worked example tying the steps together (connect → create-job → poll task → get-task) with representative parameter values to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ("CloudConvert is an online file conversion tool…") and the Input/Options/Output overview explain concepts Claude already knows, while the bulk of CLI commands and connection flow are efficient.	3 / 5
Actionability	Concrete copy-paste commands are given throughout (login, connection ensure, action list/run, proxy flags), with only minor gaps — no complete end-to-end worked example with real values and placeholders like <actionId> remain.	4 / 5
Workflow Clarity	A clear install→auth→connect→poll-state→search→run sequence with explicit feedback loops on CLIENT_ACTION_REQUIRED, but destructive actions (delete-task, delete-job) are listed without any validation/caution checkpoint.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and a single self-contained file (no bundle files present); the 18-row action table is borderline-long but reasonable to keep inline.	4 / 5
	Total	15 / 20 Passed

Description

67%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 covers both what and when and is anchored by a distinctive brand name, but its trigger phrasing is generic and the listed capabilities feel mismatched to a file-conversion tool. Tightening the "Use when" clause with concrete conversion triggers would lift it.

Suggestions

Replace the generic "Use when the user wants to interact with Cloud Convert data" with concrete conversion triggers, e.g. "Use when the user wants to convert files between formats, import/export files, or manage conversion jobs and tasks."

Drop the CRM-style entity list (Deals, Persons, Organizations, Leads, Projects, Pipelines) and instead list file-conversion actions (convert, import, export, upload, create job/task) that match what Cloud Convert actually does.

Remove the vague "and more" filler to keep the description concise and specific.

Dimension	Reasoning	Score
Specificity	Names multiple concrete entities ("Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more") but the single generic verb "Manage" and the filler "and more" leave minor gaps versus comprehensive concrete actions.	4 / 5
Completeness	Both "what" (Cloud Convert integration, manage the listed entities) and "when" ("Use when the user wants to interact with Cloud Convert data") are present, but the trigger clause is generic rather than concrete.	4 / 5
Trigger Term Quality	Only the brand keyword "Cloud Convert" and "data" appear; natural action phrases users would say ("convert files", "file conversion", "format") are missing, so coverage lacks common variations.	3 / 5
Distinctiveness Conflict Risk	The named brand "Cloud Convert" gives a clear niche, though the CRM-style entities listed (Deals, Persons, Pipelines) create minor overlap risk with CRM skills.	4 / 5
	Total	15 / 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/cloud-convert/SKILL.md
Commit: f484c82

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