Name: uploadcare
Rating: 59.2 (1 reviews)
Author: membranedev

uploadcare

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

Quality

68%

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/uploadcare/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 executable commands covering the full Membrane workflow (install, auth, connection, action discovery/execution, proxy) and a well-structured connection-polling flow. Its weaknesses are mild verbosity in the introduction, a dangling 'Step 2' reference, and a skeletal overview section.

Suggestions

Trim rhetorical padding such as 'so you can focus on the integration logic rather than auth plumbing' and the generic introductory description of what Uploadcare is.

Define or relabel the undefined 'Step 2' (e.g. rename the 'Searching for actions' section to 'Step 2: Search for actions') so the workflow sequence has no dangling references.

Flesh out the 'Uploadcare Overview' bullets (Files, Groups, Projects, Webhooks) with one-line action hints, or remove the placeholder 'Use action names and parameters as needed' directive.

Dimension	Reasoning	Score
Conciseness	The command reference and proxy-options table are lean, but padded sentences like 'so you can focus on the integration logic rather than auth plumbing' and the introductory product description add unnecessary explanation, fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides copy-paste-ready, executable commands for every common case (install, login, connection ensure, action search/run, proxy request) plus a complete flag table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with a polling feedback loop and explicit state branches (READY / CLIENT_ACTION_REQUIRED / error), but the referenced 'Step 2' is never defined and action runs lack a final verification step, fitting 'clear sequence with minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist; the single-file body is organized into clear sections with navigable sub-sections, but the 'Uploadcare Overview' is skeletal and a couple directives are vague, fitting 'good structure with minor organization gaps' rather than a clean 5.	4 / 5
	Total	16 / 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 answers both 'what' and 'when' and is anchored to a distinct product name, but its action verbs ('manage data, records') are generic and it lacks concrete trigger synonyms a user would naturally say. It is competent but could be sharpened with more specific capabilities and richer natural-language triggers.

Suggestions

Replace generic verbs with Uploadcare-specific concrete actions (e.g. 'Upload, store, transform, and deliver files; manage file groups and webhooks').

Expand the 'Use when...' clause with natural user phrasings and file/feature synonyms (e.g. 'Use when the user wants to upload files, optimize images, or manage Uploadcare files and groups').

Mention concrete artifacts like file uploads, image transformations, or CDN delivery to reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the Uploadcare domain and a few actions ('Manage data, records, and automate workflows'), but 'data' and 'records' are generic, fitting the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	States both the 'what' ('Manage data, records, and automate workflows') and a 'when' clause ('Use when the user wants to interact with Uploadcare data'), but the trigger is somewhat circular rather than a concrete phrase, fitting the anchor where 'when' could be more specific.	4 / 5
Trigger Term Quality	Has relevant keywords ('Uploadcare', 'interact with Uploadcare data') but misses common natural variations a user would say, matching the anchor for some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	Anchoring to the named product 'Uploadcare' gives a distinct niche with minimal conflict risk, though the generic action words add minor overlap, fitting the 'mostly distinct; minor overlap risk' anchor.	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/uploadcare/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.