Promote manage-external-lineage from Snowflake-Solutions

[jdanielmyers]

Summary

Promotes the manage-external-lineage 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

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

[jdanielmyers]

Audit Report: manage-external-lineage

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. Clean 5-step workflow with stopping points before sending payloads and before deleting lineage links. Good awareness of the "DELETE always returns 200" trap with explicit "verify in Snowsight" guidance. Reference files are well-organized.

Verdict

Ready to merge — Well-structured skill with correct stopping points, clear payload construction rules, and proper handling of the DELETE verification caveat. Limitations section is honest and useful.

[sfc-gh-kmuir]

This skill is still in draft mode in Solutions