Skills/Rpa_Skills
8
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rpa-bot-handoff: one 54-line SKILL.md, no reference or template files

Browse Source 
The skill is now one SKILL.md (54 lines) with the SOP shape inline, plus
templates/to_docx.py for the Word and PDF. Removed: the template, the MEK
reference example and the skill README. The converter's selfcheck uses a
built-in sample. Tests now check the skill is that one short file, has the
6 don't-miss checks, and its SOP shape has the 5 sections and To/CC lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
VasanthandClaude Opus 5.5 committed 2026-10-28 17:38:34 +05:30
1 parent 36e621b153
commit b35796e1a5
8 files changed
+89 -247
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

skills/rpa-bot-handoff/SKILL.md
+34 -14
View File
@@ -5,27 +5,47 @@ description: Writes "<Project Name> Handover SOP" - a short PDF (at most 4 pages
# RPA bot handoff
Make **`<Project Name> Handover SOP`**: one PDF, at most 4 pages, that ops keeps open while they run the bot. `templates/reference/mek-charge-reconciliation.md` is the model: copy its length, layout and tone.
Make **`<Project Name> Handover SOP`**: one PDF, at most 4 pages, that ops keeps open while they run the bot. Plain words, no code.
## Steps
1. **Scan.** One read-only subagent (never run the bot; no patient data, client names or passwords in its report). Ask for exact on-screen text with file:line: how to start (URL or shortcut, sign-in, Run button, what a new run does to old results), what shows where during a run, every timeout and retry, how a run ends and where the result is, every message ops can see, alerts, how to stop.
2. **Ask once:** the developer's email (To), the manager's name and email (CC), and where ops runs it if unclear.
3. **Write** `HANDOVER-SOP.md` in this shape:
1. **Scan.** Start one read-only subagent: never run the bot, no patient data, client names or passwords in its report. Ask for exact on-screen text with file:line: how to start (URL or shortcut, sign-in, Run button, what a new run does to old results), what shows where during a run, every timeout and retry, how a run ends and where the result is, every message the operator can see, alerts, and how to stop.
2. **Ask once:** the developer's email (To), the manager's name and email (CC), and where ops runs it if the code allows more than one place.
3. **Write** `HANDOVER-SOP.md` from `templates/HANDOVER-SOP.md`: 1. How to run, 2. What you see while it runs, 3. Result, 4. When something goes wrong, 5. Email us.
4. **Build** with `templates/to_docx.py`: `python <skill>/templates/to_docx.py HANDOVER-SOP.md -o "<Project Name> Handover SOP.docx" --pdf`. Over 4 pages: shorten cells, never drop a message.
5. **Hand over** the PDF. List problems for the dev team in at most 5 lines in the chat, not in the SOP.
```markdown
# <Project Name> Handover SOP
Version <x> · <date> · Problems: email <developer>, CC <manager> (section 5)
<one line: what the bot does, from which app, what it produces>
## 1. How to run
Numbered steps: URL or shortcut, sign in, the Run button. Then "Before you click": what a new run does to the old results; one run at a time.
## 2. What you see while it runs
| Where on the screen | What it shows | then a normal run in one line
| Step | The bot waits at most | Then | then "Step in only when: ..."
## 3. Result
Good run / Needs a look (call out a misleading "Finished" or green). Where the result is.
| Status | Meaning | What you do |
## 4. When something goes wrong
How it shows (colour, list, column). Then:
| ID | Message you see | What it means | What you do | E01, E02 ... one row per message
Don't: (at most 3, with a short reason). To stop it: (the one right way).
## 5. Email us
Email <developer> with <manager name> (<manager email>) in CC when section 4 says "email us". Answer: <time>.
To: <developer>
CC: <manager>
Subject: <Project Name> - E<number> - <date>
Run started / Error: E<number> - <message> / Where / What I did / Attached: screenshot
Never send: passwords, patient data, result files that hold patient data.
```
## Rules
4. **Build:** `python <skill>/templates/to_docx.py HANDOVER-SOP.md -o "<Project Name> Handover SOP.docx" --pdf`. Over 4 pages: shorten cells, never drop a message.
5. **Hand over** the PDF. Problems for the dev team go in the chat (at most 5 lines), not in the SOP.
- Copy every label and message exactly from the code. Variable parts go in *italics*: "Couldn't download *Location*".
- Every wait is a number. Say plainly when the screen misleads ("Finished" while something failed).
- Say what clicking Run again does to the old results.
**Rules**
- Copy every label and message exactly from the code; variable parts in *italics* ("Couldn't download *Location*").
- Every wait is a number. Say plainly when the screen misleads.
- One row per message, one short line per cell.
- No file names, code, settings names, patient data, client names or passwords.
## Don't miss
Check the bot for each of these, and cover every one that applies in section 3 or 4:
**Don't miss:** check each of these and cover every one that applies in section 3 or 4:
1. Setup missing: login, file, driver. Which message shows?
2. The app or portal is slow or changed: timeouts, "not found".
3. Names in the input or mapping don't match the target app.