Type /time-period-slicer, confirm which periods to include, and the skill builds everything:

1. Scans your model and shows you what was auto-detected — calendar table, date column, fact table, measure table, and visuals on the target page — asks only what it can't derive

2. Creates a period selector table with period names and sort order

3. Creates a bridge calculated table that maps each period to its exact date rows using correct month boundaries

4. Creates a disconnected axis table (monthly, quarterly, weekly, or daily) so the year slicer cannot collapse multi-year periods

5. Adds two relationships: standard bridge-to-period and bridge-to-calendar — no bidirectional filtering, which is what prevents the year slicer from propagating into the bridge

6. Registers all three tables in the model definition

7. Creates visual filter, date boundary, and wrapper measures in the measure table

8. Scans existing slicer styles on the target page and creates a styled period tile slicer

9. Updates target visuals: swaps the category axis to the disconnected axis table, applies a visual-level filter, and replaces base measures with their wrapper variants

10. Optionally writes scoped interaction entries so the slicer only affects the target visuals