Actually I really did mean to imply that you provide all the ancillary material in conjunction with a main module. It would be nice if the CPAN scripts repository were organised and maintained in the same fashion as the modules repository - that would be the ideal answer. But it's not, and failing that I think that a good solution is to provide your complete project keyed to a primary module.

I don't think it matters that the scripts etc. are not examples. If they are useful to other people then CPAN is a good way to make them available and it is likely that people looking for the stuff you are working with will find it on CPAN by way of a well named module.

Don't separate them further. Tie them all together into a single distribution.