separate skills from the plugin

[talhabw]

i think it would make sense to ship the skills separately from the plugin, so users can customize them for their own devices/needs, since apps render differently across different devices, and some app skills might be unnecessary for some users.

same thing for the custom agents (phone-vision)

great work on the plugin! i was using agent-device for controlling my phone until now but this seems cleaner.

[system1970]

Thanks for the kind words and for checking out the project! Really cool to hear you're coming from agent-device.

You make a great point regarding OEM UI variance (OneUI vs Pixel vs MIUI, differing screen sizes) and prompt token overhead when someone only needs the core driver tools.

Here is what I'm planning for the next release to address this cleanly:

1. Configurable Skills via Plugin Options:
   Add support in opencode.jsonc so users can opt-in, opt-out, or select specific skills:

   {
     "plugins": [
       {
         "id": "opencode-mobile-use",
         "options": {
           "skills": false, // or ["spotify", "whatsapp"] to only load specific ones
           "visionAgent": false
         }
       }
     ]
   }

2. User-Skill Precedence:
   Ensure any custom skill defined in ~/.config/opencode/skills/ or workspace .opencode/skills/ with the same name automatically overrides the bundled version.
3. Modular Entrypoint:
   Potentially export an opencode-mobile-use/core entrypoint that registers only the 12 phone_* tools without any bundled skills or subagents.

Would this give you the flexibility you need for your device setups?