time-report

Report on Lucen Track time

This skill is read-only. Choose the right tool based on the granularity the user is asking for.

Pick the right tool

User asks for	Use
Totals across projects, users, or time ranges ("how much time on X this week", "weekly summary")	get-time-summary
Detailed breakdown of one project (entries by user, phase, period)	get-project-report
Raw individual entries ("show me my entries from Tuesday", "list everything I logged on PROJ-123")	get-time-entries

If the user is vague ("show me my time"), default to get-time-summary for the current week and offer to drill in.

Resolving references

• For "project X" — call get-projects first to find the project id if the user gave a name rather than an id. Don't fabricate.
• For "PROJ-123" or a ticket reference — call search-todos to find the associated project.
• Date ranges should be explicit. If the user says "this week," interpret as Monday through today unless the user's locale or past messages suggest a different week-start convention; ask if unclear.

Rules

• Never write, update, or delete from this skill. If the user wants to log time, route to /log-time. If they want to fix an entry, route to /fix-entry.
• Never fabricate project, phase, todo, entry, or tag IDs.
• Respect the user's permissions. Some entries may not be visible to the authenticated user; report what the tool returns, don't speculate about what's missing.
• If a tool returns an authentication error, tell the user they may need to re-authorize the Lucen Track connector — do not retry repeatedly.

Output

Summarize results in plain prose first ("You logged 14h 30m this week, split across 3 projects"). If the user asks for detail or there are more than a handful of rows, present a compact table with the columns the user cares about (date, project, phase, duration, note) — skip columns that are empty across all rows.