Name: kadoa
Rating: 58.4 (1 reviews)
Author: membranedev

kadoa

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

Quality

67%

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

Quality

Content

68%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 SKILL.md body is actionable and reasonably concise, built around concrete Membrane CLI commands and clear tables. Its main gaps are the absence of validation feedback loops around destructive/batch workflow actions and some minor over-explanation that could be trimmed.

Suggestions

Add an explicit validate/verify checkpoint before destructive or batch actions (e.g., confirm a workflow ID via get-workflow before delete-workflow, and check the returned run state after run-workflow).

Tighten or remove narrative padding such as the "so you can focus on the integration logic rather than auth plumbing" aside.

Resolve the mismatch between the intro paragraph ("cloud infrastructure spend") and the actual Kadoa capabilities (web-scraping/extraction workflows) shown in the actions table to avoid confusing the model.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and compact tables with only minor padding (e.g., "so you can focus on the integration logic rather than auth plumbing"), so it is broadly efficient despite a few trimmable phrases.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxy requests, plus flag tables — strong executable guidance with minor gaps such as no example of interpreting a run's output.	4 / 5
Workflow Clarity	The connection flow has a clear state-driven sequence (ensure, poll until READY, handle CLIENT_ACTION_REQUIRED), but destructive/batch actions like delete-workflow and run-workflow lack any validation or verify-then-proceed feedback loop, capping this dimension at 3.	3 / 5
Progressive Disclosure	The single-file body is well sectioned with clear headers and inline quick-reference tables; there are no bundle files to split into, so the inlined 12-row action table is acceptable organization with only minor gaps.	4 / 5
	Total	15 / 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 identifies a clear, distinct niche (Kadoa) and includes an explicit "Use when..." clause, satisfying both what and when. Its main weakness is a generic "Manage" verb and limited trigger-term variation, which keep specificity and trigger quality in the mid range.

Suggestions

Replace the generic verb "Manage" with concrete actions per entity (e.g., "Create and update Leads, search Persons, log Activities").

Expand trigger terms beyond the platform name to natural phrases users would say (e.g., "Kadoa leads", "Kadoa workflows", "extract data with Kadoa").

Drop the vague "and more" tail or replace it with the remaining specific capabilities to avoid over-claiming.

Dimension	Reasoning	Score
Specificity	It names the domain and six concrete entity types ("Leads, Persons, Organizations, Deals, Projects, Activities"), but the only action verb is the generic "Manage ... and more", so coverage of actual actions is not comprehensive.	3 / 5
Completeness	Both "what" (Kadoa integration managing leads/persons/etc.) and "when" ("Use when the user wants to interact with Kadoa data") are present, though the "when" clause is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural keyword "Kadoa" appears in the trigger clause ("Use when the user wants to interact with Kadoa data"), but there are no synonyms, file extensions, or common variations beyond the platform name.	3 / 5
Distinctiveness Conflict Risk	"Kadoa" is a specific named platform with a clear niche, so the description is unlikely to trigger for the wrong skill and carries minimal conflict risk.	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/kadoa/SKILL.md
Commit: f484c82

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