What problem does it solve?
Before pushing an offline profile to mobile users, teams have no visibility into how much data devices will download or how often re-syncs will occur, risking data-cap overruns and battery drain. This Skill produces a read-only estimate of per-table row counts, cache size, and daily transfer volume so you can validate the profile first.
Core Features & Use Cases
- Drift Detection: Runs verify-offline-profile.js to flag divergence between the local offline-profile.json and the live Dataverse profile.
- Scope-Aware Row Counts: Applies the same recorddistributioncriteria filters (all records, owned by me/team/business unit, related only) the runtime would use, resolving identity via the Dataverse WhoAmI call.
- Size & Sync Estimates: Computes per-table byte estimates from column-type heuristics and projects daily transfer volume from syncintervalinminutes values.
- Use Case: Before running /assign-offline-profile, preview the profile to discover that a table syncing every 5 minutes would generate 288 syncs per day and exceed mobile data caps, then adjust the interval.
Quick Start
Ask the agent to preview the offline scope of the current offline profile and show estimated download size and daily sync cost per table.