Name: clarify
Rating: 61.6 (1 reviews)
Author: membranedev

clarify

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

Quality

72%

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

Quality

Content

82%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 highly actionable, providing fully executable CLI commands with an explicit feedback loop for the fragile connection step, and is well-organized into clear sections. It is slightly held back by minor verbosity and loose workflow numbering.

Suggestions

Tighten the intro and remove filler like "so you can focus on the integration logic rather than auth plumbing" to improve conciseness.

Replace the loose "skip to Step 2" references with an explicit numbered master sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run) to strengthen workflow clarity.

Consider moving the proxy flag reference table into a separate reference file so the SKILL.md overview stays leaner.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal padding, but contains minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing" and a brief product-background intro that could be trimmed, fitting the efficient-with-minor-trim anchor.	4 / 5
Actionability	It provides copy-paste-ready commands covering install, login (including headless), connection ensure, state polling, action list/run with JSON input, and proxy requests with a full flag table, fully executable and covering the common cases.	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear and the connection-polling section has an explicit validate/handle-CLIENT_ACTION_REQUIRED/re-poll feedback loop, but the overall flow uses loose "skip to Step 2" numbering without a labeled Step 2 header, leaving minor structure gaps that keep it below a 5.	4 / 5
Progressive Disclosure	No bundle files exist and the body is self-contained with clean section headers (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) and no nested references; it is well-organized though everything is inline in ~145 lines, fitting good-structure-with-minor-organization-gaps rather than an ideal overview-pointing-to-detail split.	4 / 5
	Total	17 / 20 Passed

Description

62%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 successfully includes both a what and a Use-when clause and is anchored by a distinct brand name, but its actions and triggers are generic and circular rather than concrete. Tightening the actions and triggers to reflect Clarify's actual support domain would lift the weaker dimensions.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with Clarify-specific ones like "manage support conversations, create and assign tasks, and automate support workflows".

Expand the when-clause with concrete trigger phrases, e.g. "Use when the user wants to manage Clarify support conversations, tasks, or customer records."

Add natural synonyms a user would say (support tickets, helpdesk, customer messages) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names 2-3 actions but they are generic rather than specific to Clarify's support domain (conversations, tasks), matching the anchor that names the domain with a couple concrete actions but is not comprehensive.	3 / 5
Completeness	It states both a clear "what" ("Clarify integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Clarify data."), but the when-clause is generic and circular rather than naming concrete trigger situations, so it stops below a 5.	4 / 5
Trigger Term Quality	The only real trigger term is the brand name "Clarify" in "interact with Clarify data"; it omits natural phrases a user would say like support, tickets, conversations, or tasks, fitting the anchor with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The explicit "Clarify" branding gives it a distinct niche trigger with only minor overlap risk, though the generic "manage data, records, automate workflows" phrasing could brush against other data/automation skills.	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/clarify/SKILL.md
Commit: f484c82

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