Add demo-environment skill to studio-skills

[glawrence90]

Summary

• Adds studio-skills/demo-environment — a guided interactive workflow for setting up isolated demo environments on the shared TD account
• Copies from 10 pre-built td_template_* databases (Retail, FSI, Healthcare, Travel, CPG, Media, Telecom, Auto, Insurance, Education) with exact parent segment blueprints
• Enforces naming conventions, prohibited actions, and cleanup rules to prevent shared resource corruption

What it does

1. Asks 3 questions: prospect name, vertical, goals
2. Copies template database into user's own namespaced DB ({owner}_demo_{slug})
3. Creates parent segment (Demo - {prospect}) using verified column blueprints
4. Includes pre-flight checks, error recovery, and multi-company batch support

Key features

• 10 vertical blueprints with exact column names and types (verified against live template DBs)
• Negative boundaries to avoid overlap with parent-segment, platform-demo, and industry-cdp-builder skills
• Explicit slug generation rules for special characters (T-Mobile → tmobile, Procter & Gamble → procter_gamble)
• Includes evals/evals.json with 3 test cases

Eval results

• 3-pass skill-eval: Structure PASS (417 lines), Triggers F1=0.82, Output Quality 93% (28/30)
• Benchmark: 100% assertion pass rate with skill vs 0% baseline (no skill)

Test plan

• Tested with Starbucks (CPG), Kaiser Permanente (Healthcare), T-Mobile (Telecom)
• Verified correct naming, YAML schema, blueprint columns, default_time_filter
• Verified special character handling in prospect slugs
• Verified baseline comparison (0% without skill)

🤖 Generated with Claude Code

[glawrence90]

@td-rahul could you review this when you get a chance?

[adher-code]

👋 Thanks for building the demo-environment skill — automating prospect demo setup with vertical-specific templates is exactly the kind of time-saver SEs need, and the safety guards around shared template databases are well thought out. A few things to address before I can approve.

What's needed

1. Fix CI first — label-by-path is failing

The new studio-skills/demo-environment/ path doesn't match any label routing rule in the workflow. This may also be why no reviewers were auto-assigned. Please add a label rule for this path (similar to how other studio-skills/ entries are configured) so CI goes green and the right teams are notified.

2. SKILL.md frontmatter fields

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

owner: <your-td-email>
tier: 1
classification: product
phase: 1
known-limitations: |
  - Requires td_template_{vertical} databases to be provisioned on the target account
  - Cleanup path drops the demo schema without a second confirmation — destructive
  - Prospect slug is derived from the name; collisions are detected but require manual resolution

3. SKILL.meta.yml — a staging validation record. The evals/evals.json file is a great start, but it's a custom format. Please also add a standard SKILL.meta.yml with at least one live validation entry.

4. test.yml — a standard skill-level test file. At minimum: vertical selection, naming convention check, collision detection, cleanup path.

Once CI is green and the three files are added, happy to move this forward. The skill logic itself is good.