Update to eHour

{
  "description": "Find or manage eHour clients, projects, tasks, and assignments. Use for project setup, project changes, and assigning people or teams to work in eHour.",
  "included_files": [],
  "name": "projects",
  "skill_md_contents": "---\nname: projects\ndescription: Find or manage eHour clients, projects, tasks, and assignments. Use for project setup, project changes, and assigning people or teams to work in eHour.\n---\n\n# Manage eHour projects\n\nUse the connected eHour MCP tools and their live schemas.\nProject searches do not authorize changes.\nUse returned IDs and disambiguation candidates rather than guessing which record the user means.\nAn assignment ID identifies a user or team assignment; it is not a project ID.\n\n## Find and create work\n\nUse `listClients`, `listProjects`, and `listTasks` for the requested records.\nResults depend on the caller's role and may not cover the whole organization.\nUse `listAssignments` to inspect assignment state; `getAssignments` is limited to the current user.\nUse `runReport` for tracked hours rather than inferring activity from project or assignment settings.\n\n`createProject` requires an existing client and a project name.\n`createTask` requires an existing project.\nResolve the parent before creating the child; a missing parent is not permission to create one.\nUse `createClient` only when the user has requested a new client.\nThe server can generate a code when it is omitted; preserve a code supplied by the user.\n\nFor project budgets, `budgetMinutes` represents minutes and `budgetCents` represents minor currency units.\nDo not pass decimal hours as minutes or whole currency amounts as cents.\nConfirm an ambiguous currency, amount, or enforcement setting before applying it.\nDo not add rates or budgets merely because those fields are available.\n\n## Update and assign\n\n`updateClient`, `updateProject`, `updateTask`, and `updateAssignment` apply only the fields supplied.\nSend the requested changes, without filling other fields with guessed defaults or empty values.\nResolve the target record before changing its name or code.\n\n`assignToProject` and `assignToTask` accept exactly one user or one team.\nResolve the person or team with `listUsers` or `listTeams` when needed.\nKeep assignment dates, rates, and budgets within the user's request.\nAn assignment's `role` is a work label, not a user access role.\nDo not change account permissions to make an assignment succeed.\n\nTeam assignment synchronization can remove or archive existing assignments for former members.\nTask creation can also trigger blueprint assignments and this cleanup.\nExplain this effect when relevant to the requested operation; do not describe these operations as guaranteed to only add data.\n\nUse `unassign` only for an explicit removal request, with the returned assignment ID.\nDepending on tracked time, the server deletes or archives the assignment.\nDo not move or delete time records as an automatic cleanup step.\n\n## Verify the result\n\nReport only the changes confirmed by tool results.\nAfter an uncertain create or assignment response, inspect the current records before retrying to avoid duplicates.\nIf a request has several steps and a later one fails, report the completed steps and the failure.\nDo not undo completed work unless the user requests it.\nRespect scope and role denials; do not use another account or a direct API as a fallback.\n"
}