motherduck-build-cfa-app 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
• No critical security risks found. The skill explicitly defers destructive actions, external writes, and scope expansion to user approval, and recommends keeping admin tokens and embed-session creation server-side.
• Permission surface may require sandboxing
• The tracked source changed or could not be synchronized. Review the current source before installing.
• Minor: SKILL.md does not explicitly call out parameterized queries or strict validation of user-supplied filters and tenant identifiers as a hard requirement, though the allowlisted API contract implies it.