CtrlK
BlogDocsLog inGet started
Tessl Logo

nethunt-crm

NetHunt CRM integration. Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more. Use when the user wants to interact with NetHunt CRM data.

61

Quality

73%

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/nethunt-crm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 solid, command-driven integration guide with a genuine connection-state feedback loop and good section structure. Its main weakness is conciseness: a marketing-style intro, a duplicated overview list, and redundant action-list sections pad the document unnecessarily.

Suggestions

Remove the Gmail/SMB marketing intro paragraph and the "NetHunt CRM Overview" bullet list, which duplicate the description's entity list and add background Claude can infer from the official-docs link.

Consolidate the "Searching for actions" and "Popular actions" sections, which both demonstrate `action list --intent` with inconsistent `membrane` vs `npx @membranehq/cli@latest` styles — pick one form and drop the redundancy.

Number the workflow steps explicitly (fixing the dangling "Step 2"/"1b" references) and add a verification note for `membrane action run` describing how to check the `output`/`error` fields before proceeding.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete commands, but the Gmail/SMB marketing intro, the "NetHunt CRM Overview" list that duplicates the description's entities, and two redundant `action list` sections add unnecessary explanation that could be tightened, fitting anchor 3 rather than the lean anchor 4.

3 / 5

Actionability

It provides copy-paste-ready commands covering install, auth, connect, poll, search, run, and proxy, but mixes `membrane` and `npx @membranehq/cli@latest` invocation styles and relies on placeholder-heavy examples, leaving minor gaps per anchor 4.

4 / 5

Workflow Clarity

There is a clear install→auth→connect→poll→search→run sequence with a real feedback loop on connection state (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the dangling "Step 2"/"1b" references and the absence of error-handling for `action run` are minor validation gaps, matching anchor 4.

4 / 5

Progressive Disclosure

The content is well-organized into clearly headed sections with no nested references and all material appropriately inline, but at ~140 lines some reference-like material (the proxy flags table, detailed clientAction sub-fields) sits inline rather than in a separate file, fitting anchor 4 over the cleanly-split anchor 5.

4 / 5

Total

15

/

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 strong, product-specific description that clearly states both capability and trigger. It is held back from the top tier only by a single action verb, a generic "when" clause, and a few missing synonyms rather than any structural weakness.

DimensionReasoningScore

Specificity

"Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more" names several concrete CRM entities, but relies on a single action verb ("Manage") and the "and more" hedge signals minor coverage gaps, fitting anchor 4 rather than the multi-verb comprehensiveness of anchor 5.

4 / 5

Completeness

It answers both what ("Manage Leads, Persons, Organizations, Deals, Pipelines, Activities") and when ("Use when the user wants to interact with NetHunt CRM data"), but the when is generic rather than concrete entity-based trigger phrases, matching anchor 4 instead of the explicit-trigger anchor 5.

4 / 5

Trigger Term Quality

It includes good natural terms ("NetHunt CRM", "Leads", "Deals", "Pipelines"), but uses "Persons/Organizations" rather than the more common "contacts/companies" users would say, leaving a few natural synonyms missing per anchor 4.

4 / 5

Distinctiveness Conflict Risk

The description is explicitly scoped to the named product "NetHunt CRM" with a product-specific trigger, giving it a clear niche with minimal conflict risk against 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.