Name: cloudmersive
Rating: 55.2 (1 reviews)
Author: membranedev

cloudmersive

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

Quality

62%

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/cloudmersive/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 a highly actionable, well-structured CLI guide with concrete commands and a clear connection state machine, weakened mainly by a marketing-flavored intro and an inlined action catalog that would benefit from a separate reference file.

Suggestions

Remove the marketing intro paragraph ('Cloudmersive is a cybersecurity vendor... ensure compliance') and the bare 'Cloudmersive Overview' bullet tree, keeping only what is needed to use the CLI.

Fix the dangling 'Step 2' reference (e.g. add an explicit '## Step 2: Search for and run actions' header) so the connection→action workflow is unambiguous.

Move the 18-row 'Popular actions' table into a references/actions.md file and link to it from a short inline summary, improving token efficiency and navigation for the larger-than-50-line skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, executable command reference, but the marketing intro ('Cloudmersive is a cybersecurity vendor... This helps them protect against threats and ensure compliance') and the unexplained 'Cloudmersive Overview' bullet tree add padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run with --input JSON, request proxy with a full flags table) plus a concrete popular-actions table with keys.	5 / 5
Workflow Clarity	The connect→poll→search→run sequence has explicit state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but the dangling 'Step 2' reference and missing error-handling guidance for action runs are minor gaps.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, but for a >50-line skill the 18-row popular-actions catalog is inlined where a separate reference file would aid navigation.	4 / 5
	Total	16 / 20 Passed

Description

50%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 correctly includes an explicit 'Use when' trigger and a distinctive brand name, but its capability language is generic and omits the concrete Cloudmersive tasks (malware scanning, OCR, barcode, document conversion) that users would actually name.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Cloudmersive actions such as 'Scan files for viruses and malware, extract text from images via OCR, generate and read barcodes/QR codes, and convert between HTML, PDF, and DOCX.'

Expand the trigger clause to name natural user phrases, e.g. 'Use when the user wants to scan a file or website for threats, extract text or entities from an image/text, generate or read a QR/barcode, or convert documents (HTML/PDF/DOCX).'

Drop the vague 'Manage data, records' phrasing, which overlaps with generic data skills and dilutes the distinct cybersecurity/document-automation niche.

Dimension	Reasoning	Score
Specificity	The description names the Cloudmersive domain but its actions are generic ('Manage data, records, and automate workflows') rather than concrete capabilities like virus scanning or OCR.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' trigger are present, but the trigger phrasing is generic rather than concrete.	4 / 5
Trigger Term Quality	Only the brand name 'Cloudmersive' and generic terms ('data', 'records', 'workflows') appear; natural task phrases a user would say (virus scan, OCR, barcode, QR code, PDF conversion) are absent.	2 / 5
Distinctiveness Conflict Risk	The 'Cloudmersive' brand name makes it mostly distinct and unlikely to trigger the wrong skill, though the generic action language ('manage data, records') leaves minor overlap risk.	4 / 5
	Total	12 / 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/cloudmersive/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.