Name: kite-suite
Rating: 60.8 (1 reviews)
Author: membranedev

kite-suite

Kite Suite integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Kite Suite 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/kite-suite/SKILL.md

Quality

Content

75%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.

A well-structured, actionable CLI integration guide with strong sequencing and state-based validation for the connection setup flow. Its weaker spots are minor: a trimmable overview paragraph, abstract placeholders in a few commands, inconsistent step numbering, and inlined reference tables that a larger skill would split out.

Suggestions

Tighten the opening overview paragraph and drop justifying clauses ('so you can focus on the integration logic rather than auth plumbing') that restate what the commands already show.

Resolve the inconsistent step references (the 'Step 2' / '1b' labels) into a single coherent numbered sequence, and add an explicit verify step after `membrane action run` and proxy requests.

Consider moving the popular-actions table and proxy flag reference into a separate reference file and linking from the overview, improving navigation as the skill grows.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and largely lean, but includes mild padding Claude doesn't need — the opening 'Kite Suite is a sales engagement platform...' overview and a few justifying sentences ('so you can focus on the integration logic rather than auth plumbing').	4 / 5
Actionability	Provides copy-paste-ready commands for the common cases (login, connection ensure, action run with --input JSON, proxy flags) and a concrete popular-actions table, but some parameters stay abstract (intent "QUERY", <actionId> placeholders) leaving minor gaps versus fully specified examples.	4 / 5
Workflow Clarity	A clearly sequenced install→login→connect→poll→search→run flow with explicit state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/error) and re-polling feedback, but the run/proxy stages lack a verify-success loop and section numbering is inconsistent ('Step 2' referenced, flow labeled '1b').	4 / 5
Progressive Disclosure	Clean header-based structure with no nested-reference anti-pattern, and no bundle files exist to mis-signal; however the popular-actions table and proxy flag reference are inlined rather than split into a separate reference file, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

67%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.

A solid description that states both capabilities and a use-trigger, anchored to a distinctive product name. Its main weakness is trigger-term breadth — the 'when' clause is generic and the entity list reads as domain nouns rather than natural user phrases.

Suggestions

Replace the generic 'Use when the user wants to interact with Kite Suite data' with concrete trigger phrases users would actually say (e.g., 'Use when the user asks to list Kite Suite pipelines, manage organizations, or query users/goals/filters').

Vary the verbs beyond a single 'Manage' to surface distinct concrete actions (e.g., 'List, create, and update Organizations, Pipelines, Users, Goals, and Filters').

Add common synonyms/file-format or noun variations a user might say to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Kite Suite domain and lists several concrete manageables (Organizations, Pipelines, Users, Goals, Filters), but the single verb 'Manage' wraps them rather than enumerating distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('Manage Organizations, Pipelines, Users, Goals, Filters') and 'when' ('Use when the user wants to interact with Kite Suite data'), though the 'when' clause is somewhat generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural phrase 'interact with Kite Suite data' and the product name, but the entity list (Organizations, Pipelines...) are domain nouns rather than the trigger phrases a user would naturally say, and common synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The distinct product name 'Kite Suite' carves a clear niche with minimal conflict risk; only slight breadth in 'interact with Kite Suite data' keeps it from a 5.	4 / 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/kite-suite/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.