Name: kustomer
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

kustomer

Kustomer integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Kustomer data.

Quality

61%

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

Quality

Content

66%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 a solid, mostly executable guide to the Membrane-Kustomer workflow with a well-structured connection state machine and clear commands. Its main weaknesses are mild verbosity (re-explaining known concepts and restating best practices) and the absence of explicit post-run validation for action execution.

Suggestions

Trim explanations Claude already knows — the opening 'Kustomer is a CRM platform...' paragraph and the Membrane auth rationale can be shortened or removed.

Add an explicit validation/verification step after running or proxying an action (e.g., check the `output`/error field and confirm the intended record was created or updated), since these are batch/write operations.

Consider moving the 20-row Popular actions table into a separate references file and keeping only the most common few inline, improving token efficiency and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command examples and tables, but it explains concepts Claude already knows (what Kustomer is, that Membrane handles auth, general rationale paragraphs) and the 'Best practices' section restates guidance already given, so it could be tightened.	3 / 5
Actionability	Provides concrete, executable CLI commands (login, connection ensure, action list/run, request) with flag tables and JSON-output guidance; minor gaps include placeholder placeholders like CONNECTION_ID and the lack of a worked action-run example with real input.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with a state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and explicit polling/retry steps, giving strong checkpoints; it is capped just below 5 because destructive/run operations lack explicit post-run validation.	4 / 5
Progressive Disclosure	Content is well organized into labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files present and no nested references; the large Popular-actions table is inline and could arguably live in a separate reference file, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

57%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 functional and includes an explicit trigger clause, but it relies on a generic 'Manage ...' verb and a broad 'interact with Kustomer data' trigger rather than concrete operations and natural user phrases. It is clearly distinct thanks to the Kustomer brand name yet could be sharper.

Suggestions

Replace the generic verb 'Manage Organizations, Users, Goals, Filters' with concrete actions users perform, e.g. 'Search, create, and update customers, conversations, companies, and notes'.

Broaden the trigger with natural user phrases and synonyms: 'Use when the user wants to look up customers, view or reply to conversations, manage support tickets, or query Kustomer data.'

Align the listed entities (Organizations, Users, Goals, Filters) with the actions the skill actually exposes, since the body centers on Customers/Conversations/Companies rather than Goals and Filters.

Dimension	Reasoning	Score
Specificity	Names the domain (Kustomer) and several concrete action targets ('Manage Organizations, Users, Goals, Filters') but the actions are generic ('Manage') rather than enumerated specific operations, leaving coverage incomplete.	3 / 5
Completeness	Provides a clear 'what' ('Manage Organizations, Users, Goals, Filters') and an explicit 'when' ('Use when the user wants to interact with Kustomer data'), though the trigger could be more specific about which user intents map to the skill.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Kustomer' and the phrase 'interact with Kustomer data', but lacks common synonyms, alternative phrasings, or entity terms users might say (e.g., 'customers', 'conversations', 'tickets', 'support').	3 / 5
Distinctiveness Conflict Risk	The proper noun 'Kustomer' plus the enumerated entities give it a clear niche with minimal overlap risk against other CRM skills, though the generic 'interact with data' phrasing leaves minor overlap risk with adjacent integrations.	4 / 5
	Total	14 / 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/kustomer/SKILL.md
Commit: f484c82

Reviewed: 6 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.