Name: leadoo
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

leadoo

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

Quality

78%

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/leadoo/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 strong connection-state validation loop, weakened only by a marketing-fluff intro and broken step cross-references. It is well-organized for a single-file integration skill.

Suggestions

Fix the dangling step references: "skip to Step 2" and "#### 1b. Wait for the connection" point to steps that do not exist — renumber into a coherent Step 1 / Step 2 sequence or remove the references.

Trim the opening marketing paragraph about what Leadoo is (line 17); Claude does not need the sales pitch to execute the integration.

De-duplicate action discovery: the "Searching for actions" and "Popular actions" sections repeat the `action list` invocation — consolidate into one discovery section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven content, but the opening marketing paragraph ("Leadoo is a website conversion platform that helps businesses identify and engage...") and a few asides ("so you can focus on the integration logic rather than auth plumbing") are over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request) plus a flags table, with clearly marked placeholders for values the agent supplies.	5 / 5
Workflow Clarity	The connection-readiness state machine has explicit validation and a re-poll feedback loop, but the step numbering is broken ("skip to Step 2" and "#### 1b." reference steps that do not exist), introducing a navigation gap.	4 / 5
Progressive Disclosure	Content is well-sectioned in a single file with clear headers; no external reference files are needed since actions are discovered at runtime, though some inline material (e.g. the proxy flags table) could live in a reference if the file grows.	4 / 5
	Total	17 / 20 Passed

Description

73%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 cleanly answers both what and when using a distinctive brand trigger, but its capability list is generic rather than tied to Leadoo's actual features. It is solid but would be sharper with concrete Leadoo-specific actions.

Suggestions

Replace the generic action list ("Manage data, records, and automate workflows") with Leadoo-specific capabilities, e.g. "capture and qualify leads, manage chatbot conversations, retrieve visitor and lead information".

Tighten the "Use when..." trigger to concrete scenarios, e.g. "Use when the user wants to manage Leadoo leads, bots, conversations, or visitor data."

Dimension	Reasoning	Score
Specificity	It names the domain ("Leadoo integration") and lists a few actions ("Manage data, records, and automate workflows"), but those actions are generic rather than Leadoo-specific (e.g. qualifying leads, managing chatbots), so it is not comprehensive.	3 / 5
Completeness	Both "what" (Leadoo integration; manage data, records, workflows) and "when" ("Use when the user wants to interact with Leadoo data") are present, but the trigger is somewhat generic and the "what" could be more concrete.	4 / 5
Trigger Term Quality	Good keyword coverage anchored on the natural brand term "Leadoo" plus use-case terms ("data, records", "workflows", "Leadoo data"); a few natural synonyms or scenario phrases are missing.	4 / 5
Distinctiveness Conflict Risk	The brand-specific trigger "Leadoo" carves out a clear niche 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/leadoo/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.