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

cloudfill

CloudFill integration. Manage data, records, and automate workflows. Use when the user wants to interact with CloudFill 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/cloudfill/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 strong, actionable integration guide with executable commands and an explicit connection-state workflow, slightly held back by a padded intro paragraph, a filler overview stub, and thin error-recovery guidance.

Suggestions

Delete the empty 'CloudFill Overview' stub and trim the opening paragraph to one line; Claude does not need CloudFill explained as 'similar to Dropbox or Google Drive'.

Add an explicit retry/recovery loop for CONFIGURATION_ERROR and SETUP_FAILED states (read the error field, remediate, re-run connection ensure) rather than just 'check the error field for details'.

Consider moving the proxy flag table and popular-actions list into a references/ file linked from the body to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command reference, but the opening paragraph over-explains what CloudFill is ('similar to Dropbox or Google Drive... used by individuals and businesses') and the 'CloudFill Overview' stub ('Form / Field / Submission... Use action names and parameters as needed') is filler that should be trimmed.	3 / 5
Actionability	Copy-paste ready commands cover the common cases end-to-end: install, login (incl. headless), connection ensure/wait, action list/run with --input JSON, and the proxy request with a full flag table and popular-actions table.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence with explicit state-polling checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, though error recovery for CONFIGURATION_ERROR/SETUP_FAILED is thin ('check the error field') with no explicit retry loop.	4 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no buried or nested references; the empty Overview stub and lack of a split-out reference for the bulkier proxy/flag material are minor organization gaps that keep it below 5.	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 a 'Use when' trigger and names the target service, but its capabilities are stated in vague generic terms rather than the concrete CloudFill actions (PDF generation, templates) the skill actually supports.

Suggestions

Replace 'Manage data, records, and automate workflows' with the concrete actions the skill exposes, e.g. 'Generate PDFs from templates, list and inspect PDF templates, and run CloudFill actions.'

Broaden trigger terms with natural synonyms users would say, such as 'PDFs', 'PDF templates', 'form filling', or 'CloudFill records'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to generate or fill PDFs, list PDF templates, or automate CloudFill workflows.'

Dimension	Reasoning	Score
Specificity	It names the CloudFill domain but the actions ('Manage data, records, and automate workflows') are minimal and generic, with no concrete capabilities like PDF generation or templates mentioned.	2 / 5
Completeness	Both a 'what' (manage data/records/automate workflows for CloudFill) and an explicit 'when' ('Use when the user wants to interact with CloudFill data') are present, though the 'when' is generic and could be more specific.	4 / 5
Trigger Term Quality	Only one or two keywords ('CloudFill', 'interact with CloudFill data') are present; the 'manage data, records, and automate workflows' phrasing is generic boilerplate rather than natural domain terms users would say.	2 / 5
Distinctiveness Conflict Risk	The named CloudFill service gives it a clear niche with minimal conflict risk, though the generic 'manage data/records' action verbs create minor overlap with other data-oriented skills.	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/cloudfill/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.