Name: helpcrunch
Rating: 58.4 (1 reviews)
Author: membranedev

helpcrunch

HelpCrunch integration. Manage Organizations, Users, Articles, Reports, Automations. Use when the user wants to interact with HelpCrunch data.

Quality

67%

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/helpcrunch/SKILL.md

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 well-structured, actionable integration skill with executable CLI commands and a clear connection workflow including validation states. The main weakness is mild verbosity from introductory background and narrative padding.

Suggestions

Trim the marketing-style background paragraph ('HelpCrunch is a customer communication platform combining...') since Claude does not need it to use the skill.

Reconcile the Overview entity list (Conversation/Message/User/Company/Article/Category) with the Popular actions table (Applications/Departments/Agents/Chats/Customers) so the structure matches what is actually available.

Add one concrete example of running an action with a real --input payload (e.g. create-customer) to round out the actionability guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and a compact actions table, but includes unnecessary background ('customer communication platform combining live chat, email marketing...') and some narrative padding that could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready bash commands for install, login, connection, action search/run, and proxy requests, with only minor gaps in parameter examples.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and error-recovery guidance, with only minor checkpoint gaps.	4 / 5
Progressive Disclosure	Single self-contained file with well-organized sections and clear navigation; no bundle files are needed and content is appropriately sectioned rather than monolithic.	4 / 5
	Total	15 / 20 Passed

Description

67%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 concise, third-person description that covers both capability and trigger guidance for a specific integration niche. It is slightly thin on natural keyword variations and could make the 'when' more concrete.

Suggestions

Add natural trigger synonyms and likely user phrasings (e.g. 'HelpCrunch chats, customers, knowledge base articles, or live chat data') to broaden trigger coverage.

Make the 'when' clause more concrete by listing the kinds of tasks (e.g. 'Use when the user wants to list or search chats, manage customers, or read HelpCrunch articles').

Align the entity list with what the skill actually exposes (the body emphasizes Conversations/Messages/Customers/Chats rather than Organizations/Reports/Automations).

Dimension	Reasoning	Score
Specificity	Names the HelpCrunch domain and lists several concrete managed entities (Organizations, Users, Articles, Reports, Automations) with the verb 'Manage', giving good action coverage with only minor gaps.	4 / 5
Completeness	Clearly states both what it does ('Manage Organizations, Users, Articles, Reports, Automations') and when to use it ('Use when the user wants to interact with HelpCrunch data'), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the relevant term 'HelpCrunch' and the phrase 'interact with HelpCrunch data', but lacks common variations, synonyms, or file extensions that users might naturally say.	3 / 5
Distinctiveness Conflict Risk	Targets a clear HelpCrunch-specific niche with distinct triggers, with only minor overlap risk against other CRM/support integrations.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/helpcrunch/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.