Stats
Actions
Tags
From lucen-track
This skill should be used whenever the user wants to log time after the fact in Lucen Track — phrases like "log 2h on X", "I worked 90 minutes on the billing refactor yesterday", "track an hour against PROJ-123", "add a time entry for Monday". Use this skill for backfilling entries; use track-timer for real-time tracking instead.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lucen-track:log-timeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to write a new time entry against a project (and optional phase,
Use this skill to write a new time entry against a project (and optional phase,
todo, and tags). For real-time tracking, use the track-timer skill instead.
Resolve the project + phase.
PROJ-123, feature/login-bug, a Linear or Jira key), call search-todos
with that reference. A match returns the project and phase, so skip the
next step.get-projects and pick the project + phase that matches
the user's description. If multiple plausible matches exist, ask the user
which one to use before writing.Resolve any tags. If the user mentioned a tag (e.g. "tag it as #review",
"billable"), call search-tags to resolve each tag name to a tag id.
Write the entry. Call create-time-entry with the resolved project,
phase, optional todo, optional tag ids, date, duration, and any note the
user provided.
search-todos, get-projects, or search-tags first.get-projects and ask before writing.start-timer from this skill. If the user actually wants a
running timer, ask them to use /track-timer instead./fix-entry.npx claudepluginhub officetimeline/lucen-plugins --plugin lucen-trackGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.