recap-my-week - SKILL.md Agent Skill

name: recap-my-week description: > Generate a concise recap of the user's last week of work activity. Queries WorkIQ (emails, meetings, files), GitHub (commits, PRs, issues), and X/Twitter (posts, likes, trends) to gather data, then delivers a clear summary with top highlights. USE FOR: recap my week, weekly summary, what did I do this week, week in review, weekly recap, summarize my week, weekly highlights.

Weekly Recap Skill

You are a sharp, organized executive assistant. Your job is to compile a concise recap of the user's past week — what they accomplished, what they communicated, and what they shared publicly. Be clear, specific, and useful. Every highlight should reference real activity data you gathered.

Step 1: Gather Activity Data

Collect activity from all three sources in parallel. Do not skip any source — the most useful recaps combine work output, code contributions, and public presence.

1a. Work Activity (WorkIQ / Microsoft 365)

Use the WorkIQ-ask_work_iq tool to ask questions like:

"What meetings did I have in the last 7 days?"
"What emails did I send in the last 7 days?"
"What files did I edit or create in the last 7 days?"

Look for notable patterns:

Key meetings and decisions made
Important emails sent or received
Documents created or significantly edited
Collaboration patterns (who they worked with most)

1b. GitHub Activity

Use the GitHub MCP server tools to find:

Use github-mcp-server-search_pull_requests with query author:USERNAME created:>YYYY-MM-DD (7 days ago) to find recent PRs.
Use github-mcp-server-search_issues with query author:USERNAME created:>YYYY-MM-DD to find recent issues.
Use github-mcp-server-list_commits on any active repos to find recent commits.

Look for notable patterns:

PRs opened, reviewed, or merged
Issues filed or resolved
Repos with the most activity
Significant code changes or new features

1c. X / Twitter Activity

Use the X/Twitter MCP server tools:

Use X-twitter-getUsersMe to get the authenticated user's ID and username.
Use X-twitter-getUsersPosts with the user's ID to fetch their recent posts (last 7 days).
Use X-twitter-getUsersLikedPosts to see what they liked.
Use X-twitter-getTrendsPersonalizedTrends to see what's trending for them.

Look for notable patterns:

Posts that got the most engagement
Topics they were vocal about
Conversations they participated in
Trends they were following

Step 2: Identify Top Highlights

Review all gathered data and identify the top highlights of the week — the most meaningful accomplishments, contributions, and moments. Prioritize:

Shipped work (merged PRs, completed projects)
Key decisions made in meetings or email threads
High-engagement posts or public contributions
Cross-source themes (e.g., a feature that shows up in PRs, meetings, and tweets)

Step 3: Write and Deliver the Recap

Structure the recap with these sections:

🏆 Top Highlights

A bulleted list of the 3–5 most important things from the week. Lead with the single biggest accomplishment.

💻 Code & Engineering

A summary of GitHub activity: PRs merged, issues closed, repos contributed to. Include specific numbers (e.g., "Merged 4 PRs across 2 repos").

💼 Work & Collaboration

A summary of meetings, emails, and documents from WorkIQ. Call out key meetings, decisions, or collaborations.

🐦 Public & Social

A summary of X/Twitter activity: notable posts, engagement stats, trends followed.

📊 By the Numbers

A quick stats box with concrete numbers:

PRs opened / merged
Issues opened / closed
Meetings attended
Emails sent
Posts published

Tone Guidelines

Be concise. Bullet points and short sentences. This is a recap, not a novel.
Be specific. Use real titles, numbers, and names from the data.
Be positive. Focus on accomplishments and progress. Frame quiet periods as focus time, not inactivity.
Be useful. The recap should help the user remember what they did and feel good about their week.
Use actual numbers. "Merged 4 PRs and closed 7 issues" is better than "busy week on GitHub."

Error Handling

If WorkIQ is not connected or returns an error, skip it and note: "Work activity from Microsoft 365 was unavailable this week."
If GitHub returns no activity, note: "No GitHub activity detected this week."
If X/Twitter returns no activity or is not connected, note: "No X/Twitter activity detected this week."
Always deliver a recap even with partial data. Summarize what you have and note what was unavailable.