Name: leap
Rating: 60.8 (1 reviews)
Author: membranedev

leap

Leap integration. Manage Organizations, Pipelines, Projects, Users, Goals, Filters. Use when the user wants to interact with Leap data.

Quality

71%

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/leap/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.

A highly actionable, well-structured CLI guide with concrete commands throughout. Its main weaknesses are an unnecessary background intro paragraph and the absence of validation checkpoints around the destructive actions it advertises.

Suggestions

Cut the opening background paragraph ("Leap helps automate repetitive tasks...Think of it as a no-code automation platform") and other padding; assume Claude knows what the product is.

Add a validation/verification step to the 'Running actions' workflow, especially for destructive actions like delete-model and delete-image-job (e.g., confirm the output, check for error fields, list to verify).

Fix the broken 'skip to Step 2' reference by labeling the downstream steps (e.g., 'Step 2: Search for actions') so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient CLI commands and tables, but the opening paragraph ("Think of it as a no-code automation platform...") and a few lines like "so you can focus on the integration logic rather than auth plumbing" are background padding Claude does not need.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover every common case (install, login, connection ensure, poll, action search/run with JSON input, proxy with a complete flag table) and the popular-actions table supplies real action keys.	5 / 5
Workflow Clarity	There is a clear sequence with a real feedback loop (poll connection state, act, re-poll), but the popular-actions catalog includes destructive operations (delete-model, delete-image-job) and the 'Running actions' workflow has no validation/verification step, capping this dimension at 3.	3 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and easy navigation, and no external references are needed; minor gaps are the broken 'skip to Step 2' cross-reference and no split-out file for the action catalog.	4 / 5
	Total	15 / 20 Passed

Description

75%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, third-person description that pairs a concrete list of managed Leap resources with an explicit 'Use when' trigger. It is held back from the top band by a single generic verb and a generic trigger clause rather than concrete trigger phrases.

Suggestions

Replace the single generic verb 'Manage' with several specific actions (e.g., 'Create, list, update, and delete Organizations, Pipelines, Projects...') to raise specificity.

Expand the 'when' clause into concrete trigger phrases, e.g., 'Use when the user wants to create Leap pipelines, list projects, or manage users and goals.'

Add natural synonyms / domain terms users might say (e.g., 'workflows', 'automation', 'Leap AI') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Enumerates six concrete resource types ("Organizations, Pipelines, Projects, Users, Goals, Filters") giving clear capability scope, though the single generic verb "Manage" keeps it just below comprehensive.	4 / 5
Completeness	Both a clear "what" (manage the listed entities) and an explicit "Use when the user wants to interact with Leap data" clause are present, but the trigger is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"Leap" plus the entity nouns (Pipelines, Projects, Goals) are natural terms a user would say, but coverage lacks synonyms or variations and "interact with Leap data" is generic.	4 / 5
Distinctiveness Conflict Risk	The distinct "Leap" brand name gives a clear niche with minimal conflict risk, though the generic entity nouns leave minor overlap with other project-management skills.	4 / 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/leap/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.