skills/timecamp-org/skills/fill-timesheet

fill-timesheet

SKILL.md

Fill Timesheet

Help the user complete their daily timesheet by matching computer activities to tasks and generating time entry suggestions.

Steps

  1. Get existing time entries for the target date
  2. Get time entry suggestions (if available from the system)
  3. Get computer activities for the target date
  4. Get available tasks — prioritize recently used, favorites, and project-assigned tasks
  5. If user uses a todo app (e.g., Obsidian, Todoist), get completed tasks for the target date
  6. Get time entry notes from previous days to learn the user's writing style
  7. Match computer activities to tasks:
    • Group related activities into logical work blocks
    • Assign the most likely task to each block
    • Apply any learned matching rules (see below)
  8. Generate draft time entries:
    • Fill gaps between activities with likely tasks
    • Merge overlapping or duplicate entries
    • Write notes matching the user's existing style and tone
    • Round times to reasonable intervals (e.g., 15 min)
  9. Present a summary to the user:
    • List of proposed entries (task, time range, duration, notes)
    • Total hours for the day
    • Highlight any gaps or uncertainties
  10. Ask user for confirmation or corrections
  11. If user requests changes, update matching rules below for future use

Good Timesheet Rules

  • A normal working day should total approximately 7–8 hours
  • Total time entries should be roughly 110% of tracked computer activity time (to account for meetings, phone calls, and other non-computer work)
  • Each entry should have a note that matches the tone and format of the user's previous time entry notes
  • Typically 1–5 unique tasks per day — if significantly more, consider consolidating
  • Avoid entries shorter than 15 minutes unless the user explicitly prefers them
  • Prefer continuous blocks over fragmented entries

These rules are defaults. Modify them if the user has different expectations.

Edge Cases

  • No computer activities found: Ask the user what they worked on, or check if they had a day off / were on leave
  • Very few activities (< 1 hour): Ask if it was a short day, meeting-heavy day, or if tracking was off
  • Activities exceed 10 hours: Flag potential overnight tracking or forgotten logout
  • No matching tasks found: Ask the user to assign the task manually, then save the mapping as a matching rule

Matching Rules

Rules learned from user corrections. Add new rules when the user fixes a suggestion.

Weekly Installs
3
First Seen
Feb 25, 2026
Installed on
opencode3
github-copilot3
codex3
kimi-cli3
gemini-cli3
amp3