Tempo Time Tracker is a PowerShell-based AI skill for logging and reviewing Jira time entries through the Tempo Timesheets API.
- Logs individual work entries with shorthand ticket aliases
- Logs recurring "standard day" templates from configuration
- Queries and summarizes timesheet data by ticket, day, or account
- Validates local configuration and API connectivity before use
tempo-time-tracker/
|-- README.md
|-- SETUP.md
|-- SKILL.md
`-- scripts/
|-- Get-TempoTimesheet.ps1
|-- Log-StandardDay.ps1
|-- Log-TempoTime.ps1
|-- Validate-Configuration.ps1
|-- standard-day-config.json
`-- ticket-mappings.json
- PowerShell 7.0+
- Tempo API token
- Jira API token and Atlassian email
- Access to the target Jira projects and Tempo accounts
Set these variables before running scripts:
$env:TEMPO_API_TOKEN = "<tempo-token>"
$env:TEMPO_BASE_URL = "https://api.tempo.io/4"
$env:TEMPO_ACCOUNT_ID = "<atlassian-account-id>"
$env:ATLASSIAN_EMAIL = "<you@company.com>"
$env:ATLASSIAN_API_TOKEN = "<jira-api-token>"scripts/ticket-mappings.json: defines work categories, aliases, Jira ticket keys, Tempo account codes, and optional defaults.scripts/standard-day-config.json: defines recurring weekday templates used byLog-StandardDay.ps1.
Run configuration validation before first use:
./scripts/Validate-Configuration.ps1Logs a single entry.
./scripts/Log-TempoTime.ps1 -Ticket "infra" -Duration "6h30m" -Description "Platform maintenance"
./scripts/Log-TempoTime.ps1 -Ticket "standup" -WhatIf
./scripts/Log-TempoTime.ps1 -Ticket "1:1" -Date "2026-03-18"Logs all configured recurring entries for a day.
./scripts/Log-StandardDay.ps1 -WhatIf
./scripts/Log-StandardDay.ps1
./scripts/Log-StandardDay.ps1 -Date "2026-03-18"
./scripts/Log-StandardDay.ps1 -DayOfWeek "Tuesday" -Date "2026-03-20"Retrieves and analyzes existing worklogs.
./scripts/Get-TempoTimesheet.ps1 -Period Today
./scripts/Get-TempoTimesheet.ps1 -Period ThisWeek -ShowRemaining
./scripts/Get-TempoTimesheet.ps1 -From "2026-03-01" -To "2026-03-19" -GroupBy Account- Validate configuration and credentials.
- Query existing worklogs before adding or correcting entries.
- Use
-WhatIffor dry runs. - Log entries (single or standard-day).
- Re-query to confirm totals and avoid duplicates.
- See
SETUP.mdfor detailed onboarding instructions. - See
SKILL.mdfor AI-skill usage rules, correction workflows, and conversation patterns.
Original skill created by John Martin.
- Tempo writes are non-idempotent. Replaying the same payload can create duplicates.
- Use signature checks and post-write verification when doing corrections or bulk logging.