Name: clientify
Rating: 60.8 (1 reviews)
Author: membranedev

clientify

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

Quality

71%

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

Quality

Content

76%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 with executable Membrane CLI commands throughout and a well-structured connection workflow with polling feedback loops. Its main weakness is the absence of validation guidance around destructive delete operations, which caps workflow clarity.

Suggestions

Add a validation/verification step for destructive actions, e.g. confirm the record exists and prompt for confirmation before running delete-deal/delete-company/delete-contact, then verify deletion afterward.

Clarify the actionId vs. Key distinction in the popular-actions table so 'membrane action run <actionId>' maps unambiguously to the listed keys.

Trim the marketing-flavored intro and 'auth plumbing' phrasing to tighten conciseness from 4 toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and tables, with only minor over-explanation (e.g. 'so you can focus on the integration logic rather than auth plumbing' and the marketing-style intro) that could be trimmed, fitting score 4 rather than 5.	4 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxying, plus a concrete actions table and flag reference, fully covering the common cases per the score-5 anchor.	5 / 5
Workflow Clarity	The connect→search→run sequence is clear with state-based polling feedback loops, but destructive operations (delete-deal, delete-company, delete-contact) appear in the action table with no validation or verification checkpoint, capping workflow clarity at 3 per the destructive-ops guideline.	3 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear headed sections covering overview, setup, actions, and best practices; the large inline actions table is borderline but acceptable, giving score 4 rather than 5 since some reference material could live in a separate file.	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 is clear and distinct due to the named Clientify product, with both a 'what' and a 'when' clause. It is weakened by generic action verbs and a thin set of trigger terms that omit common synonyms like CRM, leads, deals, and contacts.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Clientify actions such as 'manage leads, deals, companies, and contacts'.

Expand the trigger clause to include natural terms users say, e.g. 'Use when the user wants to manage Clientify CRM data — leads, deals, contacts, companies, or tasks.'

Add file/record-level specifics (e.g. 'create, update, delete, and list records') to lift specificity from 3 toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the Clientify domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic and coverage is not comprehensive, matching the score-3 anchor rather than the more concrete score-4.	3 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Clientify data'), but the 'when' is generic rather than listing concrete trigger phrases, matching score 4 instead of 5.	4 / 5
Trigger Term Quality	The only natural keyword is 'Clientify' (and 'Clientify data'), which is relevant but misses common variations users would say like CRM, leads, deals, or contacts, so it lands at 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	'Clientify' is a distinct named product, giving it a clear niche with minimal overlap risk versus other skills, matching the score-5 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/clientify/SKILL.md
Commit: f484c82

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