In reply to kernalmode1:
Default skew sampling in the postponed region of previous timestep translates to the previous clock cycle, is this correct?
Correct.
With #0 skew, if the clock even trigger corresponds to the rising edge of a clock, does this sample updated data or data before the update?
This can be a race condition, depending on how the data is assigned. I would never use this.