Name: warehouse-init
Rating: 71.2 (1 reviews)
Author: astronomer

warehouse-init

Initialize warehouse schema discovery. Generates .astro/warehouse.md with all table metadata for instant lookups. Run once per project, refresh when schema changes. Use when user says "/astronomer-data:warehouse-init" or asks to set up data discovery.

1.60x

Quality

56%

Does it follow best practices?

Impact

96%

1.60x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/warehouse-init/SKILL.md

Quality

Content

27%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill covers a complex multi-step warehouse discovery process with good conceptual coverage but suffers from significant verbosity — the output format template, example session, cache staleness guidance, and codebase patterns table inflate the document well beyond what's needed for actionable guidance. The workflow is logically sequenced but lacks validation checkpoints for a process that involves parallel subagents and database operations. The entire content is inline with no progressive disclosure despite being well over 200 lines.

Suggestions

Extract the output format template, cache management section, codebase patterns table, and example session into separate reference files (e.g., WAREHOUSE_FORMAT.md, CACHE.md) and link to them from the main skill.

Add explicit validation checkpoints: verify warehouse.yml exists before proceeding, confirm subagent results are non-empty before merging, validate the generated warehouse.md has expected sections.

Remove or drastically condense the 'Signs of Stale Cache' section (Claude can infer these) and the 'Codebase Patterns Recognized' table (already covered in Step 2).

Replace the pseudocode Task() calls with the actual tool invocation syntax Claude should use, or clarify that Task is a conceptual placeholder and provide the real mechanism.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~250+ lines. It includes extensive output format templates, example sessions, explanations of cache staleness signs ('Queries fail with table not found errors'), and sections like 'Codebase Patterns Recognized' that repeat information already covered in the process steps. Much of this could be condensed significantly.	1 / 3
Actionability	The skill provides concrete SQL queries and CLI commands, but key parts use pseudocode-like Task() calls that aren't real executable syntax. The subagent orchestration pattern is described conceptually rather than with precise, copy-paste-ready instructions. Some commands reference scripts without confirming their actual interfaces.	2 / 3
Workflow Clarity	The 8-step process is clearly sequenced and logically ordered, but lacks explicit validation checkpoints between critical steps. There's no verification that warehouse.md was generated correctly, no error handling for failed database connections or SQL queries, and no feedback loop if subagent discovery fails. The refresh behavior section describes preservation logic but doesn't include validation.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of text with no references to supporting files despite its length and complexity. The output format template (~40 lines), cache management section, codebase patterns table, and example session could all be split into separate reference files. No bundle files are provided to offload this content.	1 / 3
	Total	6 / 12 Passed

Description

85%

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 that clearly communicates what the skill does (generates warehouse metadata files) and when to use it (specific slash command or data discovery setup requests). Its main weakness is that the trigger terms could be broader to capture more natural user phrasings beyond the slash command and 'data discovery'.

Suggestions

Add more natural trigger terms users might say, such as 'explore my database', 'list all tables', 'what tables are available', or 'scan schema'.

Dimension	Reasoning	Score
Specificity	Lists specific concrete actions: 'Initialize warehouse schema discovery', 'Generates .astro/warehouse.md with all table metadata for instant lookups'. Also specifies when to run ('once per project, refresh when schema changes').	3 / 3
Completeness	Clearly answers both what ('Generates .astro/warehouse.md with all table metadata for instant lookups') and when ('Use when user says /astronomer-data:warehouse-init or asks to set up data discovery'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes the slash command trigger '/astronomer-data:warehouse-init' and terms like 'schema discovery', 'data discovery', 'warehouse', and 'table metadata'. However, it misses natural user phrases like 'explore my database', 'list tables', 'what tables do I have', or 'schema' alone.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with a specific slash command trigger, a unique output artifact (.astro/warehouse.md), and a narrow domain (warehouse schema discovery). Unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: astronomer/agents
Commit: 789b454

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