Add quick-list skill

[johniannone-eng]

Skill Overview

engage-segment-builder: Fast audience upload to CDP Engage from a list of emails/IDs.

What This Skill Does

• Takes a list of emails (inline, file, or SQL query) and creates a usable segment in Engage
• Automates the full chain: TD table → parent segment → child segment
• Eliminates manual parent segment configuration for simple list uploads
• Guides user through workspace selection or creation

Flow

Two paths based on user choice:

Path A (new parent segment):
emails → TD table → parent segment → child segment → workspace guidance

Path B (add to existing parent segment):
emails → insert into existing table → re-run parent segment → child segment auto-updates → workspace check

Known Limitations

• Workspace-to-parent-segment association cannot be automated via CLI yet — user is guided to do this manually in Engage Studio UI. Planned as a future CLI enhancement.

Checklist

• SKILL.md is under 500 lines
• description contains succinct trigger conditions
• No generic concept explanations
• Examples used instead of prose
• Tested with Claude Code (multiple end-to-end runs)

🤖 Generated with Claude Code

[adher-code]

👋 Thanks for the engage-segment-builder skill — the one-shot contact list → Engage segment pipeline is genuinely useful and the CLI wiring (tdx db → tdx ps → tdx sg) looks correct. A few things to address before I can approve.

What's needed

1. Resolve the CI failure

The 'Analyze (actions)' CodeQL check is failing on this branch. Please investigate — if it's the known repo-wide false positive, add a note in the PR so we can confirm and move on. If it's something new, it'll need a fix.

2. SKILL.md frontmatter fields

Currently only name and description. For Tier 1, please add:

owner: <your-td-email>
tier: 1
classification: product
phase: 1
known-limitations: |
  - The workspace-to-parent-segment association step must be done manually in the TD Console UI — the skill cannot do this programmatically
  - Requires write access to the quick_lists database on the target account
  - Child segment filter uses @ character detection for email addresses — non-email ID lists need a different filter condition

Note: the workspace-to-parent-segment limitation is mentioned in the PR body — it needs to live in the SKILL.md itself so users are warned before they start, not surprised at the end.

3. SKILL.meta.yml — a validation log with at least one live staging run.

4. test.yml — skill-level test scenarios: email list input, SQL query input, collision handling, cleanup path.

Once CI is resolved and the three files are in, I'm happy to approve. The automation flow is solid.