Weekly Synthesis

Create a comprehensive synthesis of the week's work and thinking

Security Scan

The skill's purpose (make a weekly synthesis) is coherent, but the runtime instructions are vague about where to gather notes and what data sources the agent may access, which could lead to broad/unexpected access to personal data.

Purpose & Capability

The name and description (weekly synthesis of work and thinking) match the instructions (gather notes, identify patterns, synthesize). However, the skill does not declare where those notes live or what integrations/tools it will use, so it is unclear whether additional permissions or credentials would legitimately be required.

Instruction Scope

SKILL.md directs the agent to 'Gather Week's Work' including 'All notes created/modified this week' and 'Projects that saw activity' but provides no source list, file paths, or limits. This open-ended directive grants broad discretion to read whatever 'notes' the agent can access (local files, connected apps, inboxes), which could lead to collection or transmission of sensitive data beyond an expected narrow scope.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk and there is no remote download. This is the lowest-risk install posture.

Credentials

No environment variables, credentials, or config paths are declared (reasonable for an instruction-only synthesis). But the instructions implicitly require access to user notes; the skill should declare required data sources or permissions so users can judge proportionality.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request persistent presence or modify other skills. Autonomous invocation is allowed by default but not specially elevated here.

What to consider before installing

This skill appears to do what it says (generate a weekly synthesis) but is vague about where it will pull 'notes' and 'projects' from. Before installing or enabling it, ask the author which data sources the agent will access (local files, specific apps like Notion/Obsidian/Evernote, email, calendar, etc.). Prefer a version that lists required integrations or asks the user to supply a specific folder/collection or a manual export; deny access to unrelated services. For sensitive work, test the skill on a copy or a small sample dataset first. If you need help, request the SKILL.md be updated to enumerate data sources and required permissions, or only enable the skill when you're ready to grant explicit, limited access.

Create a comprehensive synthesis of the week's work and thinking.

Usage

/weekly-synthesis

Analysis Process

1. Gather Week's Work

   • All notes created this week
   • All notes modified this week
   • Projects that saw activity

2. Identify Patterns

   • Recurring themes
   • Common challenges
   • Breakthrough moments
   • Energy patterns (what energized vs drained)

3. Synthesize Learning

   • Key insights that emerged
   • How thinking evolved
   • Connections discovered
   • Questions answered and raised

4. Assess Progress

   • Projects advanced
   • Areas maintained
   • Resources added
   • Items archived

Output Format

Create a weekly synthesis note:

# Weekly Synthesis - Week of [Date]

## Week at a Glance

- Notes created: [X]
- Projects active: [List]
- Major accomplishments: [List]

## Key Themes

### Theme 1: [Name]

- Where it appeared: [contexts]
- Why it matters: [significance]
- Next actions: [what to do]

### Theme 2: [Name]

- Where it appeared: [contexts]
- Why it matters: [significance]
- Next actions: [what to do]

## Major Insights

1. [Insight with context]
2. [Insight with context]

## Progress by Project

### [Project Name]

- What advanced:
- What's blocked:
- Next week's focus:

## Questions Emerged

- [Question 1 - and why it matters]
- [Question 2 - and why it matters]

## Energy Audit

- What gave energy:
- What drained energy:
- What to adjust:

## Connections Made

- [Note A] <-> [Note B]: [Why significant]
- [Concept X] <-> [Concept Y]: [New understanding]

## Next Week's Intentions

1. [Primary focus]
2. [Secondary focus]
3. [Thing to explore]

## To Process

- Inbox items: [count]
- Orphaned notes: [list]
- Missing connections: [identified]

Follow-up Actions

• Archive completed projects
• Clean up inbox
• Update project status
• Plan next week's focus