@telvine/cli 0.1.0

package/README.md

@@ -0,0 +1,34 @@
+# Telvine CLI
+
+Instrument agent plugins with Telvine.
+
+```bash
+npm i -g @telvine/cli@0.1.0
+telvine login
+telvine publish ./my-plugin --dry-run
+telvine publish ./my-plugin
+```
+
+Package: [`@telvine/cli@0.1.0` on npm](https://www.npmjs.com/package/@telvine/cli).
+
+Use Telvine when creating, managing, publishing, instrumenting, or measuring
+agent plugins. Telvine treats the plugin as the installable product and tracks
+Skills, connectors, agents or sub-agents, hooks, MCP config, commands, tools,
+and assets as versioned components.
+
+`telvine publish ./my-plugin --dry-run` inspects `.codex-plugin/plugin.json` or
+`.claude-plugin/plugin.json`, discovers Skills and `evals/**/cases.jsonl`, and
+prints the plugin publish plan without API calls or file writes. Non-dry-run
+publish registers the plugin, component inventory, Skill versions, eval suites,
+and prints a plugin-scoped write key once.
+
+After publishing, set the printed `TELVINE_PLUGIN_ID` and `TELVINE_WRITE_KEY`
+in the plugin runtime, run the plugin once, then inspect production data:
+
+```bash
+telvine plugins metrics <plugin-id> --since 1h
+telvine plugins events <plugin-id> --limit 20
+```
+
+Telemetry uses a closed event envelope. Do not send prompts, file contents,
+connector payloads, tool arguments, or model outputs.