Name: delighted
Rating: 55.2 (1 reviews)
Author: membranedev

delighted

Delighted integration. Manage data, records, and automate workflows. Use when the user wants to interact with Delighted data.

Quality

62%

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/delighted/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.

The content is a well-structured, largely executable guide to driving Delighted through the Membrane CLI, with a clear connection workflow and validation checkpoints. It would improve by trimming concept explanations and turning the "Popular actions" heading into actual Delighted-specific examples.

Suggestions

Cut the introductory paragraph explaining what Delighted/NPS/CSAT are and the "so you can focus on the integration logic" aside; assume Claude's knowledge and lead with the workflow.

Populate "Popular actions" with concrete Delighted examples (e.g. list survey responses, retrieve a person, send a survey) instead of only the generic discovery command.

Label the workflow steps consistently (Step 1, Step 2) so the "skip to Step 2" reference resolves to a clearly named section.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, but the opening paragraph explains what Delighted, NPS, and CSAT are (concepts Claude already knows) and includes asides like "so you can focus on the integration logic rather than auth plumbing", placing it at mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides concrete executable commands for install, auth, connection, polling, action search/run, and proxying, but the "Popular actions" section delivers only a discovery command rather than Delighted-specific action examples, leaving a minor gap.	4 / 5
Workflow Clarity	The connection setup is a clear sequence with validation checkpoints (poll until state leaves BUILDING) and a feedback loop (re-poll after the user completes a client action), with a documented READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state machine; minor gap is the "skip to Step 2" reference to an unlabeled section.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well organized with clear section headers and no nested or buried references; the proxy flag table and clientAction state machine are somewhat detailed to keep inline, but overall structure and placement are good.	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 adequately complete with both a what and an explicit when clause, and the Delighted brand keeps it reasonably distinct. Its main weakness is generic capability language and missing natural trigger synonyms like surveys, NPS, and customer feedback.

Suggestions

Replace generic actions with concrete Delighted operations, e.g. "Collect survey responses, retrieve NPS/CSAT scores, and manage people and survey records."

Add natural trigger terms users would say, such as "Use when the user wants to send surveys, check NPS or CSAT scores, or work with Delighted customer feedback."

Differentiate from sibling integrations by leading with the Delighted-specific capability (surveys/NPS) rather than the generic "Manage data, records, and automate workflows" template.

Dimension	Reasoning	Score
Specificity	It names the Delighted domain but the listed actions ("Manage data, records, and automate workflows") are generic rather than concrete Delighted-specific operations like sending surveys or retrieving NPS responses, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It explicitly states both what it does ("Delighted integration. Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Delighted data"), but the when clause could be more specific, matching the anchor for both present with room for greater specificity.	4 / 5
Trigger Term Quality	It includes the core keyword "Delighted" and a trigger phrase ("interact with Delighted data") but omits common natural synonyms a user would say such as surveys, NPS, CSAT, or customer feedback, so it sits at the anchor for missing common variations.	3 / 5
Distinctiveness Conflict Risk	The "Delighted" brand name gives it a clear niche and distinct trigger, but the generic "Manage data, records, and automate workflows" phrasing overlaps with sibling Membrane integration skills, yielding minor overlap risk rather than minimal.	4 / 5
	Total	13 / 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/delighted/SKILL.md
Commit: f484c82

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