📍스킬 설치 방법

첨부파일을 다운로드 받은 후,

ChatGPT → 플러그인 → 상단 스킬 탭 → + 버튼 클릭 → 컴퓨터에서 업로드 → 다운받은 zip 파일을 첨부해주세요!

👇 스킬 내용

# Weekly Work Check

Build a personal report that the user can read in about three minutes and immediately act on. Treat Gmail, Calendar, and Drive as complementary evidence rather than three separate summaries.

## Operating principles

- Use the user's current timezone and state the exact Monday-to-Sunday date range.
- Lead with actions, deadlines, meetings, dependencies, and risks. Do not dump raw messages or event lists.
- Cross-reference repeated project names, participants, dates, links, attachments, and file titles across all three sources.
- Mark unsupported or conflicting conclusions as `확인 필요`.
- Keep connector operations read-only unless the user separately asks for a draft, send, calendar change, or file edit.
- Never expose email addresses, phone numbers, account identifiers, financial details, contract terms, access tokens, or sensitive document contents in the report.
- Prefer project roles such as `캠페인 담당자` over personal names when a name is unnecessary.

## 1. Resolve the reporting window

1. Determine today in the user's timezone.
2. Set the reporting window from Monday 00:00 through the following Monday 00:00.
3. Include near-term obligations just outside the window when work must begin this week. Label them `다음 주 마감`.
4. On Monday morning, emphasize the week ahead. Later in the week, distinguish completed, remaining, and overdue items.

## 2. Inspect Gmail

Search Gmail with a bounded query for the reporting window. Exclude spam, trash, and promotional mail. Inspect at least:

- all work-like messages in the week;
- unread or important inbox messages;
- meeting requests, schedule changes, deadlines, approvals, contracts, deliverables, and attachments;
- conversations where the latest actionable message came from someone else;
- sent messages that create a commitment or promise a delivery date.

Use Gmail-native search first. Read the full thread for shortlisted messages before deciding that a reply or follow-up is due. Do not classify newsletters, receipts, automated notifications, acknowledgements, or already-answered threads as reply obligations unless they contain a concrete action.

For each actionable thread, extract internally:

- project or workstream;
- latest status;
- explicit request;
- owner;
- deadline or promised date;
- whether the user replied after the latest request;
- relevant attachments or Drive links;
- recommended next action.

Treat read state only as a weak signal. Never claim the user ignored a message solely because it is unread.

## 3. Inspect Google Calendar

Search the primary calendar with explicit timezone-aware start and end bounds. Page within the same window if necessary.

For relevant events, inspect full details when attendees, recurrence, notes, attachments, response status, location, or preparation requirements matter. Capture:

- exact date, time, and duration;
- event title and attendee roles;
- recurring status;
- preparation material;
- linked files;
- response status;
- overlaps, back-to-back meetings, missing travel time, or inadequate preparation time.

Do not invent meeting preparation. Infer it only from the event, related mail, linked files, or a clearly associated project deadline.

## 4. Inspect Google Drive

Review files modified, shared, or recently viewed during the week. Search again using project terms found in Gmail and Calendar.

Prioritize:

- meeting notes and agendas;
- proposals, scripts, plans, contracts, reports, and performance sheets;
- files linked from mail or calendar;
- recently updated versions of repeatedly mentioned project documents.

Fetch content only for shortlisted files when it materially changes the next action. If a linked file cannot be accessed, record `접근 권한 확인 필요`; do not guess its contents.

## 5. Correlate and prioritize

Normalize obvious name variants for the same project. Build one internal work item per project or obligation and attach evidence from mail, calendar, and files.

Rank work using this order:

1. overdue or due today;
2. fixed external deadlines and meetings requiring preparation;
3. work blocking another person or approval;
4. next-week deadlines requiring work now;
5. valuable but unscheduled opportunities;
6. informational items.

Use these labels where useful:

- `[준비 필요]`
- `[오늘 마감]`
- `[다음 주 마감]`
- `[확인 필요]`
- `[접근 권한 확인 필요]`

For every priority item, provide the importance, source material, and smallest concrete next action.

## 6. Apply privacy mode

Use one of the following modes.

### Personal mode — default

- Keep enough real project context for the user to act.
- Mask unnecessary names and all direct contact details.
- Summarize sensitive commercial, personal, financial, legal, or account information.
- Do not reproduce source text verbatim unless the user asks for a draft based on it.

### Demo mode

Use when the user mentions a video, demonstration, screen recording, public sharing, presentation, or fictional output.

- Complete the real source analysis first.
- Replace every company, person, project, product, file, and sensitive figure with invented alternatives.
- Generalize or shift nonessential dates, budgets, contract details, and account information.
- Preserve only the shape of the workload: urgency, dependencies, meeting density, and recommended sequence.
- State clearly that all displayed details are fictionalized.
- Never include live links to Gmail, Calendar, or Drive.

## 7. Produce the report

Write in Korean unless the user requests another language. Keep it concise enough to scan in about three minutes.

Use this exact section order:

```markdown
# 이번 주 업무 확인 보고서

기준일: YYYY년 M월 D일 요일
조회 범위: M월 D일 월요일~M월 D일 일요일

## 1. 이번 주 핵심 요약
- 3~5 lines, highest urgency first

## 2. 이번 주 주요 일정
| 날짜 | 시간 | 일정 | 준비 사항·관련 파일 |

## 3. 이번 주 꼭 해야 할 업무 TOP 5
1. 업무명
   - 중요 이유:
   - 참고 자료:
   - 다음 행동:

## 4. 오늘 당장 해야 할 일
### 30분 안에 가능한 일
### 집중 시간이 필요한 일
### 누군가에게 확인해야 하는 일

## 5. 답장 또는 후속 조치가 필요한 메일
| 보낸 사람/역할 | 핵심 요청 | 추천 대응 | 마감 |

## 6. 확인해야 할 문서와 파일
| 파일명 | 관련 업무 | 확인 이유 | 다음 행동 |

## 7. 리스크와 놓치기 쉬운 것
- 리스크와 해결 방법

## 8. 이번 주 추천 업무 순서
| 요일 | 추천 실행 순서 |

**오늘의 실행 순서:** 가장 먼저 실행할 3~4단계
```

Omit empty rows, but keep all eight section headings. If a source has no relevant result, say so briefly and do not fabricate personal-mode work.

## 8. Quality check

Before returning the report, verify:

- the Monday-to-Sunday dates and timezone are correct;
- every asserted deadline has evidence or is marked `확인 필요`;
- sent replies are not listed as unanswered;
- the same project is not duplicated under name variants;
- calendar conflicts and preparation gaps are surfaced;
- linked or recently viewed files are connected to an action;
- the TOP 5 and today's list agree;
- personal data and sensitive details are masked;
- demo mode contains no real identifiers or live source links;
- the report is concise and action-oriented.