CtrlK
BlogDocsLog inGet started
Tessl Logo

avochato

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

56

Quality

65%

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

Quality

Content

68%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 an efficient, actionable CLI guide with strong command coverage and clean section structure. Its main weakness is workflow clarity around risky operations: send/broadcast actions run without explicit validation or feedback loops.

Suggestions

Add a verification checkpoint before destructive or batch actions, e.g. confirm the contact/recipient before 'send-message' or dry-run before broadcasts.

Fill in the empty 'Description' cells in the Popular actions table so action discovery does not require an extra list call.

Trim the opening marketing sentence about support/sales/marketing teams; it does not aid execution and competes for context.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands and minimal over-explanation; the opening marketing paragraph ('used by support, sales, and marketing teams') and the duplicated proxy/connection guidance add a little padding but stay efficient.

4 / 5

Actionability

Provides copy-paste-ready CLI commands for install, auth, connection, searching, running actions, and proxy requests with flag tables; minor gaps include placeholder CONNECTION_ID and an actions table whose descriptions are empty.

4 / 5

Workflow Clarity

The connect-to-Avochato flow has a clear sequence and polling, but destructive/batch operations (send-message, broadcasts) and the action-run path lack explicit validation or verify-before-proceeding checkpoints, capping clarity at 3.

3 / 5

Progressive Disclosure

Well-organized sections (Overview, Authentication, Connecting, Actions, Proxy, Best practices) with no nested file references and no bundle files to misroute; the inlined actions table and proxy flags are appropriately concise rather than monolithic.

4 / 5

Total

15

/

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 names a distinct niche and includes an explicit 'Use when' trigger, meeting the core completeness bar. It is weakened by vague action verbs ('manage', 'automate workflows') and missing concrete Avochato-specific trigger terms.

Suggestions

Replace generic verbs with concrete Avochato actions, e.g. 'Search and send messages, manage contacts, and run broadcast campaigns in Avochato.'

Add natural user-facing trigger terms such as 'SMS', 'WhatsApp', 'tickets', or 'broadcasts' so the skill fires on how users actually phrase requests.

Tighten the 'when' clause to specific scenarios, e.g. 'Use when the user wants to send or search Avochato messages, manage contacts, or run broadcasts.'

DimensionReasoningScore

Specificity

Names the Avochato domain and broad actions ('Manage data, records, and automate workflows') but these are generic verbs with no specific concrete actions like 'search contacts' or 'send messages'.

3 / 5

Completeness

Has both a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Avochato data'), though the 'when' is somewhat broad rather than concrete.

4 / 5

Trigger Term Quality

Includes 'Avochato' and 'interact with Avochato data' as triggers, but misses natural phrasing variations users would say such as 'SMS', 'contacts', 'messages', 'broadcasts', or 'tickets'.

3 / 5

Distinctiveness Conflict Risk

The 'Avochato' name is a distinct niche anchor, giving it minimal conflict risk, though the generic 'manage data, records' framing is shared with many CRM-style 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.