Suggestion: Allow Run to be useful for testing

Most IDEs allow one to run their script/app/etc. I'd like to be able to have a quick way of running various bookmarklets without my fingers leaving the keyboard

I get that there's already the functionality for running a bookmarklet native to chrome (e.g. go click it in your bookmarks bar), but:

• the current method of clicking bookmarks is awful for quick iteration
• the current Run feature is confusing and I don't see how it is very useful, but I'm willing to be told why it is!
• I think it's safe to say most people who using this extension are likely power users and would want an easy run menu so their hands don't have to leave the keyboard rather than trying to finagle some other extension to be running too (these auxiliary extensions just keep adding up)

So, ideas for this? Currently we can bind a shortcut to activate the extension via chrome (aka same as when you click the icon in the pinned extension list up to the right of the omnibox).

So imagine a world where you can:

1. activate extension with shortcut
2. navigate folder hierarchy and items via keyboard arrows
3. on leaves/aka bookmarklet entries, the user could drill down into editing the bookmarklet itself with keyboard actions too, such as a continuation of hierarchy like controls (highlight folder > right arrow to go into that folder (left out) > shift+enter on a highlighted node to run | enter to drill into editor view for that node