When looking at the net "ispb_aad_in(13)"above, see the explanation below:
Basically, your fastest slice on a particular net is set as a reference line, and thus can be set internally as a 0 ns delay (the line coming in still has its delay of 1.465 ns). There is still an uncertainty that is calculated by our tools (unfortunately, the equation is unavailable), and in this particular net, it was set to .081 ns. Bear in mind that this uncertainty is for the lines in THIS particular net; other nets can have different uncertainty values.
Now, our MAXSKEW will be calculated as the slowest line's delay from the reference, PLUS the uncertainty. In this case, (1.636 - 1.465 = 0.171, 0.171 + 0.081 = 0.252). Since the MAXSKEW constraint was set to 0.23 ns, it failed.
MAXDELAY runs per line in a net, and it is likely to have its uncertainty build into the result, and generally we do not care about that because it is a max value. MAXSKEW on the other hand compares skew differences between the lines, and since we have a reference set to zero, we still need to have some uncertainty on it.