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

astronaut

Astronaut integration. Manage data, records, and automate workflows. Use when the user wants to interact with Astronaut 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/astronaut/SKILL.md

Quality

Content

81%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 highly actionable with executable Membrane CLI commands and a clear state-driven connection workflow, staying concise and well-structured without unnecessary concept explanations. The main gap is the absence of explicit validation/feedback checkpoints after running actions or issuing proxy requests.

Suggestions

Add a verification step after `membrane action run` (e.g. inspect the `output` field and handle error states) to close the feedback loop on executed actions.

Include a validation checkpoint before destructive proxy requests (DELETE/PUT) such as confirming the target connection id and endpoint, which would lift workflow_clarity.

Consider moving the proxy options table and clientAction schema into a reference file to keep SKILL.md a lean overview and improve progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and tables rather than explaining concepts Claude already knows; a few lines (e.g. 'Membrane handles authentication... so you can focus on integration logic') are light padding that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection, polling, action search/run, and proxy requests, with a clear options table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit polling and a state-driven decision tree (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) plus re-poll loops, but there is no validation checkpoint after actions run or before destructive proxy requests.	4 / 5
Progressive Disclosure	Content is well-organized into titled sections with no external bundle files present; the proxy option table is appropriately inline. It is one cohesive SKILL.md rather than split across references, but at ~150 lines it stays navigable.	4 / 5
	Total	17 / 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 correctly states what the skill does and when to use it with an explicit 'Use when' clause, but its action list is generic rather than reflecting Astronaut's actual capabilities (missions, training, vehicles). Trigger terms are limited to the product name with no natural synonyms.

Suggestions

Replace generic actions with concrete Astronaut operations, e.g. 'Manage astronaut training, missions, vehicles, and health records' to lift specificity.

Add natural trigger phrases a user would actually say, such as 'astronaut training', 'mission planning', or 'health monitoring', not just 'Astronaut data'.

Tighten distinctiveness by pairing the product name with the domain-specific nouns so it cannot be confused with a generic data-management skill.

Dimension	Reasoning	Score
Specificity	It names the domain ('Astronaut integration') and a couple of generic actions ('Manage data, records, and automate workflows'), but the actions are broad and not the concrete Astronaut operations (missions, astronauts, vehicles).	3 / 5
Completeness	It has a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Astronaut data'); the trigger is slightly generic but both halves are present.	4 / 5
Trigger Term Quality	'Astronaut' and 'Astronaut data' are relevant keywords, but it lacks natural variations a user would say (training, missions, flight planning) and any file extensions or synonyms.	3 / 5
Distinctiveness Conflict Risk	Tying it to the named Astronaut SaaS makes it mostly distinct from other skills, though the generic 'manage data, records, automate workflows' phrasing carries minor overlap risk with general data 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/astronaut/SKILL.md
Commit: f484c82

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