Name: cloudfiles
Rating: 60 (1 reviews)
Author: membranedev

cloudfiles

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

Quality

70%

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

Quality

Content

82%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, a well-structured connection workflow, and explicit error-state feedback loops. It is held back only by minor redundancy, slightly inconsistent step numbering, and a single-file structure that could offload some reference detail to bundled files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a focused flag table, but has minor trimmable parts such as the duplicated `membrane action list` invocation under 'Popular actions' and the filler line 'Use action names and parameters as needed.' This fits the score-4 anchor 'Efficient; minor instances of over-explanation that could be trimmed' and does not reach score 5 due to that redundancy.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure/get, action list/run, request with a thorough flag table), matching the score-5 anchor 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases.' Placeholders like CONNECTION_ID are legitimate, not gaps.	5 / 5
Workflow Clarity	There is a clear install-authenticate-connect-search-run sequence with explicit state-based checkpoints and a genuine feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), fitting the score-4 anchor 'Clear sequence with most checkpoints present; minor validation gaps.' It falls short of score 5 because the step numbering is inconsistent (references to 'Step 2' with no matching header) and run-results validation is not addressed.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained file with clear section headers organizing install, auth, connection, actions, proxy, and best-practices content, matching the score-4 anchor 'Good structure; most content is appropriately placed; minor organization gaps.' It does not reach score 5 because content like the detailed clientAction state contract and the proxy flag table could live in one-level-deep reference files for an even leaner overview.	4 / 5
	Total	17 / 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 specific app, but its action language is generic and its trigger terms lack synonyms or concrete phrases users would naturally say. Tightening the action list and adding concrete trigger keywords would raise specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete CloudFiles operations such as uploading, sharing, listing, and retrieving files or shared links.

Expand the 'Use when' clause with natural trigger phrases (e.g. 'Use when the user wants to upload, share, or fetch CloudFiles files and folders, or manage shared links').

Add file-extension or object terms (files, folders, shared links, records) that users are likely to actually say.

Dimension	Reasoning	Score
Specificity	The domain is named ("CloudFiles integration") and lists actions ("Manage data, records, and automate workflows"), but those actions are generic and non-concrete rather than specific operations, matching the score-2 anchor 'Names the domain but actions are minimal or generic.' It does not reach score 3 because no concrete, distinguishable action (e.g. upload, share, list files) is named.	2 / 5
Completeness	It states both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with CloudFiles data"), matching the score-4 anchor where the 'when' could be more specific. It falls short of score 5 because the 'when' trigger is broad rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces some relevant terms ("CloudFiles", "data", "records", "workflows", "interact with CloudFiles data") but lacks common variations or synonyms a user might naturally say, fitting the score-3 anchor 'Some relevant keywords but missing common variations or synonyms.' It is above score 2 because more than one generic keyword is present, but below score 4 due to thin natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a specific named app ("CloudFiles") gives it a clear niche with mostly distinct triggers, matching the score-4 anchor 'Mostly distinct; minor overlap risk with closely related skills.' It does not reach score 5 because the generic 'Manage data, records, and automate workflows' phrasing could still overlap with other data-oriented 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/cloudfiles/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.