CtrlK
BlogDocsLog inGet started
Tessl Logo

convoloai

Convolo.ai integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Convolo.ai data.

64

Quality

76%

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/convoloai/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 highly actionable with executable commands and a clear connection workflow including polling feedback loops. Its main gaps are a dangling 'Step 2' cross-reference and a small amount of trimmable prose.

Suggestions

Resolve the dangling 'Skip to Step 2' references by either defining a labeled Step 2 section (e.g. '## Step 2 — Search and run actions') or replacing them with the actual target heading.

Trim the opening platform description and filler lines ('Use action names and parameters as needed') to tighten token efficiency.

Add an explicit validation/check step after running actions (e.g. inspect the `output` field and check `error` on failure) to close the workflow feedback loop for write operations.

DimensionReasoningScore

Conciseness

The body is mostly lean operational commands with light explanations; minor padding like the opening platform description and filler lines ('Use action names and parameters as needed') could be trimmed, but it is not noticeably verbose.

4 / 5

Actionability

Provides copy-paste-ready, fully executable commands across every common flow (install, login, headless completion, connection ensure/get, action list/run with JSON input, request proxy) plus a complete proxy-options table.

5 / 5

Workflow Clarity

The connection lifecycle is clearly sequenced with a poll-until-READY feedback loop and explicit handling of CLIENT_ACTION_REQUIRED, but the dangling 'Skip to Step 2' reference and absence of a post-run validation checkpoint leave minor gaps.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections with tables kept appropriately inline for a single-file skill, and external docs are signaled; with no bundle files present there is no multi-file reference pattern to demonstrate, keeping it just below a 5.

4 / 5

Total

17

/

20

Passed

Description

71%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 clear and distinguishable, explicitly covering both capability and a use-trigger, with a strong distinctiveness profile from the named platform. Its main weakness is thin trigger-term coverage and a generic 'when' clause.

Suggestions

Expand the 'when' trigger with concrete scenarios and natural synonyms users would say, e.g. 'Use when working with Convolo.ai leads, calls, dialer projects, call reports, or call analytics'.

Replace the uniform 'Manage' verb with distinct concrete actions per entity (e.g. 'create, list, update, and delete leads, deals, and projects') and drop 'and more' to remove hedging.

Add common variation terms (leads, dialer, call reports) so the trigger keywords match real user phrasing.

DimensionReasoningScore

Specificity

Lists multiple specific data domains ('Manage Leads, Persons, Organizations, Deals, Projects, Activities and more'), but the single repeated verb 'Manage' is narrow and 'and more' hedges coverage, so it falls short of comprehensive distinct actions.

4 / 5

Completeness

Both 'what' (Convolo.ai integration managing listed entities) and 'when' (interact with Convolo.ai data) are present, but the when-clause is generic rather than concrete trigger phrases, so it is not a 5.

4 / 5

Trigger Term Quality

The trigger 'Use when the user wants to interact with Convolo.ai data' provides relevant keywords but only one conceptual term, with no synonyms, scenarios, or common variations (calls, leads, dialer) that users would naturally say.

3 / 5

Distinctiveness Conflict Risk

Naming the proprietary platform 'Convolo.ai' creates a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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.