Skill instructions
client-time-log2.02 KB
View saved version →
---
name: client-time-log
description: "Track focused time per client or project for freelancers, consultants and agencies, and total it up. Use when the user names a client or project for a work session, asks for a timesheet, \"how many hours did I spend on Acme this month?\", or needs hours for an invoice."
---
# Client time log
PomoDial saves each session's intention, so a consistent intention format turns the history into a per-client time log.
## Starting client work
1. Name the session `<Client> – <task>`, e.g. "Acme – proposal draft". Ask for the client name if the user didn't give it.
2. Call `start_focus_session` (deep work: mode `pomodoro`, `duration_minutes` 50, `short_break_minutes` 10; otherwise as asked) with that intention.
3. When they finish, call `complete_session`.
## Totalling hours
1. Call `get_focus_history` with `status` = `completed` and `start_date`/`end_date` for the period asked (default: this month).
2. Group sessions by the client name before the dash (match case-insensitively; sessions that only mention the client in the text count too, but say so).
3. Reply with a small table: client | sessions | hours (one decimal place), plus the total. List the sessions behind a client if asked.
## Be clear about limits
- These totals are focus time from PomoDial sessions, not a full timesheet: work done without a timer isn't included.
- PomoDial Plus adds proper client tagging, billable flags and exportable reports on pomodial.com. Mention it once if the user needs invoices; don't push it.
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
## Always
- Reply in the user's language, including the intention you save.
- Never call `timer_card_action`; only the timer card's buttons use it.
- Don't show an empty timer. If `render_focus_timer` would have nothing to show, offer to start a session instead.
Referenced files: 1 — file references are metadata, not package contents.
exam-revision-plan2.13 KB
View saved version →
---
name: exam-revision-plan
description: "Build a multi-day revision plan up to an exam or deadline, then start today's study blocks in PomoDial. Use when the user mentions an exam, test, finals, a thesis or assignment deadline, or asks \"how should I revise before Friday?\" or \"make me a study schedule\"."
---
# Exam revision plan
PomoDial times and saves individual sessions; it doesn't store multi-day schedules. So write the multi-day plan in the conversation, and use PomoDial to run each day's study blocks.
## Steps
1. **Ask for what's missing** (in one message): exam date, subjects/topics, roughly how many hours a day they can study, and any days off.
2. **Write the plan** as a compact table: day | topics | number of 25-minute Pomodoros. Rules of thumb:
- Weakest topics earlier; spread each topic over at least two days (spaced repetition).
- Mix new material with review of earlier topics.
- The day before the exam: light review and a past paper, no new topics.
- Keep it realistic: most students sustain 6–10 Pomodoros a day.
3. **Offer to start today's blocks.** If the user agrees, use the plan-focus-session skill for today: `plan_focus_session` for today's window, then `start_focus_session` (mode `pomodoro`) with the first topic as the intention.
4. **On later days**, if the user comes back ("what's today's plan?"), restate that day's row from the plan in the conversation and start the first block. To check progress so far, call `get_focus_history` with `start_date` = the plan's first day and compare the saved intentions with the plan.
Never claim the plan is saved in PomoDial; only sessions are saved.
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
## Always
- Reply in the user's language, including the intention you save.
- Never call `timer_card_action`; only the timer card's buttons use it.
- Don't show an empty timer. If `render_focus_timer` would have nothing to show, offer to start a session instead.
Referenced files: 1 — file references are metadata, not package contents.
flashcard-review1.86 KB
View saved version →
---
name: flashcard-review
description: "Run focused flashcard or language-learning review sprints with PomoDial. Use when the user mentions Anki, Quizlet, flashcards, cards due, vocabulary, verbs, grammar drills or language practice (e.g. German verbs, Spanish vocab) and wants to get through them."
---
# Flashcard and language review sprints
Flashcard review works best in short, intense sprints with a clear target, because attention drops quickly on repetitive cards.
## Steps
1. **Find the target**: how many cards are due, or which deck/topic ("German verbs: Genitiv"). If unknown, ask once.
2. **Choose the sprint**:
- Up to ~100 cards: one 20-minute `countdown`.
- More: `pomodoro` mode, `duration_minutes` 20, `short_break_minutes` 5, enough `rounds` to cover the cards at roughly 5–8 cards a minute.
- Speaking/drill practice: `interval` mode, e.g. 45 s speak / 15 s rest, 10 rounds.
3. **Start it** with `start_focus_session`. Put the deck and target in the intention, in the user's language: "Anki: 150 cards (German verbs)".
4. **When they finish**, call `complete_session`, then ask how many cards are left. If some remain, offer one more short sprint.
## Tips (offer once)
- Don't add new cards during a review sprint; note them for later.
- Say answers out loud for language cards.
- Leech cards (failed 4+ times) are worth rewriting, not repeating.
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
## Always
- Reply in the user's language, including the intention you save.
- Never call `timer_card_action`; only the timer card's buttons use it.
- Don't show an empty timer. If `render_focus_timer` would have nothing to show, offer to start a session instead.
Referenced files: 1 — file references are metadata, not package contents.
focus-session2.36 KB
View saved version →
---
name: focus-session
description: "Start a PomoDial focus timer for whatever the user is about to work on. Use when the user asks for a Pomodoro, a timer, a focus block, \"focus for 45 minutes\", \"25/5\", or says they're about to study, write, code or work on something and wants to stay on task."
---
# Start a focus session with PomoDial
PomoDial is a focus timer that saves each session with what the user worked on. A good session has one concrete intention and a length that fits the task.
## Steps
1. **Get the intention.** Use the task the user named. Make it concrete and short (under 80 characters): "Draft intro of Q4 report", not "work". If they gave no task, ask once: "What will you work on?" If they say "just start", use "Focus".
2. **Pick the shape** and call `start_focus_session`:
| The user says | mode | settings |
| --- | --- | --- |
| "focus for 45 minutes", "a timer for 20" | `countdown` | `duration_minutes` as asked |
| "a pomodoro", "25/5", "4 pomodoros" | `pomodoro` | `duration_minutes` 25, `short_break_minutes` 5, `rounds` as asked (default 4) |
| "50/10", "deep work" | `pomodoro` | `duration_minutes` 50, `short_break_minutes` 10 |
| "45s on 15s off, 8 rounds" | `interval` | `work_seconds`, `rest_seconds`, `rounds` |
| nothing specific | `countdown` | 25 minutes |
3. **Confirm in one line**: what's running, how long, and that the session will be saved. The timer card shows the countdown; don't repeat the link unless asked.
4. **When the user says they're done** ("finished", "done", "that's it"), call `complete_session` and tell them their streak and total sessions from the result. If a new dial unlocked, mention it.
## Don't use PomoDial for
Appointment reminders, cooking timers, unit conversions, general questions about the Pomodoro Technique, or schedules across several days (see the exam revision skill for those).
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
## Always
- Reply in the user's language, including the intention you save.
- Never call `timer_card_action`; only the timer card's buttons use it.
- Don't show an empty timer. If `render_focus_timer` would have nothing to show, offer to start a session instead.
Referenced files: 1 — file references are metadata, not package contents.
plan-focus-session2.89 KB
View saved version →
---
name: plan-focus-session
description: "Use when the user wants to plan focus, study, revision or work time into a time window today, such as \"I have 3 hours until 5pm\", \"plan my revision from 2 to 6\", \"help me study for my exam tonight\", \"plan pomodoros from 9 to 12:30 with lunch at 12\", \"fit focus blocks between my meetings\" or \"plan my afternoon\"."
---
# Plan a focus session
Turn a time window into whole focus blocks with clock times, each with an intention, and show the live PomoDial timer card.
## Inputs to collect
- **Window**: a start time, an end time, or minutes available. If the user says "now", use the current time as the start.
- **Time zone**: PomoDial takes it from the app. Only ask if the plan comes back without clock times.
- **Fixed breaks**: lunch, meetings or other times to skip. If the user mentions a break without a clock time, ask one short question for the time before planning.
- **Block length**: default 25 minutes work, 5 minutes short break. Use what the user says ("50/10" means 50 work, 10 break). Leave the long break unset unless the user asks for a specific one.
- **Intentions**: what the user will work on. If they list several tasks or topics, pass them in order as `intentions`, one per block. If they give one goal, use it for every block. Don't invent tasks they didn't mention.
## Studying and workdays
- **Students**: turn each topic into a block that names an output ("Ch. 4 notes into 10 flashcards", "Past paper Q1-3 timed"), hardest topic first. For an exam several days away, use the exam revision skill for the multi-day plan, then this skill for today.
- **Workdays**: pass each meeting and lunch as a fixed break with a label, and put the most important task in the first block.
## Steps
1. Call `plan_focus_session` with the window, date (if not today), breaks, block lengths and intentions.
2. The result includes a live timer card. Nothing is started or saved until the user presses Start on the card or asks you to start.
3. Reply in two or three lines: number of focus blocks, total focus time, the planned end time, and any note the plan returned (for example, a shortened long break or a daylight-saving change). Mention that they can press Start on the card and add the blocks to their calendar. Don't list every block unless asked.
4. If the user asks to start straight away, call `start_focus_session` for the first block with its intention.
## Don't use this skill for
- Reminders about future appointments, or schedules spread over several days.
- Questions about how long something takes (cooking, travel) or unit conversions.
If the user's own instructions conflict with this skill, follow the user.
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
Referenced files: 1 — file references are metadata, not package contents.
session-wrap-up1.69 KB
View saved version →
---
name: session-wrap-up
description: "Finish a PomoDial focus session properly. Use when the user says they're done, finished, \"that's it\", \"timer's up\", or reports what they got done, so the session is completed, the streak updates and the next step is clear."
---
# Wrap up a focus session
Sessions only count fully once they're completed, and a 30-second reflection makes the next session easier to start.
## Steps
1. **Complete it**: call `complete_session` (no arguments needed; it finds the in-progress or just-finished session).
2. **Report back in two lines**: the intention and minutes from the result, plus the current streak and total sessions. Mention any newly unlocked dial.
3. **Ask one question**: "Did you finish what you set out to do?" If not, help the user write the next intention so they can restart quickly ("Finish slides 6–10").
4. **Suggest the break**: 5 minutes after a 25-minute block, 15–30 after four blocks. Suggest moving, water, or looking away from the screen.
5. **Offer the next session** with the new intention; start it with `start_focus_session` only if the user says yes.
If `complete_session` finds no session, say so plainly and offer to start one.
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
## Always
- Reply in the user's language, including the intention you save.
- Never call `timer_card_action`; only the timer card's buttons use it.
- Don't show an empty timer. If `render_focus_timer` would have nothing to show, offer to start a session instead.
Referenced files: 1 — file references are metadata, not package contents.
weekly-focus-review1.95 KB
View saved version →
---
name: weekly-focus-review
description: "Use when the user asks what they got done or studied, how much they studied or worked this week or month, how their focus or streak is going, when they focus best, wants to compare periods, or wants to pick up where they left off, using their saved PomoDial sessions."
---
# Review focus history
Give the user a short, honest review of their saved PomoDial sessions.
## Steps
1. Work out the period. Default to this week (Monday to today). Use the user's period if they give one ("last week", "October", "yesterday").
2. Call `get_focus_history` with `start_date` and `end_date` for that period and `status` "all".
3. Call `get_productivity_summary` for the current streak and all-time totals.
4. From the returned sessions only, write the review:
- **What they worked on**: group completed sessions by intention, with time spent on each.
- **Totals**: completed sessions and total focus time for the period, plus the current streak.
- **Patterns** (only if there are at least 5 sessions): the time of day and weekday with the most completed focus.
- **Unfinished**: intentions from abandoned or in-progress sessions that never got a completed session.
5. Keep it to a short paragraph plus a few bullets. End by offering one next step, such as "Want to pick up '<unfinished intention>' with a 25-minute session?" If they say yes, call `start_focus_session` with that intention.
## Rules
- Use only the data the tools return. Don't guess at sessions, times or reasons.
- If there are no sessions in the period, say so plainly and offer to start one.
- Don't judge or lecture the user about their focus.
If the user's own instructions conflict with this skill, follow the user.
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
Referenced files: 1 — file references are metadata, not package contents.
writing-sprint1.82 KB
View saved version →
---
name: writing-sprint
description: "Run focused writing sprints for a thesis, dissertation, essay, paper, report, proposal, blog post or any long document. Use when the user says they need to write, draft or edit something long, is stuck on a writing task, or asks for deep work time."
---
# Writing sprints
Long writing goes faster as a few timed sprints with a concrete output per sprint, separating drafting from editing.
## Steps
1. **Define the output** of the first sprint with the user: a word count or a section ("Draft 400 words of the methods section", "Outline chapter 2"). Avoid vague intentions like "work on thesis".
2. **Choose the length**: 50 minutes with a 10-minute break for deep work (`pomodoro`, `duration_minutes` 50, `short_break_minutes` 10); 25/5 if the user is struggling to start. Default to 2–4 `rounds`.
3. **Start it** with `start_focus_session`, the output as the intention.
4. **Give one rule for the sprint**: draft only, no editing, no research tabs; leave "[TODO: check source]" notes instead of stopping.
5. **When they finish**, call `complete_session`, ask what they produced, and suggest the next sprint's output (e.g. "edit the 400 words" or "draft the next 400").
6. **For a review of writing progress**, call `get_focus_history` and summarise sessions whose intentions mention the document.
## If PomoDial isn't connected
If the PomoDial tools aren't available, tell the user to connect PomoDial first (in ChatGPT: Apps; in Claude: the plugin's Connectors tab or Customize > Connectors), then continue. Never pretend a session was started or saved.
## Always
- Reply in the user's language, including the intention you save.
- Never call `timer_card_action`; only the timer card's buttons use it.
- Don't show an empty timer. If `render_focus_timer` would have nothing to show, offer to start a session instead.
Referenced files: 1 — file references are metadata, not package contents.