In reply to rahulkumarbudhwani:
>> If yes, wouldn't it be very unusual rather than directly setting setup and holdtime for the input/output skew in clocking block?
Timing is closed at the i/p flop considering not just setup and hold time alone, but clk-q, combo at o/p, combo at i/p + any path delays + setup.
given this, there is a budget allocated for each design, on how much would it consume. let's say a design is going to consume 30% at an i/p flop(combo+setup), rest 70% is coded as o/p skew in clocking block to validate, design indeed takes only 30%