← TimeTackleCONTENT HISTORY
WHAT CHANGED
Update to TimeTackle
Snapshot Oct 24, 2026 · 13:50 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save TimeTackle and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Log time in TimeTackle from a plain description - turn \"I spent 2 hours on the Acme proposal this morning\" into one or more manual time entries with the right tags, confirmed before saving, and fix or remove entries just created. Use when the user wants to log, record, add, correct or delete their time.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 400
}
],
"name": "log-time",
"skill_md_contents": "---\nname: log-time\ndescription: Log time in TimeTackle from a plain description - turn \"I spent 2 hours on the Acme proposal this morning\" into one or more manual time entries with the right tags, confirmed before saving, and fix or remove entries just created. Use when the user wants to log, record, add, correct or delete their time.\n---\n\n# Log time\n\nCreate manual time entries for the connected user from what they describe. Entries always belong to the connected\nuser. Explicit instructions from the user take priority over these steps.\n\n## Input\n\n- What they worked on, when (date and start time), and for how long (or an end time).\n- Optionally tags or property values (for example Project: Acme, or Development).\n\n## Steps\n\n1. Work out each entry: title, `startDateTime` in `YYYY-MM-DD HH:mm:ss`, and either `durationMinutes` or\n `endDateTime`.\n - Resolve relative dates (\"this morning\", \"yesterday at 3\") against today in the user's timezone (theirs if stated,\n otherwise their own calendar's `timezone` from `get_imported_calendars`).\n - If the start time or the duration is missing, ask. Do not guess times.\n2. Resolve tags: call `get_properties` with `search` for each tag or property the user mentioned.\n - Use `\"key\"` for a tag on its own, or `\"key:value\"` for a property value (for example `\"Project:Acme\"`).\n - If a name matches nothing, or several things, ask the user; do not invent tags.\n3. Confirm before saving: list every entry (title, date, start–end, duration, tags) and ask the user to confirm.\n For a single, fully specified entry, a short confirmation is enough.\n4. After confirmation, call `create_manual_entry` once per entry with `title`, `startDateTime`, `durationMinutes` or\n `endDateTime`, and `tagNames`.\n5. Report each created entry with its time and tags, and keep its `eventId` for corrections.\n\n## Corrections\n\n- To change an entry, call `update_manual_entry` with its `eventId` and only the fields that change. `tagNames`\n replaces all of the entry's tags, so pass the full list. Start and end times must be given together.\n- To remove an entry, confirm with the user first, then call `delete_manual_entry` with its `eventId`.\n- Only manual entries can be changed or deleted, not calendar meetings from Google or Outlook.\n\n## Do not\n\n- Do not create entries for someone else; to log time for another person, they connect their own TimeTackle account.\n- Do not create, change or delete anything without the user's confirmation.\n- Do not split, round or merge the user's times unless they ask.\n"
}SHA-256 of public snapshot: 3171918802a3849d529c6870fbbfe67c7d46659b31bf4fbb086eff7d3283408b