dsql Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• The skill relies on MCP server configuration that may grant write access if --allow-writes is enabled; users must ensure proper IAM permissions and least-privilege principles.
• High-risk permission hints: Secrets or environment access
• Financial research output is not financial advice; require human review before any live investment decision
• The skill is documentation-heavy and assumes the user has access to an Aurora DSQL cluster; without a cluster, some workflows are not directly executable.