eng-query-warehouse

Files (1)

• SKILL.md

SKILL.md (first lines)

> Generated file — do not edit.
> Persona: engineer (Software engineer)
> Pack:    engineer-pack v0.2.0
> Source:  skill `query-warehouse` @ 3d7e0fd
> Edit the source skill, not this copy — this one is overwritten on every build.

# Query the warehouse

## Boundaries that apply to this skill

**Use the least-sensitive environment that can reproduce the issue.** Start with synthetic fixtures
or approved non-production data. Do not copy customer records, production database rows, or
unredacted logs into source control, tickets, prompts, or local test data.


Drives the `warehouse-mcp` server. If it is not connected, write the SQL and say plainly that it was
not run — a query you did not execute must never be reported as a result.

For a local extract or a sample database there is `sqlite-explorer`, which is eager and always
connected. Use it for shaping a query before running the real one; never present a figure from a
local sample as a warehouse figure.

## Steps

1. Restate the question as a measurable one. "Are customers happy" is not measurable; "share of
   orders with a return within 30 days" is.
2. Name the tables and filters before running anything, so the reader can challenge the shape of the
   answer rather than only the number.
3. Run it, then report the figure **with** the query that produced it. A number without its query
   cannot be checked and will be quoted for a year.
4. State what the figure does not cover. Every filter excludes something.

From aws-samples/sample-skillforge, Apache-2.0.

More from aws-samples/sample-skillforge