Name: flyio
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

flyio

Fly.io integration. Manage Organizations. Use when the user wants to interact with Fly.io data.

Quality

66%

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/flyio/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 commands and a thorough actions table, and it is well structured, but it lacks validation/verification guidance for the destructive operations it exposes. Adding pre-flight confirmation for deletions would lift workflow clarity.

Suggestions

Add an explicit validation/confirmation step before destructive actions (e.g., list the app's resources and require user confirmation before `delete-app`).

Clarify the step numbering in the connection flow (the body references "Step 2" and "1b" without a matching "Step 1a"/"Step 2" header).

Consider moving the popular-actions and proxy-flag reference tables into a separate reference file to keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command references and tables, with only minor over-explanation such as the opening "Fly.io is a platform..." paragraph and the "focus on the integration logic rather than auth plumbing" phrasing that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for every step (login, connection ensure, action list/run, request proxy) plus a comprehensive 20-row actions table, fully covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear retry loop (poll again until state is READY), but the skill exposes destructive operations (delete-app, delete-machine, delete-volume, delete-secret) with no validation or confirmation guidance, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is organized into clearly headed sections with no nested references, but the large inline popular-actions and proxy-flag tables could be split into a reference file, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

57%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 is third-person, includes an explicit "Use when" trigger, and is clearly scoped to Fly.io, but it is thin on concrete capabilities and natural trigger terms. Expanding the action list and trigger phrasing would raise specificity and completeness.

Suggestions

Add 2-3 concrete actions to the description (e.g., deploy apps, manage machines and volumes, set secrets) instead of the single "Manage Organizations".

Broaden trigger phrasing to cover the main use cases (e.g., "Use when deploying or managing Fly.io apps, machines, volumes, or secrets").

Replace the generic "interact with Fly.io data" with specific nouns users would actually say (apps, machines, volumes, deployments).

Dimension	Reasoning	Score
Specificity	The description names the Fly.io domain but offers only one concrete action ("Manage Organizations") while the rest ("interact with Fly.io data") is generic, and it under-represents the apps/machines/volumes capabilities the body actually covers.	2 / 5
Completeness	It states what ("Fly.io integration. Manage Organizations.") and an explicit when ("Use when the user wants to interact with Fly.io data"), but the when could be more specific about deploy/machine/volume triggers, so it is not a 5.	4 / 5
Trigger Term Quality	"Fly.io" is a natural term users would say, but the description relies on it almost exclusively with no synonyms or common variations, matching the anchor for some relevant keywords with gaps.	3 / 5
Distinctiveness Conflict Risk	"Fly.io" pins a clear niche with low conflict risk, though the generic "Manage Organizations" phrasing leaves minor overlap with other infra/deployment skills, keeping it just below a 5.	4 / 5
	Total	13 / 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/flyio/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.