Update to Damoov Telematics

{
  "name": "damoov-mcp-compare-periods",
  "description": "Compares Damoov fleet or driving metrics between two periods and explains the change. Use when a user asks for period-over-period change, trends, increases, decreases, or reasons for a metric difference.",
  "included_files": [],
  "skill_md_contents": "---\nname: damoov-mcp-compare-periods\ndescription: Compares Damoov fleet or driving metrics between two periods and explains the change. Use when a user asks for period-over-period change, trends, increases, decreases, or reasons for a metric difference.\n---\n\n# Damoov period comparison\n\nUse the Damoov Telematics MCP tools.\n\n## Workflow\n\n1. Resolve the company with `list_companies`.\n2. Use `list_metrics` if the metric ID or supported periods are unclear.\n3. Confirm two non-overlapping periods when the user's wording is ambiguous.\n4. Call `compare_periods`.\n5. When the metric supports it and the user asks why it changed, call `explain_change`.\n6. Report:\n   - base-period value;\n   - comparison-period value;\n   - absolute delta;\n   - percentage change when available;\n   - exact period boundaries;\n   - non-causal change components when returned.\n\n## Rules\n\n- Treat delta as comparison value minus base value.\n- Describe `explain_change` output as non-causal components, not proven causes.\n- Never invent missing data or infer unsupported causality.\n- Keep the company and filters identical across both periods unless the user explicitly requests otherwise.\n- Do not expose raw SQL, credentials, tokens, or database schema.\n- Avoid `active_drivers`; it has a known timeout limitation.\n"
}