Name: launch27
Rating: 59.2 (1 reviews)
Author: membranedev

launch27

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

Quality

68%

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

Quality

Content

76%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 content is highly actionable with concrete CLI commands and a well-structured connection workflow, but it lacks validation/verification safeguards around destructive operations and keeps all material inline with no progressive disclosure to reference files.

Suggestions

Add a verification/checkpoint step before destructive or mutating operations, e.g., confirm the action's effect via action list output or a dry-run before running POST/PUT/DELETE proxy requests.

De-duplicate the entity catalog (listed once under Booking and again at top level) and remove the filler line "Use action names and parameters as needed."

Consider moving the detailed clientAction state breakdown and the proxy flag table into a separate reference file, signaled from the main body, to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the entity list is duplicated (nested under Booking and again at top level) and the line "Use action names and parameters as needed." is filler that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready bash commands across install, login, connection ensure/get with --wait, action list/run, and proxy requests with a clear flag table, covering the common integration cases.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but proxy requests expose destructive HTTP methods (PUT/PATCH/DELETE) and action runs can mutate data with no validation or verify step, capping this at 3.	3 / 5
Progressive Disclosure	Clear section headers organize the ~158-line single-file skill well, but there are no external reference files and some inline material (entity catalog, proxy flag table) could be split out for deeper detail.	4 / 5
	Total	16 / 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 cleanly names the target app and gives an explicit use-trigger, but its capability phrasing is vague and lacks the concrete actions and synonym coverage of a top-tier description.

Suggestions

Replace generic verbs with concrete Launch27 actions, e.g. "Create and manage bookings, customers, services, and invoices; sync scheduling and payments."

Broaden trigger terms with natural synonyms such as "cleaning business," "bookings," "appointments," and "scheduling" so users phrasing the need differently still match.

Tighten the "what" so it reads as specific capabilities rather than "Manage data, records, and automate workflows."

Dimension	Reasoning	Score
Specificity	It names the Launch27 domain but the actions ("Manage data, records, and automate workflows") are generic and abstract rather than concrete operations like extract, create, or sync.	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 Launch27 data"), though the "what" is generic rather than concrete.	4 / 5
Trigger Term Quality	"Launch27" / "Launch27 data" gives one solid natural keyword a user would say, but it misses common variations and synonyms (e.g., cleaning, bookings, appointments, scheduling).	3 / 5
Distinctiveness Conflict Risk	Launch27 is a unique named application, giving the skill a clear niche with a distinct trigger ("interact with Launch27 data") and minimal conflict risk with other skills.	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/launch27/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.