CtrlK
BlogDocsLog inGet started
Tessl Logo

troubleshooting-astro-deployments

Troubleshoot Astronomer production deployments with Astro CLI. Use when investigating deployment issues, viewing production logs, analyzing failures, or managing deployment environment variables.

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/troubleshooting-astro-deployments/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-organized troubleshooting reference built on executable Astro CLI commands. Its main weakness is redundancy across the workflow, patterns, best-practices, and quick-reference sections, plus missing validation steps for the variable-management operations.

Suggestions

Collapse 'Common Investigation Patterns' and 'Investigation Best Practices' into the existing workflow and quick-reference table to remove repetition and reclaim tokens.

Add an explicit verification step after variable create/update/delete (e.g. re-run `astro deployment variable list --key <KEY>` to confirm the change) to introduce a feedback loop for the destructive operations.

Consider moving the 'Environment Variables Management' block into a separate reference file and linking to it from the main body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient command-with-comment blocks, but 'Common Investigation Patterns', 'Investigation Best Practices', and the 'Quick Reference' table substantially restate commands and guidance already shown in 'Complete Investigation Workflow'; not a 4 because the repetition is noticeable enough to tighten.

3 / 5

Actionability

Fully executable, copy-paste-ready Astro CLI commands throughout, with concrete flag usage (-c, --error, --keyword, --secret) and examples covering the common troubleshooting cases.

5 / 5

Workflow Clarity

A clear five-step 'Complete Investigation Workflow' with 'Look for...' checkpoints per step; not a 5 because there are no explicit validate/feedback loops, and the variable create/update/delete operations lack verification steps.

4 / 5

Progressive Disclosure

Self-contained skill with no bundle files, well-organized into clearly headed sections and a navigation pointer to related skills; not a 5 because the sizable environment-variable management block could reasonably live in its own reference file.

4 / 5

Total

16

/

20

Passed

Description

83%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, well-structured description that clearly states both capability and trigger conditions in third person. It is specific and actionable with only minor gaps in trigger synonym coverage and a small overlap risk with sibling Astro skills.

Suggestions

Add a few natural synonyms users say (e.g. 'DAG failures', 'Airflow tasks', 'deployment is unhealthy') to broaden trigger coverage toward a 5.

Sharpen the boundary with the managing-astro-deployments skill, e.g. note this skill is read-only diagnosis while creation/updates live in the other skill.

DimensionReasoningScore

Specificity

Names the domain ('Astronomer production deployments with Astro CLI') and lists several concrete actions ('investigating deployment issues, viewing production logs, analyzing failures, or managing deployment environment variables'); not a 5 because 'investigating deployment issues' is somewhat generic and a couple of finer troubleshooting actions are absent.

4 / 5

Completeness

Explicitly answers both 'what' ('Troubleshoot Astronomer production deployments with Astro CLI') and 'when' ('Use when investigating deployment issues, viewing production logs, analyzing failures, or managing deployment environment variables') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say ('deployment issues', 'production logs', 'analyzing failures', 'environment variables') are present with good coverage; not a 5 because common synonyms/extensions (e.g. 'DAG failures', 'Airflow') are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche focused on troubleshooting production deployments with the Astro CLI, distinct from sibling management skills; not a 5 because it borders on overlapping with the related 'managing-astro-deployments' skill around environment-variable management.

4 / 5

Total

17

/

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.