CtrlK
BlogDocsLog inGet started
Tessl Logo

managing-astro-deployments

Manage Astronomer production deployments with Astro CLI. Use when the user wants to authenticate, switch workspaces, create/update/delete deployments, or deploy code to production.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

An actionable, well-structured CLI reference with executable examples and sensible workflows. The main gap is the absence of explicit validation checkpoints around destructive and production-deploy operations, which caps workflow clarity.

Suggestions

Add an explicit verification step to destructive and production-deploy workflows, e.g. run `astro deployment inspect <ID>` to confirm HEALTHY status before and after `astro deploy` / `astro deployment delete`.

Insert a confirm-before-proceed checkpoint in the Delete Deployments workflow (verify the deployment ID via `astro deployment list` before running delete).

Trim the Tips section to remove guidance already covered in Deploy Code and Update Deployments, or fold the unique tips back into their relevant sections.

DimensionReasoningScore

Conciseness

The body is a lean command reference with minimal concept explanation, though the Tips section repeats guidance already stated in Deploy Code and Update sections.

4 / 5

Actionability

Copy-paste-ready `astro` commands with concrete flags and examples (executor selection, --dags/--image-only/--force, token creation) cover the common cases fully.

5 / 5

Workflow Clarity

Numbered workflows (First-Time Deployment, Iterative DAG Dev, Staging-to-Prod) are sequenced, but destructive/batch operations like delete and production deploy lack explicit validation/verification checkpoints, capping this at 3.

3 / 5

Progressive Disclosure

Well-organized into clear sections for a single-file CLI reference with no bundle files, though some detail (token management, config, the inspect field list) could be split into one-level-deep references.

4 / 5

Total

16

/

20

Passed

Description

88%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.

A strong, third-person description that concretely enumerates deployment actions and pairs them with an explicit "Use when" trigger clause. Only minor gains available from additional synonyms and sharper disambiguation from related Astro skills.

DimensionReasoningScore

Specificity

"authenticate, switch workspaces, create/update/delete deployments, or deploy code to production" lists multiple concrete actions covering the full deployment lifecycle comprehensively.

5 / 5

Completeness

It explicitly states what ("Manage Astronomer production deployments with Astro CLI") and when ("Use when the user wants to authenticate, switch workspaces...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like "deploy code to production", "switch workspaces", and "create/update/delete deployments" match what users would say, but a few synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

The "production deployments with Astro CLI" niche is clear and distinct from local-env usage, though minor overlap risk remains with the sibling troubleshooting/local-env Astro skills.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
astronomer/agents
Reviewed

Table of Contents

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.