CtrlK
BlogDocsLog inGet started
Tessl Logo

using-glean-productivity

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.

74

2.16x
Quality

63%

Does it follow best practices?

Impact

93%

2.16x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/glean-productivity/skills/using-glean-productivity/SKILL.md
SKILL.md
Quality
Evals
Security

Using Glean for Personal Productivity

This skill drives queries about the user's own work life — their recent activity, what they accomplished, what's pending, what's urgent. It pulls from user_activity, meeting_lookup, search (with from:me / owner:me), and read_memory to assemble a personal view rather than an enterprise-wide one.

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.
  • Priorities / blockers — "what's urgent?", "what needs my attention?", "what's waiting on me?". See 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.

Tool reference lives in glean-core

user_activity, read_memory, search, and meeting_lookup are documented canonically in the using-glean skill (in the glean-core plugin):

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.
  2. Distinguish "did" from "viewed". user_activity returns both. Surface creates / edits / decisions; demote pure views.
  3. Cite sources. Every claim should link back to a doc, meeting, or commit so the user can verify and dig deeper.
  4. Personalize via memory. When framing a summary, read_memory (especially RolesAndResponsibilities and ActiveProjects) tells you what themes the user thinks they work on. Group by those themes when possible.
  5. Apply vetting. Even self-activity should be filtered. See using-glean/reference/vetting.md.

Related commands

  • /glean-productivity:my-week — full weekly summary with analysis
  • /glean-productivity:daily-briefing — what happened in the last 24 hours
Repository
gleanwork/claude-plugins
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.