@sbillinge Thanks for the suggestion. The point of a centralized workflow is to offer a reusable, consistent process—but our C++ library’s build and release steps are quite different from our Python packages, and we don’t yet have a skpkg standard for C++ modules. Folding this into the central repo today would either clutter it with C++-specific logic or introduce extra layers here, without real benefit.
Since we expect this library to be heavily modified and updated, with any possible future skpkg C++ standard to evolve rapidly, a temporary dedicated workflow in this repo is simpler and more maintainable for now. Once we’ve defined a skpkg C++ standard, we can migrate it back upstream.

sounds good. I agree.