time-task

Records task start and end timestamps with gut and calibrated estimates in a JSONL log.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill time-task-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: time-task
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/time-task
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill time-task-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Estimates for discrete tasks are rarely checked against actuals, so estimation accuracy never improves. This Skill captures start and end timestamps alongside both a gut estimate and a calibration-factor-adjusted estimate, building a per-task-class dataset that reveals whether estimates and the calibration formula itself are improving over time. ## Core Features & Use Cases - Dual-estimate logging: Records both a gut estimate and a calibrated estimate (gut × class median ratio) for each task, with a minimum of 5 completed class entries required before calibration activates. - Start and end modes: /time-task start generates a UUID and logs the estimate; /time-task end computes actual minutes, gut_ratio, and calibrated_ratio. - Task-class taxonomy: Supports classes like skill-authoring, research, debug, migration, and substitution-edit so calibration factors are computed per class. - Use Case: Before starting a research task you estimate 30 minutes; the skill finds 21 completed research entries with median ratio 0.44, logs a calibrated estimate of 13 minutes, and at completion reports both ratios so you can see which estimate was closer. ## Quick Start Ask the AI to start timing a task by saying "time this task: research the API options, estimate 30 minutes, class research" and later ask it to end the task with the returned task_id.

Frequently Asked Questions about time-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track task time estimates against actuals?

Invoke the start mode with a task description, gut estimate in minutes, and a task class; the skill logs a UUID and timestamp to a JSONL file. When finished, invoke end mode with the task_id to compute actual minutes and the ratio of actual to estimate.

How does estimate calibration work for task timing?

The skill computes a calibration factor as the median gut_ratio of completed tasks in the same class, requiring at least 5 entries. The calibrated estimate equals your gut estimate multiplied by that factor, and it stays null until enough class history exists.

What task classes are supported for time tracking?

Supported classes are skill-authoring, substitution-edit, new-authorship, propagation, research, debug, migration, gate-attestation, and other. Calibration is never applied to the 'other' class because its tasks are too heterogeneous for a trustworthy factor.

Can I use old single-estimate log entries with the new version?

Yes, v01 entries with estimate_minutes and ratio fields are read as gut_estimate_minutes and gut_ratio for backward compatibility. Mixed-version data in the same JSONL log is fully supported when computing class medians.

Why is my calibrated estimate null when I start a task?

A null calibrated estimate means fewer than 5 completed entries exist for that task class, so no calibration factor can be computed. Keep logging tasks in that class; calibration activates automatically once the threshold is reached.