From these slides, one of the use-cases is:

Also support patterns such as “every engineer has their own dev DB on localhost”

Which is also a goal for us. However, it's quite difficult to work with an empty database!

Could Skeema be used to "seed" the database with some base set of data so that it doesn't start empty? Or do you think this should be delegated to another tool?

What about for the scenario where a developer adds a new feature, and creates a table for it. When it's deployed into production, it shouldn't start empty there either. For example, a list of options used in a drop-down.