CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudlayer

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

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cloudlayer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 SKILL.md body is highly actionable with copy-paste membrane commands, a clear connection workflow that includes polling and error-branch feedback loops, and well-organized sections; it is mostly concise with only minor over-explanation in the clientAction field guide.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands and minimal preamble, but sections like the clientAction field-by-field breakdown and overview hierarchy add some explanation that could be trimmed, matching 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

It provides copy-paste-ready membrane commands with flags and JSON examples, an actions table with concrete keys, and proxy-request usage, fully covering the common cases per 'fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

The connection flow is explicitly sequenced (ensure -> wait/poll -> READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR branches) with a validate-then-retry feedback loop for CLIENT_ACTION_REQUIRED and guarded progression, matching 'clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

Content is well-organized into headed sections with inline commands and a reference table, and there are no broken multi-level references, but the actions table and proxy options are inlined rather than offloaded to reference files, fitting 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

18

/

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 is third-person and answers both what and when, but its actions are abstract ('manage data, records') rather than the concrete screenshot/PDF capabilities Cloudlayer actually provides, and it lacks natural user trigger terms like 'PDF', 'screenshot', or 'convert webpage'.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with Cloudlayer's concrete capabilities, e.g. 'Capture website screenshots, convert web pages to PDFs, and extract website content'.

Add natural trigger terms a user would actually say, such as 'screenshots', 'PDF', 'convert webpage to PDF', or 'website to image'.

Sharpen the 'when' clause to concrete triggers, e.g. 'Use when the user wants to screenshot a website, convert a URL or HTML to PDF, or extract web page content.'

DimensionReasoningScore

Specificity

The description names the domain (Cloudlayer) and two generic actions ('Manage data, records, and automate workflows') but they are abstract rather than concrete API operations like screenshot capture or PDF conversion, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

It states both what (manage data, records, automate workflows) and when ('Use when the user wants to interact with Cloudlayer data'), but the 'when' is generic rather than tied to concrete trigger phrases, matching 'has both what and when; when could be more explicit'.

4 / 5

Trigger Term Quality

It offers 'Cloudlayer data' and 'workflows' but omits the natural phrases a user would say ('screenshots', 'PDFs', 'convert webpage to PDF', file extensions), leaving common synonyms missing per the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Cloudlayer name and 'Cloudlayer data' phrasing make it mostly distinct with only minor overlap risk against generic data-management skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.