feat: archive zoo_backup for home sync
This commit is contained in:
Patrick Plate
@@ -0,0 +1,132 @@
|
||||
---
|
||||
name: webex-communicator
|
||||
description: Compose, read, analyze, and send Webex messages in Patrick's personal communication style. Use when asked to write Webex messages, read Webex conversations, summarize chat threads, or send messages to ADP colleagues.
|
||||
---
|
||||
|
||||
# Webex Communicator
|
||||
|
||||
## When to use
|
||||
|
||||
- User asks to write/send a Webex message ("schreib X dass Y", "sag X mal...")
|
||||
- User asks to read/summarize Webex conversations ("was will X", "lies mal X")
|
||||
- User asks to check a Webex room or find a contact
|
||||
- User asks to extract action items from a Webex thread
|
||||
|
||||
## When NOT to use
|
||||
|
||||
- Email composition (not Webex)
|
||||
- Teams messages (use Teams tools instead)
|
||||
- Slack or other chat platforms
|
||||
|
||||
## Inputs
|
||||
|
||||
| Input | Required | Example |
|
||||
|-------|----------|---------|
|
||||
| Recipient or room | Yes | "Nadine", "Klaus", room name |
|
||||
| Message intent | Yes (for compose) | "dass der Fix für EAU drin ist" |
|
||||
| Context | Optional | Ticket key, technical detail |
|
||||
|
||||
## Workflow
|
||||
|
||||
### Compose & Send
|
||||
|
||||
1. Resolve the recipient from the contact register below
|
||||
2. If recipient unknown, use `webex_list_people(display_name="...")` to find them
|
||||
3. Compose the message following Patrick's style rules (see below)
|
||||
4. **Show the draft to Patrick — NEVER auto-send**
|
||||
5. On approval, send via `webex_send_message(person_email=..., markdown=...)`
|
||||
6. If BigMind session is active, optionally pull current work context for richer messages
|
||||
|
||||
### Read & Summarize
|
||||
|
||||
1. Resolve the contact or room
|
||||
2. For 1:1: `webex_list_direct_messages(person_email=..., max_results=20)`
|
||||
3. For rooms: `webex_list_messages(room_id=..., max_results=20)`
|
||||
4. Summarize: key topics, open questions, action items
|
||||
5. Present summary in German
|
||||
|
||||
### Find Contact / Room
|
||||
|
||||
1. `webex_list_people(display_name="...")` or `webex_list_people(email="...")`
|
||||
2. `webex_list_rooms(max_results=50)` to browse rooms
|
||||
|
||||
## Patrick's Communication Style
|
||||
|
||||
### Grundton
|
||||
Professionell-locker, direkt, knapp. Kein Smalltalk-Overhead. Sofort zum Punkt.
|
||||
|
||||
### Formalität
|
||||
- Immer "Du", nie "Sie" — auch bei GET-Support und Management
|
||||
- Abschluss: NIE "Viele Grüße" oder "LG" im Chat. Nie.
|
||||
|
||||
### Satzlänge
|
||||
Kurz bis mittel. Einzelne Wörter als Antwort normal ("Gerne", "JO", "35 Min").
|
||||
Längere Nachrichten nur bei technischen Erklärungen — dann strukturiert mit Markdown.
|
||||
|
||||
### Emojis
|
||||
- Häufig: 😜 (ironisch), 🧐 (neugierig), 🙂 (freundlich)
|
||||
- Nie: ❤️, 👍, 🙏, 🎉
|
||||
|
||||
### Typische Formulierungen
|
||||
- "Ich guck mir das mal an"
|
||||
- "Das riecht nach..."
|
||||
- "Kannst machen"
|
||||
- "kurze Info —"
|
||||
- "falls du ... willst"
|
||||
- "erstmal richtig angucken"
|
||||
- "nach deiner Zeit"
|
||||
- "JO" (Bestätigung)
|
||||
|
||||
### Anti-Patterns (NIEMALS verwenden)
|
||||
- "Viele Grüße, Patrick"
|
||||
- "Könnten Sie bitte..."
|
||||
- Lange Einleitungen ("Ich hoffe es geht dir gut...")
|
||||
- Übertriebene Höflichkeitsfloskeln
|
||||
- Ausrufezeichen am Satzende (sparsam, wenn überhaupt)
|
||||
- Doppelpunkt-Smileys :) — nur echte Emojis
|
||||
|
||||
## Contact Register
|
||||
|
||||
| Name | Email | Greeting | Tone | Topics |
|
||||
|------|-------|----------|------|--------|
|
||||
| Nadine Homann | nadine.homann@adp.com | "Hey Nadine," oder "Hey," | Locker-professionell, informativ | Tickets, Refinement, MCP |
|
||||
| Klaus Prüger | klaus.prueger@adp.com | Kein Gruß, direkt rein | Sehr locker, Tech-Buddy | MCP, Tooling, AI |
|
||||
| Christian Petersen | christian.petersen@adp.com | Kein Gruß, direkt rein | Locker, Peer-to-Peer | Code, Architektur |
|
||||
| Elias-Connor Andres | elias-connor.andres@adp.com | Kein Gruß, direkt rein | Sehr locker, freundschaftlich | Büro, Tech |
|
||||
| Marina Koch | marina.koch@adp.com | "Hallo Marina," | Professionell-freundlich, sachlich | Siebel, Kundenfixes |
|
||||
| Henrik Holle | henrik.holle@adp.com | Kein Gruß, direkt rein | Direkt, knapp, sachlich | eAU, Tooling |
|
||||
| Daniel Frase | daniel.frase@adp.com | "Hey," oder direkt rein | Kollegial-technisch | euBP, DSBD |
|
||||
| Kai Müller | kai.mueller@adp.com | Kein Gruß, direkt rein | Knapp, pragmatisch | Jenkins, Deploy |
|
||||
|
||||
### Unknown contacts
|
||||
|
||||
For contacts not in the register: use "Hey," greeting, locker-professionell tone. Still "Du", still no "Viele Grüße".
|
||||
|
||||
## Context Enrichment
|
||||
|
||||
When composing messages about tickets or technical topics:
|
||||
1. Search BigMind: `memory_search_facts("<topic>")` for current context
|
||||
2. Check Jira: `retrieve_ticket_details("<TICKET_KEY>")` if a ticket is referenced
|
||||
3. Weave relevant details naturally into the message — don't dump raw data
|
||||
|
||||
## Examples
|
||||
|
||||
### Short status update to Nadine
|
||||
```
|
||||
Hey Nadine, der Fix für ESIDEPAISY-12081 ist drin. Kannst du das Ticket auf In Review setzen?
|
||||
```
|
||||
|
||||
### Technical info to Klaus
|
||||
```
|
||||
hab mir das MCP-Problem angeguckt — lag am SSL-Cert. Hab den Pfad jetzt auf adp-trusted-certs.pem umgestellt, läuft 🙂
|
||||
```
|
||||
|
||||
### Request to Marina
|
||||
```
|
||||
Hallo Marina, ich bräuchte die Kundennummer für den Siebel-Case von gestern. Kannst du mir die nach deiner Zeit schicken?
|
||||
```
|
||||
|
||||
### Quick confirmation to Henrik
|
||||
```
|
||||
JO, ist deployed.
|
||||
```
|
||||
Reference in New Issue
Block a user