Name: astronomer
Rating: 56.8 (1 reviews)
Author: membranedev

astronomer

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

Quality

65%

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

Quality

Content

67%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 a lean, command-driven integration guide with concrete executable steps and a clear connection workflow including validation checkpoints, held back by minor padding and inconsistent step labeling.

Suggestions

Trim marketing/editorial padding ("so you can focus on the integration logic", "This is the fastest way to get a connection") and the introductory paragraph explaining what Astronomer is, since Claude already knows the platform.

Fix the step numbering: either label an explicit "Step 2" heading or reword the "skip to Step 2" reference and the "1b" subsection into a coherent numbered sequence.

Add at least one fully-worked example with concrete values (a real connection id and action) so the action run and request commands are copy-paste ready end-to-end.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tight explanations, but includes unnecessary padding such as "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", and an introductory paragraph explaining what Astronomer is.	3 / 5
Actionability	It provides concrete, executable commands (npm install, membrane login, connection ensure, action run, request) plus a flags table, but examples rely on placeholders (CONNECTION_ID, actionId, QUERY) without a fully-worked example with real values.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with state-polling validation and a re-auth feedback loop ("After the user completes the action... poll again"), but step labeling is inconsistent ("Step 2" is referenced but never labeled, and "1b" sits oddly).	4 / 5
Progressive Disclosure	The single-file body is well organized into clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no external bundle files; structure is good with only minor organization gaps such as the inlined proxy flags table.	4 / 5
	Total	15 / 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 answers both what and when with an explicit trigger clause tied to a named platform, but the capability phrasing is generic and lacks natural synonyms users would say for the Astronomer/Airflow domain.

Suggestions

Replace generic verbs with concrete Astronomer capabilities the body already lists, e.g. "Manage Deployments, Workspaces, Users, and Tokens, and run actions against Astronomer data."

Add natural trigger terms a user would actually say, such as Airflow, pipelines, DAGs, or deployments, alongside "Astronomer data".

Tighten the when clause to name the triggering artifacts, e.g. "Use when the user wants to manage Astronomer/Airflow deployments, workspaces, or run data pipeline actions."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Astronomer domain plus a few actions, but the actions are generic ("manage X", "automate workflows") rather than concrete, matching the anchor that lists 1-2 domain actions without comprehensive coverage.	3 / 5
Completeness	It states both the what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Astronomer data"), matching the anchor where both are present but the what could be more specific.	4 / 5
Trigger Term Quality	"Astronomer" and "data" are natural terms a user would say, but common synonyms users actually use (Airflow, pipelines, DAGs, deployments) are absent, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Astronomer integration" targets a named platform niche with a distinct trigger ("interact with Astronomer data"), giving mostly distinct scope with only minor overlap risk from the generic action verbs.	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/astronomer/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.