More documentation for setting up Continuous Integration

https://skip.tools/docs/faq/#ci

Can Skip frameworks be built and tested using continuous integration systems?
Skip framework projects contain built-in support for running parity tests for both the Swift and Kotlin sides of a project. These tests can be included in automated continuous integration workflows to ensure that the tests are always passing. We do this ourselves for the various Skip frameworks, such as the SkipLib Actions, which references our standard GitHub CI workflow.

The documentation here should at least link to https://github.com/skiptools/actions/ and https://github.com/skiptools/actions/tree/main/.github/workflows

I think I would remove the link to https://github.com/skiptools/skip-lib/actions. That's just a report of Github Action results. (I guess it's just a social proof, "see, wee use it, too" but I don't think the sort of person reading this answer needs that proof.)

It would also be great if skip init were to add example workflows.

Start with the CI section at https://skip.tools/docs/faq/#ci and review the linked skiptools/actions workflows. Update the documentation with the requested workflow links, consider the suggested removal of the skip-lib Actions report link, and inspect the skip init entry point if adding example workflows is included; the relevant links and workflow guidance should be clear when done.