Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
plugin-native-system - Skill - OpenSmartRoute
Skillv1.0.0
plugin-native-system
A Capacitor plugin that bridges Android system-role status and device-settings control into the elizaOS mobile runtime.
Imported from elizaOS/eliza (plugins/plugin-native-system/AGENTS.md). Install upstream with npx skills add elizaOS/eliza --skill plugin-native-system. Copyright stays with the author.
@elizaos/capacitor-system
A Capacitor plugin that bridges Android system-role status and device-settings control into the elizaOS mobile runtime.
Keep the ElizaSystem registration name identical in TypeScript and Kotlin. Protected operations require host-declared and user-granted Android permissions.
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install plugin-native-system and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
elizaos-eliza-plugin-native-system.ocm.jsonjson
{
"ocm": "1",
"id": "elizaos-eliza-plugin-native-system",
"kind": "skill",
"name": "plugin-native-system",
"description": "A Capacitor plugin that bridges Android system-role status and device-settings control into the elizaOS mobile runtime.",
"publisher": "elizaOS",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"A Capacitor plugin that bridges Android system-role status and device-settings control into the elizaOS mobile runtime."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/elizaOS/eliza",
"path": "plugins/plugin-native-system/AGENTS.md",
"ref": "07852e51fe8e1a2e0eae6e9e17f2bb925985910f",
"url": "https://github.com/elizaOS/eliza/blob/07852e51fe8e1a2e0eae6e9e17f2bb925985910f/plugins/plugin-native-system/AGENTS.md",
"key": "elizaOS/eliza/plugins/plugin-native-system/AGENTS.md"
}
},
"instructions": "# @elizaos/capacitor-system\n\nA Capacitor plugin that bridges Android system-role status and device-settings control into the elizaOS mobile runtime.\n\nKeep the `ElizaSystem` registration name identical in TypeScript and Kotlin. Protected operations require host-declared and user-granted Android permissions.\n\nBuild, test, and setup: [README.md](README.md).",
"cost": {
"context_tokens": 89
}
}
Fetch it by URL: GET /api/v1/registry/elizaos-eliza-plugin-native-system/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
