When working with plugins the developer find himself doing the same renaming work too many times.
I found a script in eos that actually do the job of automating plugin creation: https://github.com/EOSIO/eos/blob/master/plugins/eosio-make_new_plugin.sh
So i copied over and added some further instructions to get up and running in bitshares after the files are all in place.
The template is a plugin with implementation class, most of our plugins are like that even if there are others that don't follow this pattern i think this is the way most of them can be built.
It haves some minimal functionality on how to add an argument and an onBlock function that will execute every block.
For further examples the developer will check other plugins, unfortunately we have no plugin that exposes api calls in the plugin itself. This is only visible on @xeroc hello plugin:
I think we should encourage the use of the api in the plugin itself rather than adding to
Sample script output: