Name: gohighlevel
Rating: 48.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gohighlevel

GoHighLevel integration. Manage Organizations. Use when the user wants to interact with GoHighLevel data.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gohighlevel/SKILL.md

Quality

Content

45%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 genuine integration guidance is concrete and well-sequenced, but it is buried under an enormous, irrelevant, duplicated bullet list that destroys token efficiency and structure. Removing the junk list and optionally splitting the action reference would dramatically improve the score.

Suggestions

Delete the ~1547-line 'GoHighLevel Overview' bullet list entirely; it is unrelated padding that wastes context and is truncated mid-item.

If the full action catalog is useful, move it to references/actions.md and link to it from a concise 'Popular actions' table in SKILL.md.

Add a validation/confirmation step before destructive actions (delete-contact, delete-opportunity) and label the workflow steps explicitly (e.g. fix the dangling 'Step 2' reference).

Dimension	Reasoning	Score
Conciseness	The body is dominated by roughly 1547 lines of a duplicated, generic bullet list (e.g. 'PDF', 'Word Document', 'Kernel', 'VPN', 'Gantt Chart') unrelated to GoHighLevel — severely verbose, heavily padded, and ending mid-line in a broken list item. This is the worst-case anchor.	1 / 5
Actionability	The actionable section provides concrete, copy-paste-ready commands (`npm install -g @membranehq/cli@latest`, `membrane login`, `membrane connection ensure`, `membrane action run ... --input`, `membrane request`) plus a popular-actions table and flag reference. It is not 5 because some flows (e.g. constructing action inputs) rely on schemas the user must discover rather than worked examples.	4 / 5
Workflow Clarity	There is a clear sequence (install → login → ensure connection → poll until READY → search actions → run/proxy) with validation checkpoints (state polling, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR handling). It is not 5 because a referenced 'Step 2' is not labeled, and no validation guidance is given for the destructive delete actions listed in the table.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and everything is inlined into one monolithic file, with a giant junk list that should not be present at all. Section headers in the latter half add some structure, but overall organization is poor and no external references are signaled, keeping it below anchor 3.	2 / 5
	Total	11 / 20 Passed

Description

61%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 distinctive and includes an explicit trigger clause, but its capability statement is thin and generic ('Manage Organizations'). It would benefit from listing concrete GoHighLevel actions (contacts, opportunities, appointments, campaigns) to lift specificity and trigger-term coverage.

Suggestions

Replace the generic 'Manage Organizations' with concrete actions, e.g. 'Manage contacts, opportunities, appointments, calendars, and campaigns in GoHighLevel'.

Add natural trigger synonyms users say, such as 'CRM', 'contacts', 'pipelines', or '.gohighlevel' context, to broaden keyword coverage.

Tighten the 'when' clause to mention specific intents (e.g. 'Use when the user wants to query or update GoHighLevel CRM data').

Dimension	Reasoning	Score
Specificity	It names the domain ('GoHighLevel integration') but the only action is the generic 'Manage Organizations', which is minimal and non-specific rather than a concrete capability list. It does not reach anchor 3 because there are not 1-2 clearly concrete actions.	2 / 5
Completeness	It states both a 'what' ('Manage Organizations') and an explicit 'when' ('Use when the user wants to interact with GoHighLevel data'). It is not 5 because the 'what' is thin and non-comprehensive; it is not 3 because the trigger clause is explicit rather than weakly implied.	4 / 5
Trigger Term Quality	It surfaces the natural product keyword 'GoHighLevel' and the phrase 'interact with GoHighLevel data', but misses common variations/synonyms a user might say (CRM, contacts, opportunities, appointments). It is above anchor 2 (which has only generic terms) but below 4 due to limited variation.	3 / 5
Distinctiveness Conflict Risk	'GoHighLevel integration' is a clear, named niche with a distinct product trigger and minimal overlap risk with other skills. It clearly matches the anchor 5 example of a clear niche with distinct triggers.	5 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1712 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/gohighlevel/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.