I like the concept behind this but I think the implementation is flawed as it binds the actions to specific providers. For example - repo.new only creates repos on GitHub, playlist.new only creates playlists on Spotify and the music.new thing for OVO Sound is just odd, being specific to a custom cover art generator thing.
For me, the better implementation would be where for each "action" there are numerous providers and at a user level you could define which one you want to use. So user A goes to repo.new and gets redirected to GitHub, user B goes to GitLab, user C to Bitbucket and so on. The first time you go to the action you're prompted to select which service you want to use by default and from then on you go straight through.
Yeah I get that, but rather than Google opening it up for open registration and having the usual domain land grab, they could have created domains for each action and allow service providers to register intents in their services for each action. It's going to make discovery of actions much harder if there are different actions for different providers. It will also mean the usefulness of the pattern will be limited based on the services I choose to use.
In your example - if I prefer Domino's to Pizza Hut, what do I go to? I need to go to pizza.new to discover that it's linked to Pizza Hut and then try to figure out what Domino's action might be. In the end I'll just end up going to the main site instead. I think the value of this concept is completely nullified by binding the actions/domains to specific providers.
For me, the better implementation would be where for each "action" there are numerous providers and at a user level you could define which one you want to use. So user A goes to repo.new and gets redirected to GitHub, user B goes to GitLab, user C to Bitbucket and so on. The first time you go to the action you're prompted to select which service you want to use by default and from then on you go straight through.