CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudback

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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 content is a strong, executable integration guide with concrete commands and a clear connection-state workflow with feedback loops. Minor improvements would consolidate the workflow into a single end-to-end checklist and trim a few explanatory sentences.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands and minimal prose; the opening product overview is justified for a niche product, though a few explanatory sentences could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands across install, auth, connection, action search/run, and proxy requests, with a complete flag table covering common cases.

5 / 5

Workflow Clarity

The connection-readiness workflow has explicit polling checkpoints and a clear state machine with recovery actions (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but there is no single end-to-end sequenced checklist tying all sections together.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no bundle files to reference; some inlined content (proxy flag table, best practices) could live in separate files but the single-file structure is navigable.

4 / 5

Total

17

/

20

Passed

Description

67%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 functional and correctly answers both what and when with a clear product anchor, but the trigger-term coverage is thin and the actions are generic rather than specific. Adding concrete capability nouns and natural synonyms would strengthen it.

Suggestions

Add specific concrete actions (e.g., 'create and restore backups, view restoration points, manage backup tasks') instead of the generic 'manage data, records'.

Broaden trigger terms with natural variations users would say (e.g., 'backups', 'restore', 'backup tasks', 'restoration points').

Tighten the 'when' clause to mention concrete triggers like 'when the user wants to back up, restore, or monitor SaaS application data'.

DimensionReasoningScore

Specificity

Names the Cloudback domain and lists several concrete actions ('Manage data, records, and automate workflows'), though the actions are fairly generic rather than granular.

4 / 5

Completeness

Explicitly answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Cloudback data'), though the trigger is somewhat generic.

4 / 5

Trigger Term Quality

Includes relevant keywords ('Cloudback integration', 'Cloudback data') but lacks synonyms, variations, or file extensions a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

Anchored to a specific named product (Cloudback), giving it a clear niche and low conflict risk, though the action verbs themselves are generic.

4 / 5

Total

15

/

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.