cosmos-dbt-fusion
Use when running a dbt Fusion project with Astronomer Cosmos. Covers Cosmos 1.11+ configuration for Fusion on Snowflake/Databricks with ExecutionMode.LOCAL. Before implementing, verify dbt engine is Fusion (not Core), warehouse is supported, and local execution is acceptable. Does not cover dbt Core.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description for a niche technical skill. It excels at completeness with explicit 'Use when' guidance, clear exclusions, and prerequisites. The main weakness is that it describes scope and constraints rather than listing specific concrete actions the skill enables, which slightly reduces specificity.
Suggestions
Add 1-2 specific concrete actions the skill performs, e.g., 'Configures Cosmos operators, sets up dbt profiles, and defines Airflow DAG settings for dbt Fusion projects with Astronomer Cosmos.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (dbt Fusion with Astronomer Cosmos) and mentions configuration details like Cosmos 1.11+, Snowflake/Databricks, and ExecutionMode.LOCAL, but doesn't list specific concrete actions (e.g., 'configure DAGs', 'set up operators', 'define profiles'). It describes scope and prerequisites more than actions. | 2 / 3 |
Completeness | Clearly answers both 'what' (Cosmos 1.11+ configuration for Fusion on Snowflake/Databricks with LOCAL execution) and 'when' ('Use when running a dbt Fusion project with Astronomer Cosmos'). Also includes explicit exclusion criteria ('Does not cover dbt Core') and prerequisites to verify before implementing. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'dbt Fusion', 'Astronomer Cosmos', 'Cosmos 1.11+', 'Snowflake', 'Databricks', 'ExecutionMode.LOCAL', 'dbt Core' (as exclusion). These are the exact terms a user working in this space would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: dbt Fusion (not Core) + Astronomer Cosmos + specific warehouses + specific execution mode. The explicit exclusion of dbt Core further reduces conflict risk with any general dbt skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides a clear step-by-step implementation checklist with executable code examples and explicit validation checkpoints at each stage. The progressive disclosure to reference files is well-handled. The main weakness is moderate redundancy — the full DAG example re-declares configs already shown, and some constraints (LOCAL mode, supported warehouses) are stated multiple times.
Suggestions
In Step 7's DbtDag example, reference the config objects from Steps 3-6 rather than re-declaring them, reducing ~15 lines of duplication.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the full DbtDag example in Step 7 re-declares all config objects already shown in Steps 4-6, and some constraints are repeated (e.g., LOCAL execution mode mentioned multiple times). The constraint table and version notes are tight, but the overall document could be trimmed. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready code for every step: Dockerfile install, Python config objects, complete DAG examples for both DbtDag and DbtTaskGroup patterns. Commands like `pip show` and `pip install` are concrete and specific. | 3 / 3 |
Workflow Clarity | Clear numbered sequence from version check through final validation. Each step has explicit validation checkpoints (e.g., 'Validate: pip show reports version ≥ 1.11.0', 'Validate: dbt binary exists'). The final checklist and troubleshooting section provide error recovery guidance. The pre-conditions are clearly stated upfront. | 3 / 3 |
Progressive Disclosure | Clean overview structure with well-signaled one-level-deep references to `reference/cosmos-config.md` for detailed ProfileConfig and operator_args. Related skills are clearly listed. The main document stays focused on the implementation checklist without inlining reference material. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- astronomer/agents
- Commit
0642adb
- 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.