Name: preflight
Rating: 55.2 (1 reviews)
Author: membranedev

preflight

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

Quality

63%

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

Quality

Content

63%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 executable CLI commands and a clear state-driven connection workflow, but it carries some unnecessary explanatory padding and keeps all material inline rather than splitting detailed reference content into separate files. It is a strong, practical skill body with room to tighten prose and improve file structure.

Suggestions

Trim editorial padding like 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' to improve token efficiency.

Move the proxy options table and full clientAction state details into a separate reference file and link to it from SKILL.md.

Add an explicit validate-and-retry checkpoint for destructive actions (e.g. after running an action that modifies PreFlight data, verify the result before proceeding).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and examples, but includes some unnecessary padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready executable commands for install, auth, connecting, polling, searching, running actions, and proxying requests, with only minor gaps such as unspecified placeholder values.	4 / 5
Workflow Clarity	The connection workflow has a clear state-driven sequence (READY / BUILDING / CLIENT_ACTION_REQUIRED) with a polling loop and explicit next-steps per state, though it stops short of a full validate-fix-retry checklist.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections, but everything lives inline in a single SKILL.md with no external reference files, so large reference-style content (the proxy options table, full state details) is not split out.	3 / 5
	Total	14 / 20 Passed

Description

62%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 names the target platform and includes an explicit 'Use when' trigger, satisfying both what and when, but its action verbs are generic and it lacks the concrete PreFlight-specific capabilities that would make it truly distinctive. It is solid but could be sharpened with platform-specific trigger terms.

Suggestions

Replace generic verbs ('Manage data, records') with concrete PreFlight capabilities such as 'run flights, view check results, and manage compliance scans'.

Expand the trigger clause with natural user phrases like 'Use when the user wants to run PreFlight checks, view flight details, or check compliance status before deployment'.

Add file-extension or object synonyms (flights, checks, scans) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the PreFlight domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive — it does not list concrete PreFlight capabilities such as flights, checks, or compliance results.	3 / 5
Completeness	Provides both a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with PreFlight data'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the natural keyword 'PreFlight' and the phrase 'interact with PreFlight data', but misses common synonyms or variations a user might actually say (e.g. flights, compliance checks, scans).	3 / 5
Distinctiveness Conflict Risk	The named product 'PreFlight' gives it a clear niche with distinct triggers and minimal conflict risk, though the generic action verbs leave minor overlap with other data-management skills.	4 / 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/preflight/SKILL.md
Commit: f484c82

Reviewed: 5 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.