Name: landing-ai
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

landing-ai

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/landing-ai/SKILL.md

Quality

Content

67%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 action-dense with executable Membrane CLI commands and a clear setup-to-execution workflow including state validation. Main weaknesses are an over-explanatory intro paragraph, a dangling "Step 2" reference, and minor redundancy between the action-discovery sections.

Suggestions

Cut or compress the introductory paragraph describing what Landing AI is, since Claude already knows this; keep only the official docs link if needed.

Fix the workflow numbering: the text references "Step 2" but no Step 1/Step 2 headers exist — renumber sections consistently or relabel the cross-references.

Deduplicate the action-discovery guidance between "Searching for actions" and "Popular actions", and show how to obtain CONNECTION_ID and actionId from prior command output.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Landing AI is ("a platform that helps businesses build and deploy computer vision solutions...") is unnecessary context Claude already knows. It is not a 4 because that intro block is a noticeable instance of over-explanation that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready bash commands for install, login, connection, action discovery, action execution, and proxy requests. It is not a 5 because some placeholders (CONNECTION_ID, actionId, QUERY) are used without showing how to obtain them, and the "Popular actions" section repeats the "Searching for actions" guidance.	4 / 5
Workflow Clarity	The sequence (install, authenticate, ensure connection, poll until READY, discover actions, run) is clear with explicit state handling and a feedback loop for CLIENT_ACTION_REQUIRED. It is not a 5 because the document references "Step 2" and "1b" without a clearly defined Step 1/Step 2 numbering, leaving a navigation gap.	4 / 5
Progressive Disclosure	The content is self-contained with well-organized section headers and no nested external references. It is not a 5 because, at over 50 lines, the simple-skill exception does not apply and the proxy options table plus best practices could be cleanly separated, though structure is otherwise good.	4 / 5
	Total	15 / 20 Passed

Description

61%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 has an explicit "Use when" trigger and a clearly distinct niche via the Landing AI brand, but its capability list is generic and thin on concrete actions. Tightening the "what" with specific operations would lift specificity and completeness.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Landing AI capabilities such as listing datasets, labeling images, training models, or deploying model versions.

Add natural trigger synonyms users might say (e.g., "computer vision", "visual inspection", "manufacturing defect detection") to broaden trigger_term_quality.

Include reference to file types or API objects (datasets, models, labels) to make the "what" more tangible and distinctive.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Landing AI integration") but the actions are minimal and generic ("Manage data, records, and automate workflows"), lacking concrete operations. It is below the midpoint because no specific capabilities like model training, dataset labeling, or deployment are stated.	2 / 5
Completeness	It states both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Landing AI data"). It is not a 5 because the "what" is vague rather than listing concrete capabilities, and not a 3 because the "when" clause is explicitly present.	4 / 5
Trigger Term Quality	It includes the natural term "Landing AI" and "data", but misses common variations, synonyms, or specific trigger phrases users might say. It is not a 4 because keyword coverage is thin rather than merely missing a few terms.	3 / 5
Distinctiveness Conflict Risk	Naming "Landing AI" explicitly establishes a clear niche with a distinct trigger unlikely to collide with other skills. It matches the anchor for minimal conflict risk.	5 / 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/landing-ai/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.