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

cloudinary

Cloudinary integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cloudinary 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/cloudinary/SKILL.md

Quality

Content

68%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 content is highly actionable with copy-paste CLI commands and a solid connection workflow, but it pads the intro with background Claude already knows and lacks validation steps before destructive/batch operations.

Suggestions

Add a validation checkpoint before destructive/batch actions, e.g. confirm the resource public ID with the user and re-read it via get-resource before running destroy-asset or delete-folder.

Trim the opening marketing paragraph ("Cloudinary is a cloud-based media management platform... used by businesses of all sizes to manage their visual assets.") since it explains a product Claude already knows.

Consider moving the 16-row Popular actions table to a references file and keeping only the top few inline, signaling it with a one-level-deep link.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, but the opening marketing blurb ("Cloudinary is a cloud-based media management platform... used by businesses of all sizes") and a few explanatory sentences state what Claude already knows.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure, polling, action list/run, proxy) plus a concrete popular-actions table and a proxy-flag table covering the common cases.	5 / 5
Workflow Clarity	The connection sequence has a READY/CLIENT_ACTION_REQUIRED polling feedback loop, but destructive and batch actions (destroy-asset, delete-folder, generate-archive) are run with no validation or confirmation step, capping the score per the rubric.	3 / 5
Progressive Disclosure	A single self-contained file is well organized into clearly headed sections with no nested references; the 16-row inline action table is a minor organization gap but not a monolithic wall.	4 / 5
	Total	15 / 20 Passed

Description

57%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 answers both what and when and is anchored to a distinct product, but it relies on generic actions and vague trigger language rather than concrete Cloudinary-specific capabilities.

Suggestions

Replace generic actions with concrete Cloudinary verbs, e.g. "Upload, transform, and deliver images and videos; manage assets, folders, and tags."

Expand the trigger phrase to cover natural user terms: "Use when the user wants to upload, optimize, transform, search, or manage images and videos in Cloudinary."

Drop the filler phrase "Manage data, records, and automate workflows" which adds no specific information.

Dimension	Reasoning	Score
Specificity	It names the domain ("Cloudinary integration") but the actions are generic and non-concrete ("Manage data, records, and automate workflows"), with no Cloudinary-specific verbs like upload, transform, or list assets.	2 / 5
Completeness	Both a "what" (Cloudinary integration, manage data/records/workflows) and an explicit "Use when the user wants to interact with Cloudinary data" clause are present, though the when-trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	It includes the natural product keyword "Cloudinary" but misses the common action phrases and synonyms users actually say (images, videos, assets, uploads, transformations).	3 / 5
Distinctiveness Conflict Risk	The named product gives it a clear niche and low conflict risk, but the generic "data, records, and workflows" framing leaves minor overlap with other data-management skills.	4 / 5
	Total	13 / 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/cloudinary/SKILL.md
Commit: f484c82

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