Name: crisp
Rating: 60 (1 reviews)
Author: membranedev

crisp

Crisp integration. Manage Persons, Organizations, Conversations, Users. Use when the user wants to interact with Crisp data.

Quality

70%

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

Quality

Content

75%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 content is a strong, actionable CLI integration guide with executable commands and a useful state-machine for connection setup. Its main weaknesses are minor verbosity in the intro and a small workflow-labeling gap rather than structural problems.

Suggestions

Trim the introductory paragraph explaining what Crisp is and the "auth plumbing" aside; assume Claude can infer platform context.

Fix the "skip to Step 2" reference by labeling the action-search/run sections as Step 2, or remove the cross-reference.

Add a brief validation/checkpoint note for destructive actions (e.g., confirm a conversation or people profile ID before running delete-* actions).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but includes unnecessary explanation Claude could infer ("Crisp is a customer support and engagement platform. It's used by businesses to manage live chat, email, and social media...") and padding ("focus on the integration logic rather than auth plumbing"), matching the 3 anchor of mostly efficient with some tightening needed.	3 / 5
Actionability	It provides many copy-paste-ready commands (install, login, connection ensure/get, action list/run, request) plus a 16-row popular-actions table and a proxy-flags table that cover the common cases, matching the 5 anchor of fully executable guidance.	5 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear with a state-machine feedback loop (poll READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but it references an unlabeled "Step 2" and offers no validation guidance for destructive actions (Delete Conversation, Delete People Profile), matching the 4 anchor with minor validation gaps.	4 / 5
Progressive Disclosure	It is a single, well-sectioned file with clear headers and no nested references, but at ~157 lines with no bundle files the under-50-line simple-skill exception does not apply and content like the action table could live in a separate reference, matching the 4 anchor of good structure with minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

66%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 clearly names the Crisp platform and an explicit use-trigger, with good distinctiveness. It is held back by a single generic verb and limited trigger-term variety rather than a comprehensive list of concrete actions and synonyms.

Suggestions

Replace the generic verb "Manage" with specific concrete actions, e.g. "List, create, update, and delete Crisp conversations, messages, and people profiles."

Expand the "Use when" clause with concrete natural triggers such as live chat, customer messages, support conversations, or people/contacts in Crisp.

Align listed entities with the skill's actual capabilities (the body exposes People/Conversations/Messages/Websites, not "Organizations" or "Users").

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Conversations, Users" lists several domain entities but relies on a single generic verb ("Manage") rather than distinct concrete actions, matching the 3 anchor (domain + limited actions) and falling short of 4's several specific actions.	3 / 5
Completeness	It has a clear "what" ("Crisp integration. Manage Persons, Organizations, Conversations, Users.") and an explicit "Use when the user wants to interact with Crisp data" clause, but the single trigger phrase could be more specific, matching the 4 anchor rather than 5's multiple concrete triggers.	4 / 5
Trigger Term Quality	It surfaces the strong natural keyword "Crisp" plus entity nouns (Conversations, Persons, Users) but misses common variations/synonyms a user might say (live chat, messages, support, tickets), fitting the 3 anchor rather than 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	"Crisp integration" names a specific platform with distinct triggers and minimal overlap risk, matching the 5 anchor's clear niche; it is not merely broad like the 4 anchor.	5 / 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/crisp/SKILL.md
Commit: f484c82

Reviewed: ~14 hours 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.