The diagram in the README shows which reads count toward the inclusion or skipping isoform of each event type:
https://github.com/Xinglab/rmats-turbo/tree/v4.3.0?tab=readme-ov-file#outputThe README also describes the different ways for a read to count toward one of the isoforms in the "Event specific columns" section which names the optional columns available when run with --individual-counts
What you wrote for RI events is correct. For A5SS, the diagram shows that the skipping counts come from reads with the splice junction of the shorter exon (short_to_flanking_count). The inclusion counts do not necessarily have the splice junction of the longer exon. An inclusion read could cover the short exon boundary without reaching the other splice junction (across_short_boundary_count) or the read could be contained within the portion of the exon after the short boundary (exclusive_to_long_count)
See also:
https://github.com/Xinglab/rmats2sashimiplot/issues/68#issuecomment-910567403
Eric