activity-synthesis
Activity Synthesis
When users ask about their own work activity, use Glean's user_activity and memory tools to provide a synthesized view of their contributions.
Tool Naming
See the glean-tools-guide skill for Glean MCP tool naming conventions. Tools follow the pattern mcp__glean_[server-name]__[tool] where the server name is dynamic.
When This Applies
Use this approach when users ask:
- "What have I been working on?"
- "What did I do last week?"
- "Summarize my recent activity"
- "What projects have I touched?"
- "Help me remember what I worked on"
- "What should I put in my status update?"
BE SKEPTICAL
Not every activity is worth highlighting. Before including items, evaluate:
Significance Test
- Is this a meaningful contribution?
- ✅ INCLUDE: Created docs, made decisions, completed tasks
- ⚠️ MAYBE: Reviewed items, attended meetings
- ❌ EXCLUDE: Just viewed something, minor edits, noise
Accomplishment Test
- Did the user actually accomplish something?
- ✅ INCLUDE: Finished tasks, shipped features, resolved issues
- ⚠️ CONTEXT: In-progress work (note the status)
- ❌ EXCLUDE: Started but abandoned, just browsing
Relevance Test
- Does this reflect real work the user did?
- ✅ INCLUDE: Direct contributions with clear ownership
- ❌ EXCLUDE: Auto-generated, mass-distributed, tangential CC's
Filter Out:
- Automated notifications
- Documents the user only viewed briefly
- Mass emails or announcements received
- Activity with no meaningful outcome
Quality over quantity: A focused summary of 5-7 accomplishments is better than 20 trivial activities.
Primary Tools
| Tool | Purpose | When to Use |
|---|---|---|
user_activity |
Get work activity feed | Primary source for user's actions |
memory |
Get context about user | Roles, projects, responsibilities |
search |
Find documents by user | Documents created/updated |
meeting_lookup |
Find meetings | Meetings attended |
Query Patterns
Get Activity Feed
user_activity start_date:[YYYY-MM-DD] end_date:[YYYY-MM-DD]
Note: end_date is exclusive.
Get User Context
memory - read all categories
Returns roles, responsibilities, active projects, recent topics.
Find User's Documents
search query="*" from="me" updated="past_week"
search query="*" owner="me"
Synthesis Approach
- Gather raw data from user_activity and search
- Group by theme: Projects, meetings, documents, collaborations
- Identify patterns: What topics appear repeatedly?
- Highlight accomplishments: Completed items, decisions made
- Note open items: Things still in progress
Output Format
Present activity in a scannable format:
## Your Recent Activity: [Time Period]
### By Project
- **[Project A]**: [X activities] - [summary]
- **[Project B]**: [Y activities] - [summary]
### Key Actions
- [Action 1] - [date]
- [Action 2] - [date]
### Collaborations
- Worked with [Person] on [topic]
Relationship to Commands
For comprehensive activity summaries, suggest:
/glean-productivity:my-week- Full weekly summary with analysis/glean-productivity:daily-briefing- What happened in last 24 hours
More from gleanwork/claude-plugins
code-exploration
Use when the user asks about internal code, implementations, patterns across repositories, or needs to understand how something is built. Triggers on "how is X implemented", "where is the code for", "find the implementation of", "what repos contain", "who wrote the code for", or code architecture questions about internal systems.
15glean-tools-guide
Use when Glean MCP tools are available and you need guidance on which tool to use, how to format queries, or best practices for enterprise search. This skill provides tool selection logic and query optimization for Glean integrations. Auto-triggers when mcp__glean tools are being considered.
14project-awareness
Use when the user asks about project status, ownership, or context. Triggers on phrases like "status of X project", "who owns Y", "what's happening with Z", "project update", "where does the project stand", "what's the state of", "who's working on", or when needing quick project context without a full analysis.
13people-lookup
Use when the user asks about people, employees, team members, org structure, or expertise. Triggers on phrases like "who works on", "who is responsible for", "who owns", "find someone who knows", "who should I talk to", "who reports to", "team members", "org chart", or any question starting with "who" about the company.
12enterprise-search
Use when the user asks about company documents, internal wikis, policies, specifications, design docs, RFCs, or enterprise knowledge. Triggers on phrases like "find the doc about", "what's our policy on", "where is the spec for", "company guidelines", "internal documentation", or when searching for information that would be in enterprise systems rather than the local codebase.
12skill-creation-guide
Auto-triggers when users discuss creating skills or ask about SKILL.md format. Triggers on phrases like "create a skill", "write a skill", "make a skill", "new skill", "SKILL.md format", "skill structure", "how do skills work", "skill best practices", or when the user wants to add custom behavior to Claude Code.
11