{"id":12228,"plugin_id":"plugin_asdk_app_6a5259b0384881919be9cb3139943abc","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:01:04.590Z","digest":"d175855b800ce2a01269d1a4355d9d56fda5e2a29a7fd9884b462b63f3683b6c","against":null,"payload":{"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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}