Name: klenty
Rating: 64 (1 reviews)
Author: membranedev

klenty

Klenty integration. Manage Persons, Organizations, Deals, Leads, Pipelines, Activities and more. Use when the user wants to interact with Klenty data.

Quality

76%

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

This is a strong, command-driven integration guide that is highly actionable and clearly sequenced with a real error-recovery loop for connection state. The only weaknesses are minor: light marketing padding at the top and no validation guard around the destructive prospect actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but the opening product/marketing paragraph ("Klenty is a sales engagement platform...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands for every stage — install, login, connection ensure/get, action list/run with JSON input, and proxy requests — plus a popular-actions table and flag reference covering the common cases.	5 / 5
Workflow Clarity	The connect→poll-state→search→run sequence is clearly laid out with an explicit feedback loop (re-poll after CLIENT_ACTION_REQUIRED), but destructive actions surfaced in the table (unsubscribe, mark-do-not-contact, stop-cadence, remove-tags) run without a verify-before-execute checkpoint.	4 / 5
Progressive Disclosure	The single file is well-organized under clear section headers with no nested references, but the 16-row popular-actions table is a chunk that could live in a separate reference file, leaving a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

71%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 specific, complete, and highly distinctive thanks to the Klenty product name, but its trigger guidance relies on a single keyword and generic "interact with Klenty data" phrasing rather than richer natural triggers. It scores well overall with room to improve trigger-term breadth and the specificity of the when clause.

Suggestions

Add natural trigger synonyms to the when clause, e.g. "Use when managing Klenty prospects, cadences, sales outreach, or sales engagement data."

Replace the single verb "Manage" with a few concrete actions (e.g. "Create and update prospects, start and stop cadences, fetch email engagements") to push specificity toward comprehensive coverage.

Drop the "and more" hedge or pair it with a concrete example so the scope reads as deliberate rather than open-ended.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Leads, Pipelines, Activities and more" names several concrete entities, but a single generic verb (Manage) applied across them and the "and more" hedge leave minor coverage gaps rather than comprehensive multi-action coverage.	4 / 5
Completeness	It explicitly answers both what ("Manage Persons, Organizations, Deals...") and when ("Use when the user wants to interact with Klenty data"), but the when clause is a single generic phrase rather than the concrete multi-trigger phrasing of a level-5 anchor.	4 / 5
Trigger Term Quality	The natural trigger is essentially the single app name "Klenty" ("interact with Klenty data"); common synonyms a user might say — sales engagement, cadence, prospecting, outreach — are absent, so coverage is relevant but missing variations.	3 / 5
Distinctiveness Conflict Risk	"Klenty integration... interact with Klenty data" carves out a clear niche around a distinctive product name, with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/klenty/SKILL.md
Commit: f484c82

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