create skills: salesforce-se-info and update-salesforce-tech-validation, update skill index

update-salesforce-tech-validation/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: update-salesforce-tech-validation
+description: |
+  Edit and run the SE Radar report in Salesforce to add columns, view SE notes, and manage technical validation data.
+
+  Triggers when user mentions:
+  - "update the SE radar report"
+  - "add a column to the SE report"
+  - "edit the vNotes report"
+  - "run the SE radar report"
+  - "update salesforce tech validation report"
+---
+
+## Overview
+
+This skill automates editing and running the **SE Radar: SE vNotes and TVSs IC** report in Salesforce. It covers adding columns, re-running the report, and reading the results. More workflows (e.g., filtering, grouping, saving changes) will be added as needed.
+
+## Prerequisites
+
+- Chrome browser with an active Salesforce session (authenticated via Okta SSO at verkada.okta.com)
+- Access to the SE Radar report
+
+## Report URL
+
+```
+https://verkada.lightning.force.com/lightning/r/Report/00OUu000004gR9ZMAU/view
+```
+
+## Workflow: Add a Column and Re-Run
+
+### Step 1: Open the Report
+
+Navigate to the report URL. Wait for the page to load (look for "Total Records" and the report table). If Salesforce doesn't load via browser automation (SSO issues), ask the user to open it manually first.
+
+### Step 2: Enter Edit Mode
+
+1. Take a snapshot to find the **"Edit"** button inside the Report Viewer iframe
+2. Click **"Edit"**
+3. Wait for the Report Builder to load (look for "Fields" panel, "Undo"/"Redo" buttons, and "Run" button)
+
+### Step 3: Add a Column
+
+1. The **Fields** panel on the left contains a tree of all available fields grouped by object (e.g., "Opportunities", "SE Deal Management", "vNotes", "SE User")
+2. Locate the desired field in the tree. If the list is long, use the **"Search Fields"** searchbox at the top of the panel
+3. Click the field name to select it (it will show as `selected` in the accessibility tree)
+4. The page will display: "1 selected. To add new fields as detail columns, press Enter"
+5. Press **Enter** to add the field as a new column
+
+After adding, the **Undo** button becomes enabled, confirming the change was registered. The preview area may show "To see the latest edits, refresh the preview."
+
+### Step 4: Run the Report
+
+1. Click the **"Run"** button (top of the report builder)
+2. The page navigates back to the report view with the new column included
+3. Wait for "Total Records" to appear confirming the data has loaded
+
+### Step 5: Verify the New Column
+
+Take a snapshot of the report view and confirm the new column header appears in the table.
+
+## Known Columns in the Report
+
+As of the initial skill creation, the report includes these columns:
+
+| Column | Object |
+|--------|--------|
+| Opportunity ID | Opportunities |
+| Opp Name And Link | Opportunities |
+| Solutions Engineer: Full Name | Opportunities |
+| VNote: VNote Name | vNotes |
+| Technical Validation Stage | SE Deal Management |
+| POC Documentation Link | SE Deal Management |
+| POC Stage | SE Deal Management |
+| Solutions Engineer: Team | SE User |
+| SE Notes | Opportunities (added via this workflow) |
+
+## Common Gotchas
+
+- **Salesforce loads in an iframe**: The report content lives inside an iframe called "Report Viewer" (view mode) or "Report Builder" (edit mode). Snapshots and interactions must target elements within this iframe.
+- **Ephemeral UIDs**: Salesforce Lightning re-renders frequently. Element UIDs change between snapshots. Always take a fresh snapshot before clicking.
+- **Progressive loading**: The report builder shows "Previewing a limited number of records" while loading. Use `wait_for` with text like "Columns" or "Run" before interacting.
+- **SSO session expiry**: If the session has expired, the page will redirect to Okta login. Ask the user to re-authenticate manually.
+- **Field tree is large**: The Opportunities object alone has 400+ fields. Use the "Search Fields" searchbox to find specific fields quickly rather than scrolling.
+- **"Run" vs "Save"**: Clicking "Run" re-runs the report with the new columns but does not persist the change to the report definition. Use "Save" if the column should be permanent.