@charzhu/openjaw-agent 0.2.0

package/skills/desktop-cleanup.md

@@ -0,0 +1,82 @@
+---
+name: desktop-cleanup
+description: "Organize files on the desktop or any directory by categorizing into folders."
+whenToUse: "User asks to organize/clean their desktop"
+---
+
+# Skill: Desktop Cleanup & Organization
+
+## Description
+Organize files on the user's desktop or any directory by categorizing files into folders based on type, topic, or date. Handles deduplication and creates a clean folder structure.
+
+## When to Use
+- User asks to organize/clean their desktop
+- User asks to sort files in a directory
+- User says "整理一下桌面" or "帮我分类文件"
+
+## Steps
+
+### 1. Survey Current State
+```python
+import os
+
+path = os.path.expanduser('~/Desktop')
+entries = os.listdir(path)
+# Categorize: files vs directories, by extension
+```
+
+### 2. Classification Rules
+
+| Category | Extensions / Patterns | Folder Name |
+|----------|----------------------|-------------|
+| Documents | .pdf, .docx, .doc, .txt, .md | 工作文档 |
+| Spreadsheets | .xlsx, .xls, .csv | 数据表格 |
+| Presentations | .pptx, .ppt | 演示文稿 |
+| Images | .png, .jpg, .jpeg, .gif, .bmp, .svg | 图片 |
+| Code | .py, .js, .ts, .html, .css, .json | 代码文件 |
+| Apps | .lnk, .exe | [Categorize by app type] |
+| Archives | .zip, .rar, .7z, .tar.gz | 压缩包 |
+| Videos | .mp4, .avi, .mkv, .mov | 视频 |
+| Investment/Finance | *Gold*, *Fund*, *Stock*, 黄金*, 基金* | 投资分析 |
+
+### 3. Smart Categorization
+Don't just sort by extension — also check content/filename patterns:
+- Financial reports → 投资分析
+- PM/work reports → 工作文档
+- Screenshots → 图片 or Misc Files
+- App shortcuts → Group by function (Browsers, Development, etc.)
+
+### 4. Move Files Safely
+```python
+import shutil
+
+def safe_move(src, dst_dir, filename):
+    os.makedirs(dst_dir, exist_ok=True)
+    dst = os.path.join(dst_dir, filename)
+    if os.path.exists(dst):
+        # Add number suffix to avoid overwrite
+        base, ext = os.path.splitext(filename)
+        i = 1
+        while os.path.exists(dst):
+            dst = os.path.join(dst_dir, f"{base}_{i}{ext}")
+            i += 1
+    shutil.move(src, dst)
+```
+
+### 5. Respect Existing Structure
+- Don't move files that are already in organized folders
+- Don't touch system files (desktop.ini, etc.)
+- Preserve existing folder categorization
+- Ask before deleting duplicates
+
+### 6. Report Results
+After organizing, list:
+- How many files were moved
+- What folders were created
+- What the desktop looks like now
+
+## Important Notes
+- **Never delete files without asking** — only move
+- Skip `desktop.ini` and hidden files
+- Check for duplicate shortcuts before removing
+- Preserve existing folder structure — enhance, don't replace

package/skills/doc-coauthoring.md

@@ -0,0 +1,123 @@
+---
+name: doc-coauthoring
+description: "Guide the user through a 3-stage workflow for co-authoring documents."
+whenToUse: "User mentions writing documentation: write a doc, draft a proposal, create a spec"
+---
+
+# Skill: Doc Co-Authoring
+
+## Description
+Guide the user through a structured 3-stage workflow for co-authoring documents: PRDs, specs, proposals, decision docs, design docs, or any substantial writing. Adapted from Anthropic's doc-coauthoring skill for OpenJaw/PM context.
+
+## When to Use
+- User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"
+- User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC", "spec"
+- User says "帮我写个文档" or "写个proposal"
+- User seems to be starting a substantial writing task (not just a quick email)
+
+## Workflow Overview
+Offer the 3-stage workflow. If user declines, work freeform. If they accept:
+
+```
+Stage 1: Context Gathering → Stage 2: Refinement & Structure → Stage 3: Reader Testing
+```
+
+---
+
+## Stage 1: Context Gathering
+
+**Goal:** Close the knowledge gap between what the user knows and what Jon knows.
+
+### Initial Questions (ask these first)
+1. What type of document? (spec, decision doc, proposal, PRD...)
+2. Who's the primary audience? (leadership, peer PMs, engineering, cross-team...)
+3. What impact do you want when someone reads this?
+4. Is there a template or format to follow?
+5. Language preference? (English, Chinese, mixed)
+6. Any other constraints?
+
+### Info Dumping
+Encourage user to dump all context — don't worry about organizing:
+- Background on the project/problem
+- Related discussions (can point to Teams chats/channels — Jon can read them)
+- Why alternative solutions aren't being used
+- Timeline pressures or constraints
+- Technical architecture or dependencies
+- Stakeholder concerns
+
+**Jon's special capabilities for context gathering:**
+- Read Teams chat history: `teams_read_messages`
+- Read emails: `outlook_read_content` / `outlook_search`
+- Search memory: `memory_search`
+- Browse web for background: `web_search` / `web_fetch`
+
+### Clarifying Questions
+After initial dump, generate 5-10 numbered questions about gaps.
+User can answer in shorthand: "1: yes, 2: see the Teams chat, 3: no because backwards compat"
+
+**Exit condition:** When I can ask about edge cases and trade-offs without needing basics explained.
+
+---
+
+## Stage 2: Refinement & Structure
+
+**Goal:** Build the document section by section through brainstorming and iteration.
+
+### For Each Section:
+1. **Clarifying questions** — What should this section include?
+2. **Brainstorm 5-20 options** — Points, angles, data that might belong here
+3. **User curates** — "Keep 1,4,7. Remove 3. Combine 11 and 12."
+4. **Draft the section** — Write it out
+5. **Iterate** — User gives feedback, Jon makes surgical edits
+6. **Quality check** — After 3 iterations with no major changes, ask if anything can be cut
+
+### Section Ordering
+- Start with the section that has the most unknowns
+- Leave summary/intro sections for last
+- For decision docs: start with the core proposal
+- For specs: start with the technical approach
+
+### Near Completion (80%+ done)
+Re-read entire document and check for:
+- Flow and consistency across sections
+- Redundancy or contradictions
+- "Slop" — generic filler that doesn't carry weight
+- Whether every sentence earns its place
+
+---
+
+## Stage 3: Reader Testing
+
+**Goal:** Test the document with "fresh eyes" to catch blind spots.
+
+### Steps:
+1. **Predict reader questions** — Generate 5-10 questions a reader would ask
+2. **Test each question** — Re-read the doc as if seeing it for the first time
+3. **Check for:**
+   - Ambiguity or unclear phrasing
+   - Assumed knowledge that isn't stated
+   - Internal contradictions
+   - Missing context for new readers
+4. **Report & fix** — List issues found, fix them
+
+### Exit Condition
+When the doc consistently makes sense to a "fresh reader" without needing verbal explanation.
+
+---
+
+## Final Steps
+1. User does a final read-through (they own the document)
+2. Double-check facts, links, technical details
+3. Verify it achieves the intended impact
+
+## Output Options
+- Save as markdown file
+- Generate as PDF (use create-pdf-report skill)
+- Generate as Word document (use create-docx skill)
+- Send via email (use email-with-attachment skill)
+
+## Style Notes
+- Be direct and procedural — don't oversell the process
+- If user wants to skip a stage, let them
+- Don't reprint the whole doc after every edit — show what changed
+- Always give user agency to adjust the process

package/skills/email-drafting.md

@@ -0,0 +1,141 @@
+---
+name: email-drafting
+description: "Draft professional, audience-aware emails for any purpose."
+whenToUse: "User asks to write/draft an email"
+---
+
+# Skill: Email Drafting
+
+## Description
+Draft professional, audience-aware emails for any purpose — status updates, leadership communications, cross-team requests, follow-ups, escalations. Adapted for Microsoft PM context with Chinese/English bilingual support.
+
+## When to Use
+- User asks to write/draft an email
+- User says "帮我写封邮件" or "draft an email"
+- User wants to reply to an email and needs help with wording
+- User needs to escalate, follow up, or request something via email
+
+## Workflow
+
+### 1. Understand the Context
+Before drafting, clarify:
+- **Audience**: Who is receiving? (skip-level leader, peer PM, engineer, external partner)
+- **Purpose**: What action do you want? (inform, request, escalate, follow up)
+- **Tone**: Formal? Casual? Urgent?
+- **Language**: English? Chinese? Mixed?
+
+### 2. Structure by Purpose
+
+#### Status Update / FYI
+```
+Subject: [Topic] — [Key takeaway in 5 words]
+
+Hi [Name],
+
+[1 sentence context — why you're writing]
+
+Key updates:
+• [Update 1 with metric/impact]
+• [Update 2 with metric/impact]
+• [Update 3 with metric/impact]
+
+Next steps: [What happens next, who owns it]
+
+[Closing]
+```
+
+#### Request / Ask
+```
+Subject: [Action Needed] — [Specific request]
+
+Hi [Name],
+
+[1 sentence context]
+[1 sentence why this matters]
+
+Ask: [Clear, specific request]
+Timeline: [When you need it by]
+
+[Why this is important to them / what's in it for them]
+
+Thanks,
+```
+
+#### Escalation
+```
+Subject: [Urgent/Priority] — [Issue] impacting [scope]
+
+Hi [Name],
+
+Issue: [What's happening, since when]
+Impact: [Quantified impact — users affected, SLA at risk, revenue impact]
+Root cause: [Known/investigating]
+What we need: [Specific ask with timeline]
+Mitigation: [What we're doing in the meantime]
+```
+
+#### Follow-up (Gentle Nudge)
+```
+Subject: Re: [Original subject]
+
+Hi [Name],
+
+Just circling back on [topic] from [date/meeting].
+[Brief reminder of what was discussed/agreed]
+
+Could you [specific action] by [date]?
+
+Happy to discuss if there are any blockers.
+```
+
+### 3. Style Rules
+- **Subject lines**: Front-load the key info. No vague subjects like "Quick question"
+- **Length**: Shorter is better. If > 5 paragraphs, it should be a doc
+- **Action items**: Bold or bullet them. Don't bury asks in paragraphs
+- **CC etiquette**: Only CC people who need to know, not everyone
+- **Chinese/English mix**: Use English for technical terms, Chinese for narrative when writing to Chinese colleagues
+- **Avoid**: "As per my last email", "Please advise", "Hope this email finds you well"
+
+### 4. Sending
+- Use `outlook_compose_email` for plain text
+- Use Outlook REST API for emails with attachments (see email-with-attachment skill)
+- **Always show draft to user before sending** (send confirmation gate)
+
+## Templates for Common Scenarios
+
+### Weekly Team Update (Chinese)
+```
+Subject: [Team Name] 周报 — W[XX]
+
+Hi all,
+
+本周进展：
+• [重要里程碑/发布]
+• [关键指标变化]
+
+下周计划：
+• [计划1]
+• [计划2]
+
+风险/阻塞：
+• [如有]
+
+Thanks,
+```
+
+### Cross-team Request (English)
+```
+Subject: [Request] — Need [X] support for [project] by [date]
+
+Hi [Name],
+
+We're working on [project/feature] which [brief context].
+To unblock [specific next step], we need your team's help with:
+
+1. [Specific ask]
+2. [Specific ask]
+
+Timeline: Ideally by [date] to meet our [milestone].
+
+Happy to set up a quick sync if helpful. Let me know!
+```

package/skills/email-with-attachment.md

@@ -0,0 +1,114 @@
+---
+name: email-with-attachment
+description: "Send emails with file attachments via Outlook REST API v2.0."
+whenToUse: "User asks to email a file/document/PDF/PPTX"
+---
+
+# Skill: Email with Attachment (Outlook REST API)
+
+## Description
+Send emails with file attachments via Outlook REST API v2.0. Use this when the Graph channel's `outlook_compose_email` tool doesn't support attachments.
+
+## When to Use
+- User asks to email a file/document/PDF/PPTX
+- Need to send email with attachment
+- Graph channel email was sent but attachment is missing
+
+## IMPORTANT: Use Outlook REST API, NOT Graph API, NOT COM
+- Our token audience is `https://outlook.office.com` (not `https://graph.microsoft.com`)
+- COM `$mail.Send()` is unreliable — emails get stuck in Outbox with lost attachments
+- **Outlook REST API v2.0 is the ONLY working method** ✅
+
+## Steps
+
+### 1. Create the File First
+Generate the file (PDF, PPTX, DOCX, etc.) and save to a known path:
+- Temp: system temp directory (use `tempfile.gettempdir()` in Python or `$env:TEMP` in PS)
+- Desktop: `~/Desktop/{filename}` (use `os.path.expanduser('~/Desktop')` in Python)
+
+### 2. Send via Outlook REST API v2.0
+```python
+import json, os, base64, urllib.request, urllib.error
+
+# Read token
+token_path = os.path.expanduser("~/.graph-token/tokens/outlook-mail.json")
+with open(token_path, 'r') as f:
+    token_data = json.load(f)
+access_token = token_data['access_token']
+
+# Read and encode file
+with open(file_path, 'rb') as f:
+    file_b64 = base64.b64encode(f.read()).decode('utf-8')
+
+# Build email payload
+email_payload = {
+    "Message": {
+        "Subject": subject,
+        "Body": {"ContentType": "Text", "Content": body_text},
+        "ToRecipients": [
+            {"EmailAddress": {"Address": recipient}}
+        ],
+        "Attachments": [
+            {
+                "@odata.type": "#Microsoft.OutlookServices.FileAttachment",
+                "Name": filename,
+                "ContentType": content_type,  # e.g., "application/pdf"
+                "ContentBytes": file_b64
+            }
+        ]
+    },
+    "SaveToSentItems": "true"
+}
+
+# Send
+url = "https://outlook.office.com/api/v2.0/me/sendmail"
+data = json.dumps(email_payload).encode('utf-8')
+req = urllib.request.Request(url, data=data, method='POST')
+req.add_header('Authorization', f'Bearer {access_token}')
+req.add_header('Content-Type', 'application/json')
+
+response = urllib.request.urlopen(req)
+# Status 202 = success
+```
+
+### 3. Content Types
+| File Type | Content-Type |
+|-----------|-------------|
+| PDF | `application/pdf` |
+| DOCX | `application/vnd.openxmlformats-officedocument.wordprocessingml.document` |
+| PPTX | `application/vnd.openxmlformats-officedocument.presentationml.presentation` |
+| XLSX | `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet` |
+| PNG | `image/png` |
+| ZIP | `application/zip` |
+
+### 4. For HTML Body
+Change `"ContentType": "Text"` to `"ContentType": "HTML"` and use HTML in Content.
+
+### 5. For CC/BCC
+Add to the Message object:
+```json
+"CcRecipients": [{"EmailAddress": {"Address": "cc@microsoft.com"}}],
+"BccRecipients": [{"EmailAddress": {"Address": "bcc@microsoft.com"}}]
+```
+
+### 6. Multiple Attachments
+Add more items to the Attachments array.
+
+## Important Notes
+- Token is at `~/.graph-token/tokens/outlook-mail.json`
+- API endpoint: `https://outlook.office.com/api/v2.0/me/sendmail`
+- Status 202 = Accepted (success)
+- Max attachment size: ~35MB (base64 encoded)
+- **Always confirm with user before sending** (send confirmation gate)
+- For self-send: use the user's own email address
+
+## Troubleshooting
+| Problem | Fix |
+|---------|-----|
+| 401 Invalid audience | Make sure using `outlook.office.com` NOT `graph.microsoft.com` |
+| 401 Token expired | Run refresh-token skill first |
+| COM Send() stuck in Outbox | Don't use COM — use this REST API method |
+| Large file fails | Split into chunks or compress first |
+
+## Verification
+Check response status code: 202 = success.

package/skills/internal-comms.md

@@ -0,0 +1,88 @@
+---
+name: internal-comms
+description: "Write professional internal communications: status reports, 3P updates, and summaries."
+whenToUse: "User asks to write a status report or weekly update"
+---
+
+# Skill: Internal Communications
+
+## Description
+Write professional internal communications for Microsoft PM context: status reports, 3P updates, weekly summaries, team newsletters, meeting recaps, and email drafts. Adapted from Anthropic's internal-comms skill for CharZ's team.
+
+## When to Use
+- User asks to write a status report or weekly update
+- User asks to draft an email to leadership or team
+- User asks for 3P updates (Progress, Plans, Problems)
+- User asks for meeting recap or summary
+- User asks to write any internal communication
+- User says "帮我写个周报" or "写个update"
+
+## Communication Types
+
+### 1. 3P Update (Progress / Plans / Problems)
+```
+## 📊 [Team/Area] Weekly Update — [Date]
+
+### ✅ Progress (What we shipped/achieved)
+- [Metric improvement]: Describe quantified impact
+- [Feature shipped]: What it does, who benefits
+- [Milestone reached]: Context and significance
+
+### 📋 Plans (What's coming next)
+- [Next deliverable]: ETA, owner, dependencies
+- [Investigation]: What we're exploring and why
+- [Upcoming milestone]: Target date and criteria
+
+### ⚠️ Problems (Blockers & risks)
+- [Blocker]: Impact, mitigation, help needed
+- [Risk]: Probability, impact, contingency plan
+- [Dependency]: Who/what we're waiting on
+```
+
+### 2. Leadership Update
+- **Keep it to 5-7 bullet points max**
+- Lead with **impact and metrics**, not activities
+- Use "So what?" test — every bullet should answer why leadership cares
+- Include 1 clear ask if needed
+- Tone: Confident, concise, data-backed
+
+### 3. Team Newsletter / Announcement
+- Lead with the most exciting news
+- Include people shoutouts (builds culture)
+- Keep sections scannable (headers, bullets, bold key info)
+- End with clear action items or dates
+
+### 4. Meeting Recap
+```
+## 📝 Meeting Recap: [Meeting Name] — [Date]
+
+### Attendees
+[List key attendees]
+
+### Key Decisions
+1. [Decision]: Rationale and owner
+2. [Decision]: Impact and timeline
+
+### Action Items
+| Owner | Action | Due Date |
+|-------|--------|----------|
+| Name  | Task   | Date     |
+
+### Open Questions
+- [Question]: Who needs to answer, by when
+```
+
+### 5. Incident Report
+- Timeline of events (UTC timestamps)
+- Root cause analysis
+- Customer impact (quantified)
+- Mitigation steps taken
+- Follow-up actions with owners and dates
+
+## Style Guidelines for CharZ's Team
+- **Language**: Mix Chinese and English naturally (Chinese for narrative, English for technical terms)
+- **Tone**: Professional but not stiff — CharZ's team has a casual, friendly culture
+- **Data first**: Always quantify impact when possible
+- **Attribution**: Credit specific people by name
+- **Brevity**: If it can be said in 3 bullets, don't use 5
+- **Emoji**: Use sparingly for section headers, not in every sentence

package/skills/meeting-summarizer.md

@@ -0,0 +1,72 @@
+---
+name: meeting-summarizer
+description: "Summarize meeting content into structured notes with decisions and action items."
+whenToUse: "User provides meeting transcript or notes to summarize"
+---
+
+# Skill: Meeting Summarizer
+
+## Description
+Summarize meeting content into structured notes with decisions, action items, and follow-ups. Works with meeting transcripts, chat logs, email threads, or verbal descriptions.
+
+## When to Use
+- User provides meeting transcript or notes to summarize
+- User says "帮我整理会议纪要" or "summarize this meeting"
+- User pastes a long chat/email thread and wants key points
+- After reading Teams/Outlook content that contains meeting discussions
+
+## Workflow
+
+### 1. Input Sources
+- Meeting transcript (text pasted by user)
+- Teams chat history (read via `teams_read_messages`)
+- Email thread (read via `outlook_read_content`)
+- User's verbal description of what happened
+
+### 2. Output Structure
+```markdown
+# Meeting Summary: [Meeting Name]
+**Date:** [Date] | **Duration:** [if known]
+**Attendees:** [List]
+
+## Key Decisions
+1. **[Decision]** — [Brief rationale]
+2. **[Decision]** — [Brief rationale]
+
+## Discussion Highlights
+- [Topic 1]: [Key points, different viewpoints, conclusion]
+- [Topic 2]: [Key points, different viewpoints, conclusion]
+
+## Action Items
+| # | Owner | Action | Due Date | Status |
+|---|-------|--------|----------|--------|
+| 1 | [Name] | [Task] | [Date] | Pending |
+| 2 | [Name] | [Task] | [Date] | Pending |
+
+## Open Questions
+- [Question needing resolution] — Owner: [Name]
+
+## Next Meeting
+- [Date/time if scheduled]
+- [Topics to cover]
+```
+
+### 3. Processing Rules
+- **Decisions**: Extract only clearly agreed-upon outcomes, not suggestions
+- **Action items**: Must have an owner and ideally a due date
+- **Be concise**: Meeting was 1 hour? Summary should be < 1 page
+- **Separate facts from opinions**: Note where there was disagreement
+- **Prioritize**: Lead with decisions and actions, not discussion play-by-play
+- **Language**: Match the language of the original content. If mixed, use the dominant language
+
+### 4. For Long Transcripts
+- First pass: Identify speakers and topic changes
+- Second pass: Extract decisions and action items
+- Third pass: Summarize discussion points
+- Final: Organize into template
+
+### 5. Distribution
+After user approves:
+- Send via email (`outlook_compose_email` or REST API with attachment)
+- Post to Teams chat/channel (`teams_send_message`)
+- Save as PDF (use create-pdf-report skill)

package/skills/proofreading.md

@@ -0,0 +1,77 @@
+---
+name: proofreading
+description: "Review and improve text for grammar, spelling, clarity, tone, and style."
+whenToUse: "User asks to review/proofread/polish text before sending"
+---
+
+# Skill: Proofreading & Polish
+
+## Description
+Review and improve text for grammar, spelling, clarity, tone, and style. Works for emails, documents, chat messages, and presentations in both English and Chinese.
+
+## When to Use
+- User asks to review/proofread/polish text before sending
+- User says "帮我看看这个" or "check this before I send"
+- User wants to improve the quality of a draft
+- Before sending important emails or documents
+
+## Workflow
+
+### 1. Quick Scan (Automated Checks)
+- Spelling errors
+- Grammar mistakes (subject-verb agreement, tense, articles)
+- Punctuation (missing periods, comma splices, semicolon misuse)
+- Repeated words
+- Inconsistent formatting (bullet styles, heading levels)
+
+### 2. Clarity Pass
+- Sentences > 30 words → suggest breaking up
+- Passive voice → suggest active where appropriate
+- Vague language ("some", "various", "things") → suggest specifics
+- Jargon check → is the audience familiar with these terms?
+- Remove filler: "basically", "actually", "in order to", "at this point in time"
+
+### 3. Tone Check
+| Audience | Tone Adjustments |
+|----------|-----------------|
+| Leadership/skip-level | More confident, less hedging, lead with impact |
+| Peer PM | Conversational but professional |
+| Engineering team | Technical, precise, action-oriented |
+| External partner | Formal, diplomatic, clear |
+| Team chat | Casual OK, but still clear |
+
+### 4. Chinese-Specific Checks
+- 的地得 usage (的=noun modifier, 地=adverb modifier, 得=complement)
+- 了/着/过 tense markers
+- Avoid 翻译腔 (translationese)
+- Consistent use of 你/您 (formality)
+- Punctuation: Chinese punctuation marks (，。！？) vs English
+
+### 5. English-Specific Checks
+- Article usage (a/an/the) — especially tricky for Chinese speakers
+- Preposition choice (in/on/at, to/for/with)
+- Countable vs uncountable nouns
+- Verb tense consistency
+- Oxford comma consistency
+
+### 6. Output Format
+```
+## Proofread Result
+
+### Changes Made
+1. [Original] → [Corrected] — [Reason]
+2. [Original] → [Corrected] — [Reason]
+
+### Suggestions (Optional)
+- Consider rephrasing: "[sentence]" → "[suggestion]" for [clarity/tone/conciseness]
+
+### Polished Version
+[Full corrected text]
+```
+
+### 7. Rules
+- **Don't change the author's voice** — improve, don't rewrite
+- **Preserve technical terms** exactly as written
+- **Mark changes clearly** so user can accept/reject each one
+- **Be opinionated on errors, gentle on style suggestions**
+- **For sensitive content**: Follow confidentiality rules (no salary/review info leaking through corrections)