As far as I know there is no official library template available for Robot Framework libraries.
For custom keyword python libraries it seems like the current recommendation is to use poetry for dependency management and packaging.
From a long time project maintenance perspective and ease of onboarding it could be beneficial to provide some template(s). This allows scaffolding libraries easily and consistently with common community best practices. In addition code lifecycle management could ease updating older libraries.
Options for code scaffolding and code lifecycle management are:
Absolutely. I just want to make sure that it’s in alignment with the RF core team and that the template(s) can me maintained as part of the Robot Framework · GitHub organization later on to ensure long time maintenance,
I‘ll open source a RF library robotframework-github I’ve worked on recently the next days to weeks. The project uses common modern tools for development (uv, marimo) and could be a good inspiration.
Project issues makes it easier to communicate features and coordinate development. Feel free to create new issues (features) and reference those in PRs (feature implementation).