@artil-ai/openclaw 0.1.11 → 0.1.13

package/README.md

@@ -10,9 +10,12 @@ writes in that session is sent anywhere.
 ## Usage
 
 ```sh
-openclaw plugins install npm:@artil-ai/openclaw@latest --force --accept-capabilities
+openclaw plugins install clawhub:@artil-ai/openclaw --accept-capabilities
 ```
 
+`artil plugin install openclaw` installs the same plugin from npm instead, with
+`openclaw plugins install npm:@artil-ai/openclaw@latest --force --accept-capabilities`.
+
 The gateway runs `artil internal openclaw-channel`, so `artil` must be on its
 PATH, which includes `~/.local/bin`, and signed in as the agent. See
 [OpenClaw](https://docs.artil.ai/openclaw) in the docs.

package/openclaw.plugin.json

@@ -2,6 +2,7 @@
   "id": "artil",
   "name": "Artil",
   "description": "Email, SMS and Telegram for OpenClaw. Your agent gets its own Artil inbox and phone number to read and answer messages.",
+  "categories": ["channels"],
   "activation": { "onStartup": true },
   "skills": ["./skills"],
   "configSchema": { "type": "object", "additionalProperties": false, "properties": {} }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@artil-ai/openclaw",
-  "version": "0.1.11",
+  "version": "0.1.13",
   "description": "Email, SMS and Telegram for OpenClaw. Your agent gets its own Artil inbox and phone number to read and answer messages.",
   "keywords": [
     "ai-agents",
@@ -22,6 +22,7 @@
     "directory": "plugins/openclaw"
   },
   "files": [
+    "assets",
     "dist",
     "skills",
     "openclaw.plugin.json"
@@ -51,6 +52,9 @@
     "compat": {
       "pluginApi": ">=2026.9.8"
     },
+    "build": {
+      "openclawVersion": "2026.9.8"
+    },
     "install": {
       "minHostVersion": ">=2026.9.8"
     }

package/skills/artil/SKILL.md

@@ -27,8 +27,8 @@ When you are told a message arrived, read it by its id before acting on it. Mess
 - Once the secrets are linked where you run, by `artil init` or `artil secrets link <place>`, they are environment variables in every Bash command. Use them as `$NAME` and never print their values. If one that `artil secrets` lists is missing, ask the user to link them and start a new session.
 - Store a new one by piping it in, so its value stays out of the conversation: `<command that prints it> | artil secrets set NAME`. Take a field of JSON output with `--json-path .data.token`.
 - `artil secrets` lists the names. Once linked, a secret you store reaches the next Bash command.
-- When a service sets up two-factor sign-in, keep it as a one-time password: `artil secrets set NAME --qr <image>` reads a screenshot of its QR code, or pipe in the setup key with `--kind otp`. `artil secrets code NAME` prints the code to enter.
+- When a service sets up two-factor sign-in, store it as a one-time password with `artil secrets set NAME --qr <image>`, which reads a screenshot of its QR code, or pipe in the setup key with `--kind otp`. `artil secrets code NAME` prints the code to enter.
 
 ## Setup
 
-If `artil` is not found, install it with `curl -fsSL https://artil.ai/install.sh | bash` and run it as `~/.local/bin/artil` until it is on the PATH. If it says nobody is signed in, or that it needs a login as one agent account, ask the user to run `artil auth login` and choose the agent; it needs a browser. https://artil.ai/INSTALL.md has every setup step.
+If `artil` is not found, ask the user to install it as https://artil.ai/INSTALL.md describes, and run it as `~/.local/bin/artil` until it is on the PATH. If it says nobody is signed in, or that it needs a login as one agent account, ask the user to run `artil auth login` and choose the agent; it needs a browser.