highlevel
Connect your AI assistant to GoHighLevel CRM via the official API v2. Manage contacts, conversations, calendars, pipelines, invoices, payments, workflows, and 30+ endpoint groups through natural language. Includes interactive setup wizard and 100+ pre-built, safe API commands. Python 3.6+ stdlib only — zero external dependencies.
74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at specificity and distinctiveness by clearly naming the GoHighLevel CRM platform and listing numerous concrete capabilities. However, it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill, and could benefit from common user variations of the platform name.
Suggestions
Add a 'Use when...' clause with trigger terms like 'GoHighLevel', 'GHL', 'high level CRM', 'lead management', or when users mention specific entities like contacts or pipelines in a CRM context.
Include common abbreviations and variations users might say, such as 'GHL', 'HighLevel', or 'Go High Level' (with spaces).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Manage contacts, conversations, calendars, pipelines, invoices, payments, workflows, and 30+ endpoint groups'. Also mentions specific features like 'interactive setup wizard' and '100+ pre-built, safe API commands'. | 3 / 3 |
Completeness | Clearly answers 'what' (connect to GoHighLevel CRM, manage various entities), but lacks an explicit 'Use when...' clause or trigger guidance. The 'when' is only implied through the domain-specific terminology. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'GoHighLevel', 'CRM', 'API', 'contacts', 'conversations', 'calendars', 'pipelines', 'invoices', 'payments', 'workflows'. However, missing common user variations like 'GHL', 'high level', 'lead management', or 'customer relationship'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting 'GoHighLevel CRM' and 'official API v2' - unlikely to conflict with other skills. The specific platform name and technical details create clear boundaries. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive GoHighLevel API coverage with strong actionability through concrete commands and clear progressive disclosure via reference files. However, it's overly verbose with inline content that belongs in reference files (the 39-endpoint table), includes promotional/affiliate content that wastes tokens, and lacks explicit validation checkpoints in workflows beyond basic connection testing.
Suggestions
Move the 39 endpoint groups table to a reference file (e.g., references/api-coverage.md) and keep only the most common 5-10 operations in the main skill
Remove promotional content and affiliate links—these waste tokens and don't help Claude execute tasks
Add explicit validation steps after API operations, e.g., 'After create_contact, verify with get_contact [id] to confirm creation succeeded'
Add error recovery guidance: what to do when test_connection fails, common token/scope issues and how to diagnose them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes useful information but is verbose in places—the extensive API coverage table (39 endpoint groups) and detailed scope tables could be moved to reference files. The promotional content and affiliate links add unnecessary tokens. | 2 / 3 |
Actionability | Provides concrete, executable commands (python3 scripts/ghl-api.py commands), specific bash export statements, clear step-by-step setup instructions, and a comprehensive command reference table. Copy-paste ready. | 3 / 3 |
Workflow Clarity | Setup workflow has clear numbered steps, but lacks explicit validation checkpoints beyond 'test connection'. No feedback loops for error recovery during setup, and no validation steps mentioned for API operations that could fail. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview in main file and well-signaled one-level-deep references to 10 specific reference docs (references/contacts.md, etc.). Content is appropriately split between quick-start and detailed documentation. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- 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.