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

leadoku

Leadoku integration. Manage Leads, Persons, Organizations, Deals, Pipelines, Users and more. Use when the user wants to interact with Leadoku 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/leadoku/SKILL.md

Quality

Content

61%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 practical, command-driven CLI skill that is mostly executable and well-structured. Its weaknesses are unnecessary marketing prose, broken 'Step 2' cross-references, and missing validation guidance for destructive proxy operations.

Suggestions

Remove the marketing intro paragraph ('Leadoku is a lead generation...') and the auth-plumbing rationale; Claude only needs the commands.

Label the workflow steps explicitly (Step 1: Connect, Step 2: Search actions, Step 3: Run) so the 'skip to Step 2' references resolve, and add a validation/dry-run step before destructive proxy calls (e.g. GET before DELETE/PUT).

Fix the 'Official docs' URL, which currently points to HubSpot (developers.hubspot.com) rather than Leadoku.

Dimension	Reasoning	Score
Conciseness	The bulk is tight command examples and flag tables, but the opening marketing paragraph ('Leadoku is a lead generation and sales automation platform...') and rhetorical phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands with real flags for install, auth, connect, search, run, and proxy, plus a flag reference table; minor gaps remain (only two example actions, and placeholders like CONNECTION_ID/<actionId> require substitution).	4 / 5
Workflow Clarity	A reasonable state-machine sequence with polling feedback loops exists, but the 'skip to Step 2' references are unlabelled, and the proxy path supports destructive verbs (DELETE/PUT) with no explicit verification step, which caps this dimension at 3.	3 / 5
Progressive Disclosure	The single-file body is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); it is not a 5 because no content is split into one-level-deep reference files and the file runs ~150 lines.	4 / 5
	Total	14 / 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.

A solid, product-scoped description that explicitly states both capability and trigger. It is held back from the top band by a single generic action verb, vague 'and more' padding, and a slightly circular trigger clause.

Suggestions

Replace the generic verb 'Manage' with specific actions, e.g. 'Create, update, search, and delete Leads, Persons, Organizations, Deals, Pipelines, and Users'.

Drop the vague 'and more' and make the trigger clause concrete, e.g. 'Use when the user wants to create or update leads, track deals, or manage pipelines in Leadoku'.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists concrete entity objects ('Leads, Persons, Organizations, Deals, Pipelines, Users') but relies on a single generic action verb ('Manage') plus vague 'and more', so it stops short of listing several specific actions.	3 / 5
Completeness	It answers both 'what' (manage the listed entities) and 'when' ('Use when the user wants to interact with Leadoku data'), but the 'when' clause is somewhat circular and could name concrete triggering tasks.	4 / 5
Trigger Term Quality	It surfaces several natural CRM keywords a user would actually say ('Leads', 'Deals', 'Pipelines', 'Organizations') and ties the trigger to Leadoku, though it lacks synonyms/file-extension-style variations.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Leadoku' and scoping the trigger to 'interact with Leadoku data' gives it 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/leadoku/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.