DW-Copilot

This skill appears coherent for generating Spec/Plan/Task artifacts for data warehouse work, but pay attention to these points before installing or using it: - Origin: the source is unknown and no homepage is provided. Prefer skills from known maintainers or inspect files closely. - Credentials: the templates reference many sensitive values (JDBC username/password, platform AK/SK, web tokens/cookies, Kerberos keytabs). The registry metadata declares no required env vars — expect the agent to ask for these at runtime. Do NOT paste production credentials directly into chat. Use least-privilege, read-only accounts or temporary/test credentials. - External connections: Phase 1 may instruct connecting to database hosts, metadata APIs, HDFS namenode, or web portals. Confirm network endpoints and scope before allowing connections; validate that any AK/SK or tokens are scoped and revocable. - Generated code: task.md examples include absolute paths (/data/scripts/...) and production-like settings. Review generated DDL/SQL and Azkaban configs before deploying; run outputs in an isolated/test environment first. - Secrets handling: ensure any credentials the skill requests are provided via secure, out-of-band mechanisms (agent environment variables or a secrets manager) rather than pasted into chat logs. If your platform supports declaring required env vars for the skill, insist they be declared and audited. - Confirm behavior: the skill enforces user confirmation points (Phase 3 and 5) which reduces autonomous risky actions, but you should verify the agent actually prompts and does not proceed without explicit approval. If you decide to use it: test with dummy datasets/accounts, restrict credential privileges, and review all generated scripts/configs before applying them to production.