Promote snowpark-connect from Snowflake-Solutions

[jdanielmyers]

Summary

Promotes the snowpark-connect skill from the internal Snowflake-Solutions/cortex-code-skills repo to public Labs, rewritten for an external builder audience (developers, data engineers).

Run through the v1.1.0 audit pipeline:

• Holistic LLM rewrite for builder audience
• All internal Snowflake references substituted with public equivalents (e.g., Snowhouse -> ACCOUNT_USAGE)
• audience.no_internal_refs check passes
• Sub-skills folded into <sub>/INSTRUCTIONS.md per the umbrella precedent (manage-zerocopy-sapbdc)

Test plan

• Audit blocking_failures == 0
• audience.no_internal_refs passes
• Frontmatter matches Labs conventions (snowflake-docs / manage-zerocopy-sapbdc precedents)
• LICENSE present (Snowflake)
• No Snowflake-Solutions repo path leakage
• No nested SKILL.md in sub-skill dirs (all converted to INSTRUCTIONS.md)

[jdanielmyers]

Audit Report: snowpark-connect

Re-audit (post-v1.1.1 + critical fixes). Original report superseded.

Summary

Category	🔴	🟡	🟢
Frontmatter	0	0	0
Structure	0	0	0
Workflow	0	0	1

Critical 🔴

None — all critical findings from the original audit have been addressed.

Warnings 🟡

None.

Suggestions 🟢

1. Textbook umbrella/router skill: thin (~80 lines), clear 5-option routing table, single stopping point before loading sub-flows, recommended ordering (Setup → Migrate → Validate → Optimize → Deploy), and concise "Common Mistakes" focused on process ordering rather than implementation details.

Verdict

Ready to merge — Clean router with 5 well-named sub-flows, proper stopping point, and good routing logic.

[sfc-gh-kmuir]

@jdanielmyers snowpark-connect is already an existing bundled skill, is there another reason you wanted to port this one over?