CtrlK
BlogDocsLog inGet started
Tessl Logo

claid-ai

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

61

Quality

72%

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/claid-ai/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 body is a strong, executable integration guide with concrete CLI commands and a clear connection workflow, held back only by minor redundancy, a broken step reference, and an unexplained overview list.

DimensionReasoningScore

Conciseness

The body is mostly lean commands and brief explanations with little concept padding, but contains minor fluff ("so you can focus on the integration logic rather than auth plumbing") and a redundant repeated action-list command.

4 / 5

Actionability

It provides copy-paste-ready, executable commands throughout (login, connection ensure, action list/run, request) plus a thorough proxy-flags table, covering the common integration cases concretely.

5 / 5

Workflow Clarity

There is a clear install→login→connect→poll→search→run sequence with a polling/state feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the 'skip to Step 2' references point to a non-existent Step 2 heading and the action-search material is split across two sections.

4 / 5

Progressive Disclosure

Content is well-organized into headed sections with no external bundle files needed, but the bare 'Claid AI Overview' list (Project/Media/Task/Model/User) lacks context and the 'Searching for actions' / 'Popular actions' split is slightly redundant.

4 / 5

Total

17

/

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 includes an explicit 'Use when' trigger and names a distinct product, but its capability list is generic and doesn't reflect Claid AI's actual image-enhancement purpose, leaving it solid but not exemplary.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Claid AI capabilities (e.g., enhance/optimize product images, resize, recolor, background removal).

Sharpen the trigger clause with natural user phrasings such as 'Use when the user wants to enhance or optimize product images for e-commerce via Claid AI.'

Align the description with the body so 'what' reflects image enhancement rather than generic data management.

DimensionReasoningScore

Specificity

It names the domain ("Claid AI integration") and enumerates a few action areas ("Manage data, records, and automate workflows"), but those actions are abstract and generic rather than concrete capabilities.

3 / 5

Completeness

Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Claid AI data") are present, but neither is sharply concrete, so it sits below the top anchor.

4 / 5

Trigger Term Quality

The product name "Claid AI" is a clear natural trigger, but the only supporting phrase is the generic "interact with Claid AI data", with no synonyms, use-case phrasings, or variations a user might actually say.

3 / 5

Distinctiveness Conflict Risk

Naming a specific product ("Claid AI") gives it a clear niche and low conflict risk, though the generic 'manage data, records, and automate workflows' phrasing could still overlap with general data-management skills.

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.