Name: kombo
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

kombo

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

Quality

72%

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/kombo/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, dominated by executable CLI commands and a clear connection-to-execution workflow with state-based feedback loops. The main improvements are trimming the introductory prose and adding post-action validation guidance.

Suggestions

Tighten the opening "Kombo is a unified API..." paragraph and the auth-plumbing aside to assume Claude's familiarity and save tokens.

Add a brief validation/verification step after running actions (e.g. inspect the response `output` field and handle error states) to close the workflow-clarity gap.

Consider moving the detailed `clientAction` state reference and the proxy flags table into a reference file to deepen progressive disclosure, since the file is fairly long.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-driven with tables and bash snippets, but the opening "Kombo is a unified API..." paragraph and the auth-plumbing aside add minor over-explanation that could be trimmed, fitting the efficient-with-minor-padding anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests plus a flags table, covering the common cases with executable guidance, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The install→auth→connect→search→run→proxy sequence is clear and includes polling-based validation checkpoints with explicit state branching (READY/BUILDING/CLIENT_ACTION_REQUIRED), but there is no validation guidance after running actions, leaving a minor checkpoint gap at the mostly-checkpoints anchor.	4 / 5
Progressive Disclosure	The skill is a single well-sectioned file with clear headings and no nested references, which is reasonable given no bundle files exist; some detailed content (clientAction states, proxy flags) could be split out, matching the good-structure-with-minor-gaps anchor.	4 / 5
	Total	17 / 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 successfully pairs a clear domain with an explicit "Use when" trigger, but relies on generic action verbs that under-specify what the skill actually does. Tightening the action list and adding concrete Kombo-specific triggers would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Kombo operations such as "query Kombo records, run Kombo actions, and proxy requests to the Kombo API".

Expand the trigger clause with natural phrases users would say, e.g. "Use when the user wants to query, create, or update Kombo records or run Kombo SaaS actions."

Add a distinguishing cue (e.g. the SaaS-integration/unified-API angle) to reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the Kombo domain and lists several actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete operations, fitting the anchor that names domain plus a couple of actions without comprehensive coverage.	3 / 5
Completeness	It states both what it does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Kombo data"), with the explicit "Use when" clause allowing it above 3; the trigger could be more specific, matching the anchor for both present but imperfect.	4 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Kombo data" surfaces the natural keyword "Kombo", but it lacks common variations or synonyms, matching the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named Kombo platform gives it a distinct niche with minimal conflict risk, though the generic "manage data, records" phrasing leaves minor overlap with other data-oriented skills, matching the mostly-distinct 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/kombo/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.