Name: kommo
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

kommo

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

Quality

74%

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/kommo/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 body is highly actionable with executable commands and a clear connection workflow, well-structured as a single overview file. The main gaps are minor: a few trimmable asides and the absence of an explicit error-recovery checkpoint when running actions or proxying requests.

Suggestions

Add a short validation/error-recovery note after `membrane action run` and `membrane request` (e.g. check the `output`/error fields and retry or surface `clientAction` guidance on failure) to close the workflow-clarity gap.

Trim editorial asides ("rather than auth plumbing", "burn less tokens") and de-duplicate the Kommo Overview entity list to tighten conciseness and structure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands, but includes minor padding such as "so you can focus on the integration logic rather than auth plumbing" and "This will burn less tokens and make communication more secure." Not a 5 because of these trimmable asides; not a 3 because the bulk is lean and assumes Claude's competence.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the common cases (login, connection ensure, action list/run, request proxy) plus a concrete options table. Not a 4 because there are no significant gaps in the executable guidance.	5 / 5
Workflow Clarity	Clear install→authenticate→connect→discover→run sequence with a feedback loop for connection states (poll again after CLIENT_ACTION_REQUIRED, handle CONFIGURATION_ERROR). Not a 5 because the "Running actions" and "Proxy requests" sections lack an explicit validation/error-recovery checkpoint for failed action execution.	4 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear sections and no nested references; no bundle files exist so everything is appropriately inline. Not a 5 because the "Kommo Overview" list is redundantly nested (Lead/Contact/Company/Task repeated under Lead) and there is no "for X see Y" navigation to the official docs beyond a single top link.	4 / 5
	Total	17 / 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 answers both what and when and is clearly distinct thanks to the named Kommo product, but its actions are generic and trigger keyword coverage is limited to the single term "Kommo." Tightening action verbs and adding concrete trigger phrases would lift it.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with specific capabilities, e.g. "Create and update leads, contacts, and tasks; manage pipelines and catalogs; automate sales workflows."

Expand the trigger clause with concrete phrases users actually say, e.g. "Use when the user wants to manage Kommo leads, contacts, deals, tasks, or CRM workflows."

Dimension	Reasoning	Score
Specificity	Names the domain (Kommo) and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, so coverage is not comprehensive. Not a 2 because multiple actions are named; not a 4 because they lack specificity.	3 / 5
Completeness	Both what ("Kommo integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Kommo data.") are explicitly present, but the when could be more specific with concrete trigger phrases. Not a 5 because it lacks multiple concrete trigger phrases; not a 3 because when is explicit, not merely implied.	4 / 5
Trigger Term Quality	The only natural keyword is "Kommo" / "Kommo data" in the trigger clause; common variations or synonyms a user might say are missing. Not a 4 because keyword coverage is thin; not a 2 because "Kommo" is a specific, natural term rather than generic language.	3 / 5
Distinctiveness Conflict Risk	The named product (Kommo) with an explicit "interact with Kommo data" trigger carves a clear niche with minimal overlap risk. Not a 4 because the product name makes the niche unambiguous rather than only "mostly distinct."	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/kommo/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.