It took me a while to understand that despite having the plugin named as x-foo.py in the plugin repository, it gets loaded as "foo" and must be referenced as such in snapcraft.yaml: % snapcraft snap Loaded local plugin for foo Searching for local plugin for x-foo Issue while loading plugin: unknown plugin: x-foo That seems to remove the point of having the x- prefix, which is to disambiguate local plugins from remote one. The local file name matters little. Doesn't that mean, for example, that if I use a remote part that happens to use a "foo" plugin, it will pick my local x-foo.py file instead of attempting to load a "foo" plugin from snapcraft itself?