CtrlK
BlogDocsLog inGet started
Tessl Logo

customerguru

Customer.guru integration. Manage Persons, Organizations, Deals, Leads, Projects, Pipelines and more. Use when the user wants to interact with Customer.guru data.

66

Quality

80%

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

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.

A well-structured, highly actionable CLI integration guide with executable commands and polling-based validation loops. Its main weaknesses are minor verbosity and slightly inconsistent step numbering.

Suggestions

Tighten the opening overview and the "Best practices" bullets (e.g. replace "burn less tokens" with precise wording) to improve conciseness.

Reconcile the workflow numbering: label Step 1/Step 2 explicitly or renumber the orphaned "1b. Wait for the connection to be ready" so cross-references like "skip to Step 2" resolve.

Move the inline "Popular actions" table and proxy flag reference into a separate reference file if the body grows, to better leverage progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient with copy-paste CLI commands, but includes minor over-explanation such as the opening platform description and informal phrasing like "burn less tokens" that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) that cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

A clear install→authenticate→connect→search→run sequence with polling feedback loops and explicit state checks; minor numbering muddle ("skip to Step 2" with no labeled Step 1/2, an orphaned "1b") keeps it below 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections in a single file with no nested references; at ~140 lines it exceeds the simple-skill threshold, so the structure earns anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

78%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.

A clear, third-person description that states concrete capabilities and an explicit usage trigger tied to a distinct product. It is held back from the top band mainly by the generic "interact with…data" trigger phrasing and the open-ended "and more".

DimensionReasoningScore

Specificity

Lists several concrete managed entities ("Persons, Organizations, Deals, Leads, Projects, Pipelines"), but the trailing "and more" leaves a minor coverage gap, matching anchor 4 rather than a fully comprehensive 5.

4 / 5

Completeness

Both "what" (integration managing named entities) and "when" (the "Use when…" clause) are present; the "when" is explicit but slightly generic ("interact with…data") rather than concrete trigger phrases, so it sits at anchor 4 not 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("Customer.guru", persons, deals, leads, pipelines) with an explicit "Use when the user wants to interact with Customer.guru data" trigger, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Names a distinct product (Customer.guru) with a clear niche and trigger, giving minimal overlap risk with other skills, matching anchor 5.

5 / 5

Total

17

/

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.