CtrlK
BlogDocsLog inGet started
Tessl Logo

highlevel

Connect your AI assistant to GoHighLevel CRM via the official API v2.

50

Quality

53%

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 ./public/skills/10xcoldleads/highlevel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%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 well-structured and concise but extremely thin: it supplies only an install command and no usable guidance for actually integrating with the GoHighLevel API. Actionability and workflow clarity are the weakest dimensions because the core task has no executable steps.

Suggestions

Add a minimal usage example showing how to authenticate and make a first GoHighLevel API v2 call (e.g. obtaining an API key / OAuth token and a sample contacts endpoint request).

Provide a short workflow sequence: install -> configure credentials -> make first API call -> verify response, so the core integration path is unambiguous.

Either inline a few key endpoints or link to a reference file (e.g. REFERENCE.md) for the full GoHighLevel API v2 surface.

DimensionReasoningScore

Conciseness

The body is lean and mostly token-efficient; the only minor trim is the restated one-liner that duplicates the frontmatter description, fitting 'efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

Provides one concrete executable command ('npx clawhub@latest install highlevel') but no executable guidance for the actual task of connecting to / calling the GoHighLevel API, leaving key details missing per the score-3 anchor.

3 / 5

Workflow Clarity

Only a rough first step (install) is present with major gaps; the workflow for the skill's purpose (auth, endpoints, making API calls) is absent, matching 'rough sequence present but many gaps; steps poorly defined'.

2 / 5

Progressive Disclosure

The under-50-line body has clean section organization (title + Install) and the simple-skill structure is appropriate, though a CRM API skill would arguably benefit from referenced detail files.

4 / 5

Total

13

/

20

Passed

Description

52%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 concise and names a distinct niche (GoHighLevel CRM via API v2), but it uses second-person voice and omits any 'Use when...' trigger guidance, capping completeness and specificity. Adding explicit trigger phrases would lift the weaker dimensions.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user wants to integrate with GoHighLevel CRM, manage contacts/opportunities, or call the GoHighLevel API v2.'

Rewrite in third person to avoid the second-person penalty, e.g. 'Connects an AI assistant to GoHighLevel CRM via the official API v2.'

List one or two more concrete capabilities (e.g. 'manage contacts, fetch opportunities') to raise specificity above a single action.

DimensionReasoningScore

Specificity

Names the domain ('GoHighLevel CRM', 'official API v2') and one concrete action ('Connect your AI assistant'), matching the score-3 anchor, but reduced by 1 for second-person voice ('Connect your AI assistant').

2 / 5

Completeness

Gives a clear 'what' ('Connect your AI assistant to GoHighLevel CRM via the official API v2') but no 'when' / 'Use when...' trigger guidance, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Contains a relevant natural term ('GoHighLevel CRM', 'API v2') but offers no synonyms or variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The product name 'GoHighLevel CRM' names a clear, specific niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Demerzels-lab/elsamultiskillagent
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.