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

Blog Docs Log in Get started

clari

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

Quality

63%

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

Quality

Content

63%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 actionable with concrete commands and a clear, checkpointed workflow including error-state feedback loops. Its weaknesses are moderate verbosity from a marketing-style intro and a single-file structure that inlines reference-grade material rather than splitting it out.

Suggestions

Trim the opening Clari overview paragraph or move it to an external doc link; keep the body focused on integration steps Claude doesn't already know.

Move the detailed connection-state handling and the proxy flags table into separate reference files linked from the body to improve progressive disclosure.

Resolve the inconsistent step numbering ('Step 2', '1b') into a single clear ordered sequence to remove the minor workflow gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening Clari marketing paragraph and repeated action-list commands add padding that could be tightened, fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, executable membrane commands (login, connection ensure, action run, request) covering common cases with only minor gaps like the CONNECTION_ID placeholder, matching the 'mostly executable guidance' anchor.	4 / 5
Workflow Clarity	There is a clear install→auth→connect→search→run sequence with polling checkpoints and error-state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED), though the 'Step 2' and '1b' references introduce minor sequencing gaps.	4 / 5
Progressive Disclosure	The content is a single well-sectioned file with clear headers and no nested references, but bulk material (the proxy flag table, detailed state handling) is inlined rather than split into reference files, fitting the 'some structure, could be better organized' anchor.	3 / 5
	Total	14 / 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 is solid: it covers both what and when, and its Clari-specific framing gives it a clear niche. Its main weakness is generic action verbs and limited trigger-term variety rather than concrete, varied natural phrases.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Clari-specific actions (e.g., 'query opportunities, update account records, automate forecast workflows').

Add natural trigger synonyms and file/term variations users would actually say (e.g., 'opportunities, accounts, forecasting, revenue data').

Make the 'Use when' clause more specific to Clari use cases rather than the generic 'interact with Clari data'.

Dimension	Reasoning	Score
Specificity	The description names the Clari domain and a couple of actions ('Manage data, records, and automate workflows') but the actions are generic rather than comprehensive, matching the '1-2 concrete actions' anchor.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Clari data'), but the trigger could be more specific, matching the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Clari', 'data', 'records', and 'workflows' provide some relevant keywords, but common natural variations or synonyms a user would say are missing, fitting the 'some relevant keywords' anchor.	3 / 5
Distinctiveness Conflict Risk	The description is anchored to a specific app (Clari), giving it a clear niche with minor overlap risk, though the generic 'manage data, records' phrasing keeps it just below the distinct-trigger anchor.	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/clari/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.