VasanthandClaude Opus 5.5
ff2f7fcd4a
The first real handover (MEK Charge Reconciliation) came out at 9 pages. Ops want it short: which URL to open and what to click, what shows where after the click, what to do when an exception comes, and how to email us. - Output is "<Project Name> Handover SOP" (HANDOVER-SOP.md + .docx) with 5 sections: how to run, what you see while it runs, result, when something goes wrong, email us. HANDOVER-DEV.md is dropped; dev-team findings go in the chat. - At most ~1,400 words; to_docx.py prints the word count and flags overflow, and renders *italic* for the variable parts of messages. - Every quoted message, label and URL is checked against the code. The SOP must say what clicking Run again does to the data. - One scan subagent; failure classes stay as a scan checklist. - Tebra reference rewritten in the SOP format; test, README, glossary updated; ADR-0005 supersedes ADR-0004. The handoff eval runner (tests/evals/run_handoff_eval.py) still grades an older 13-section format and was already out of date; not touched here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
RPA Skills
Claude skills for RPA projects. Each folder in skills/ is one skill: copy it into ~/.claude/skills/ to install it.
| Skill | What it does |
|---|---|
rpa-run-tab |
Adds a Tebra-style Run tab (Trigger button, Excel input, progress, live log, checkpoints) to a desktop PyQt6 bot in about 5 minutes. |
rpa-dashboard-no-ai |
Builds a full dashboard (run panel, overview, report, optional checkpoints, admin and login) for a bot with no AI. Desktop or web. |
rpa-dashboard-ai |
The same dashboard, plus confidence bands, review-and-approve and a cost/ROI page, for a bot that uses an LLM or OCR. Install it together with rpa-dashboard-no-ai. |
sql-review |
Reviews SQL code (SQL Server + pyodbc) against 10 rules through a subagent and writes every issue with a before/after fix plan to query_tracker.md. Read-only. |
rpa-bot-handoff |
Writes a short <Project Name> Handover SOP (at most 4 pages, Markdown and Word) for a bot being handed over: how to run it (URL, what to click), what shows where, where the result is, how a problem shows and what to do, and how to email the dev team. |
pr |
Writes the PR body (Summary, Evidence, Merge Danger) and raises the PR to main with the tea CLI, with Murugeswaran as reviewer. Runs only on /pr; asks before creating a branch and before raising the PR. |
Run all tests: uv run --with pytest --with playwright pytest tests