Name: zendesk-sunshine
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

zendesk-sunshine

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/zendesk-sunshine/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 body is highly actionable with concrete, executable Membrane CLI commands and a well-sequenced connection workflow with state-based feedback loops. It would improve by trimming the conceptual intro and adding explicit validation around action execution and a genuinely populated Popular actions section.

Suggestions

Remove or condense the opening paragraph explaining what Zendesk Sunshine is; Claude already knows, and it competes with the context window.

Populate the "Popular actions" section with 2-3 concrete named actions (e.g. create record, list relationship records) with example commands instead of repeating the discovery command.

Add an explicit validation/verification checkpoint after running actions (e.g. check the response `output`/error fields and retry or surface `clientAction` to the user) to lift workflow clarity toward a feedback-loop standard.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows ("Zendesk Sunshine is a CRM platform that allows businesses to build custom apps...") and light padding ("so you can focus on the integration logic rather than auth plumbing"), matching the level-3 anchor; not lean enough for level-4.	3 / 5
Actionability	Provides mostly executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flags and JSON examples, with minor gaps such as unresolved placeholders and a "Popular actions" section that repeats the discovery command instead of naming specific actions.	4 / 5
Workflow Clarity	Clear sequence from install to authenticate to connect to search to run, with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback loops for the connection step; not a level-5 because the overall run-action flow lacks explicit validation checkpoints.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized with clear section headers (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) giving good structure and easy navigation, matching the level-4 anchor with minor organization gaps.	4 / 5
	Total	15 / 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 cleanly answers both what and when and targets a distinct, named-product niche. Its main weakness is generic action wording and limited trigger-term coverage (no synonyms or extension keywords).

Suggestions

Replace generic verbs ("Manage data, records") with concrete actions tied to Sunshine's model, e.g. "Create and update custom object records, manage relationships, and trigger automations."

Expand the trigger clause with natural synonyms users say, e.g. "Use when the user wants to work with Zendesk Sunshine data, custom objects, or relationship records."

Keep the third-person voice already used; ensure the "when" clause names the specific entities (records, relationships) rather than just "data".

Dimension	Reasoning	Score
Specificity	Names the domain ("Zendesk Sunshine integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete; not a level-4 list of several specific actions, and clearly above the single-action level-2.	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Zendesk Sunshine data"), but the "when" is generic so it is not the fully specific level-5; it is above level-3 where "when" is absent.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Zendesk Sunshine data" gives a relevant natural term ("Zendesk Sunshine") but misses common synonyms and extension keywords (CRM, custom objects, relationships), matching the level-3 anchor with some keywords and missing variations.	3 / 5
Distinctiveness Conflict Risk	"Zendesk Sunshine integration" names a specific product niche with a distinct trigger, giving minimal conflict risk with other skills, matching the level-5 anchor for a clear niche.	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/zendesk-sunshine/SKILL.md
Commit: f484c82

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