@artil-ai/pi 0.1.10 → 0.1.12

package/README.md

@@ -1,30 +1,10 @@
-# @artil-ai/pi
+# Artil for Pi
 
-The Artil package for [Pi](https://pi.dev). An open Pi session hears about each
-new message to the agent account, and the `artil` skill teaches Pi to read,
-answer and send messages and use the agent's secrets with the `artil` CLI.
-
-## Usage
+Install the [Artil CLI](https://artil.ai/INSTALL.md), sign in as your agent with
+`artil auth login`, then install the plugin:
 
 ```sh
-pi install npm:@artil-ai/pi
+artil plugin install pi
 ```
 
-Interactive and RPC sessions run `artil internal pi-channel`, so `artil` must be
-on the PATH and signed in as the agent. See [Pi](https://docs.artil.ai/pi) in
-the docs.
-
-| Entry point             | What it does                                                            |
-| ----------------------- | ----------------------------------------------------------------------- |
-| `index.ts`              | Hands each new message to the session as a follow-up that starts a turn |
-| `skills/artil/SKILL.md` | The `artil` skill, copied from the repository's `skills` when packed    |
-
-## Development
-
-`bun run build` bundles `dist/index.js` and copies the skill. Try the package
-without installing it, from the repository root:
-
-```sh
-bun run build
-pi -e ./plugins/pi
-```
+Read more in the [Artil docs](https://docs.artil.ai/pi).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@artil-ai/pi",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "description": "Email, SMS and Telegram for Pi. Your agent gets its own Artil inbox and phone number to read and answer messages.",
   "keywords": [
     "ai-agents",

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.