CtrlK
BlogDocsLog inGet started
Tessl Logo

gladly

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

55

Quality

62%

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/gladly/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, actionable guide to driving Gladly through the Membrane CLI, with executable commands and a clear connection-readiness feedback loop. Its main weaknesses are a redundant Gladly overview, a dangling 'Step 2' reference, and a thin 'Popular actions' section that adds little.

DimensionReasoningScore

Conciseness

The body is mostly efficient CLI commands, but the opening 'Gladly is a customer service platform...' overview explains background Claude largely already knows and the 'Popular actions' section repeats the discovery command, fitting anchor 3 rather than the lean anchor 5.

3 / 5

Actionability

It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run with --input, and a proxy flag table; minor gaps (CONNECTION_ID placeholders, no fully worked end-to-end example) keep it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The install → login → connection → search → run sequence is clear, and the connection-readiness section has explicit state checks (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with a poll-again feedback loop; a dangling 'skip to Step 2' reference with no labeled Step 2 is a minor gap, matching anchor 4.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nesting and all guidance inline (appropriate given dynamic CLI-based action discovery and no bundle files); the thin 'Popular actions' section is a minor organization gap, so anchor 4 fits better than 5.

4 / 5

Total

15

/

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 has an explicit 'Use when' trigger and is anchored to a distinct named product, but its action list is generic ('manage data, records, automate workflows') and it lacks the natural domain vocabulary (customers, conversations, tickets) users would actually say.

Suggestions

Replace generic verbs with concrete Gladly actions, e.g. 'Search customers and conversations, view messages, and automate support workflows'.

Add natural trigger terms users say, such as 'customers', 'conversations', 'support tickets', or 'inquiries' alongside 'Gladly data'.

Tighten the 'what' so it reads as specific Gladly capabilities rather than 'Manage data, records, and automate workflows'.

DimensionReasoningScore

Specificity

It names the domain (Gladly) but the actions 'Manage data, records, and automate workflows' are generic and minimal rather than concrete Gladly-specific operations, matching anchor 2 rather than the multi-action anchor 5.

2 / 5

Completeness

It states a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Gladly data'); the trigger clause is present so it clears the cap of 3, though the 'what' is vague, fitting anchor 4.

4 / 5

Trigger Term Quality

'Gladly' and 'interact with Gladly data' provide a relevant product keyword, but it omits the natural domain terms users would actually say (customers, conversations, support tickets, inquiries), so it lands at anchor 3.

3 / 5

Distinctiveness Conflict Risk

The named product 'Gladly' gives it a clear niche with minimal conflict risk, but the generic 'manage data, records, automate workflows' phrasing could overlap with other integration skills, matching anchor 4 rather than 5.

4 / 5

Total

13

/

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.