Skip to content

feat: improve skill score for using-glean-productivity #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rohan-tessl wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: improve skill score for using-glean-productivity #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 40 additions & 6 deletions plugins/glean-productivity/skills/using-glean-productivity/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: using-glean-productivity
description: Synthesize the user's own work activity, priorities, and recent context using Glean. Use when the user asks about their recent work, what they accomplished, what's urgent, what needs their attention, or wants help with status updates, 1:1 prep, or weekly summaries.
description: "Retrieve, filter, and summarize the user's own work activity, priorities, and recent context from Glean. Use when the user asks about their recent work, what they accomplished, what's urgent, what needs their attention, or wants help with status updates, 1:1 prep, or weekly summaries."
when_to_use: |
Trigger phrases include "what have I been working on", "what did I do last week", "what should I focus on", "what's urgent", "what needs my attention", "summarize my week", "help me with my status update", "1:1 prep", "what's blocking me", "what can't wait", "morning briefing", "what happened while I was out".

Expand All @@ -13,12 +13,48 @@ This skill drives queries about the user's own work life — their recent activi

## Two shapes of question

Most personal-productivity asks fall into two shapes:

- **Activity / accomplishments** — "what did I work on?", "summarize my week", "what shipped?". See [reference/activity.md](reference/activity.md).
- **Priorities / blockers** — "what's urgent?", "what needs my attention?", "what's waiting on me?". See [reference/priorities.md](reference/priorities.md).

The two overlap (a recent activity feed is the substrate for triaging priorities), but the *output* the user wants is different: activity is retrospective, priorities are prospective.
Activity is retrospective; priorities are prospective. The workflow below covers both.

## Core workflow

1. **Load personalization context.** Call `read_memory(action="read", category="ActiveProjects")` and optionally `RolesAndResponsibilities`. These themes drive how results are grouped.

2. **Pull the activity feed.** Call `user_activity(start_date="YYYY-MM-DD", end_date="YYYY-MM-DD")` for the requested window. Remember `end_date` is exclusive — to include all of Friday, set `end_date` to Saturday.

3. **Supplement with meetings and docs.** Call `meeting_lookup` for the same window, and `search` with `from:me` or `owner:me` to catch authored documents.

4. **Filter and classify.** From the combined results:
- **Include**: created docs, shipped code, decisions made, tasks completed, meaningful comments
- **Demote**: brief views, auto-generated notifications, mass announcements, peripheral involvement
- For priority queries, apply the urgency triage from [reference/priorities.md](reference/priorities.md)

5. **Validate before presenting.** Check that results are non-empty. If the feed is sparse, say so honestly — don't pad. Suggest a wider date range if appropriate.

6. **Group and format.** Use `ActiveProjects` themes as the grouping axis when available. Otherwise group by repo, project, or topic. Cite every claim with a link to its source doc, meeting, or commit.

### Example: "summarize my week"

```
→ read_memory(action="read", category="ActiveProjects")
# Returns: ["Auth migration", "API v3 launch", "Onboarding revamp"]

→ user_activity(start_date="2025-05-19", end_date="2025-05-24")
# Returns: 34 items — filter down to 8 meaningful contributions

→ meeting_lookup(start_date="2025-05-19", end_date="2025-05-24")
# Returns: 6 meetings — extract action items assigned to user

→ Output grouped by ActiveProjects themes, with citations:
## May 19–23 — your week
### Auth migration
- Merged token-rotation PR (#412) — [link]
- Resolved session-storage compliance flag with legal — [meeting notes]
### API v3 launch
- Published updated rate-limit docs — [link]
```

## Tool reference lives in glean-core

Expand All @@ -29,8 +65,6 @@ The two overlap (a recent activity feed is the substrate for triaging priorities
- [`reference/search.md`](../../../../glean-core/skills/using-glean/reference/search.md) — for documents the user authored or was mentioned in
- [`reference/meeting-lookup.md`](../../../../glean-core/skills/using-glean/reference/meeting-lookup.md) — for meetings the user attended

This skill carries the *workflow* on top.

## Cross-cutting rules

1. **Quality over volume.** A status update of 5 real accomplishments beats a list of 20 trivial activities. Filter aggressively per [reference/activity.md](reference/activity.md).
Expand Down