Promote openflow-spcs-privatelink from Snowflake-Solutions

[jdanielmyers]

Summary

Promotes the openflow-spcs-privatelink 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: openflow-spcs-privatelink

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

Summary

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

Critical 🔴

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

Warnings 🟡

1. Frontmatter name is setup-openflow-privatelink but the skill folder is openflow-spcs-privatelink → The name field should match the folder name for consistent discovery and invocation. Either rename the folder to setup-openflow-privatelink or change the frontmatter name to openflow-spcs-privatelink.

Suggestions 🟢

1. Excellent single-file skill: clear architecture diagram (ASCII), well-structured 2-phase workflow (AWS infra → Snowflake side), stopping points at health-check gates, troubleshooting quick-reference table, and ordered cleanup instructions.

Verdict

Needs minor fixes — The name/folder mismatch should be resolved before merge. Everything else is clean and well-structured.