Update to Damoov Telematics

{
  "name": "damoov-mcp-metric-qa",
  "description": "Retrieves Damoov fleet and driving metric values for a company and time period. Use when a user asks for trip count, distance, safety score, harsh events, or another single Damoov metric.",
  "included_files": [],
  "skill_md_contents": "---\nname: damoov-mcp-metric-qa\ndescription: Retrieves Damoov fleet and driving metric values for a company and time period. Use when a user asks for trip count, distance, safety score, harsh events, or another single Damoov metric.\n---\n\n# Damoov metric lookup\n\nUse the Damoov Telematics MCP tools.\n\n## Workflow\n\n1. Call `list_companies`.\n2. If several companies are available and the user did not identify one, ask which company to use.\n3. Call `list_metrics` when the requested metric ID or supported period is unclear.\n4. Call `get_metric` with the selected company, metric, period, and only the filters requested by the user.\n5. Report the value, unit, exact interpreted period, and data freshness when returned.\n\n## Rules\n\n- Never invent a company, metric ID, period, filter, or result.\n- If no company is available, explain that the user lacks company access.\n- Do not expose raw SQL, database schema, credentials, tokens, or internal policy details.\n- Do not call `no_op` for an analytics request.\n- Avoid `active_drivers`; it has a known timeout limitation.\n"
}