Move all three skills into skills/; add root README; fix paths

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

PLAN.md

@@ -73,12 +73,12 @@ Build both in `D:\RPA SKILLS\<skill-name>\`. The user installs them into Claude
 ## Status: what already exists
 
 ```
-rpa-dashboard-no-ai/
+skills/rpa-dashboard-no-ai/
   templates/dashboard.html     DONE: generic page, works in Qt (QWebChannel) or web (polling)
   templates/contract.md        DONE: event/JSON contract + Tebra lessons
   templates/bridge.py          DONE: minimal PyQt6 host + subprocess log tailing
   templates/reference/         DONE: tebra_dashboard.html, tebra_bridge_part1/2.py (raw extracts)
-rpa-dashboard-ai/
+skills/rpa-dashboard-ai/
   templates/reference/web/     DONE: Superbill index.css, DESIGN.md, bands.ts, theme.tsx, types.ts, api.ts,
                                      components (BrandHeader, Sidebar, StatsBar, Donut, SplitPane,
                                      RunPanel, ReviewPane, RoiTab, PdfPane, Tooltip, icons)
@@ -86,24 +86,24 @@ rpa-dashboard-ai/
 ```
 
 ## TODO for the implement skill
-1. **Fix the lint error in `rpa-dashboard-no-ai/templates/bridge.py:15`.** `STEPS = {{STEPS_PY}}` is not valid Python, so the lint hook flags it (F821). Change it to `STEPS = ["{{STEP_1}}", "{{STEP_2}}"]` or similar.
-2. **Write `rpa-dashboard-no-ai/SKILL.md`.**
+1. **Fix the lint error in `skills/rpa-dashboard-no-ai/templates/bridge.py:15`.** `STEPS = {{STEPS_PY}}` is not valid Python, so the lint hook flags it (F821). Change it to `STEPS = ["{{STEP_1}}", "{{STEP_2}}"]` or similar.
+2. **Write `skills/rpa-dashboard-no-ai/SKILL.md`.**
    - Frontmatter `name` and `description`. The trigger should cover "RPA dashboard", "automation dashboard", "bot dashboard", and "without AI".
    - The workflow above.
    - Point to `templates/*`.
-3. **Write `rpa-dashboard-ai/SKILL.md`.**
+3. **Write `skills/rpa-dashboard-ai/SKILL.md`.**
    - Trigger: "AI RPA dashboard", "extraction dashboard", "LLM/OCR review dashboard".
    - The workflow above.
    - Web path: React + Vite + Tailwind v4, adapted from `reference/web`.
    - Desktop path: copy the no-AI `dashboard.html`, then add the AI sections.
 4. **Write `templates/themes.md` in both skills.** Content is in the Theme presets section above.
-5. **Write `rpa-dashboard-ai/templates/contract.md`.** It extends the no-AI contract with:
+5. **Write `skills/rpa-dashboard-ai/templates/contract.md`.** It extends the no-AI contract with:
    - `Run{job_id,status:pending|queued|running|done|failed,model,pages_done,pages_total,summary:{green,amber,red,unscored}}`
    - `ReviewRow{row_id,field,value,band,score,reason,verified,corrected_value}`
    - `RoiRun{model,input_tokens,output_tokens,thinking_tokens,total_cost}`
    - Endpoints: `PATCH /review/{row_id}`, `POST /runs/{id}/approve` (server gate), `GET /roi`.
    - Polling: 1.5–2s only while a run is busy.
-6. **Write `rpa-dashboard-ai/templates/ai-sections.html`.** Plain HTML/CSS/JS versions of the band legend, the review split pane and the ROI tiles, for the desktop path.
+6. **Write `skills/rpa-dashboard-ai/templates/ai-sections.html`.** Plain HTML/CSS/JS versions of the band legend, the review split pane and the ROI tiles, for the desktop path.
 7. **Strip project-specific bits from the AI reference files.** Remove ECW/Tebra project names, SPB_* tables and patient/ticket wording, or mark them as such. **Never** ship real patient data (PHI), internal IPs or keys. The reference copies have already been checked for these, but check again after editing.
 8. **Verify.** Open `dashboard.html` in a browser using sample data. Check light, dark and narrow width. Load each SKILL.md and make sure every path it references exists.