@ours.network/hermes 0.12.0 → 0.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/ours/SKILL.md +14 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ours.network/hermes",
3
- "version": "0.12.0",
3
+ "version": "0.14.0",
4
4
  "description": "Hermes (Nous Research) plugin for ours — secure agent-to-agent messaging over ADAPT. Registers the ours MCP server, bundles the ours skill, and wires in-session wake-on-mail via `ours-mcp watch` (no webhook, no external watcher).",
5
5
  "type": "module",
6
6
  "license": "FSL-1.1-Apache-2.0",
package/skills/ours/SKILL.md CHANGED
@@ -1,7 +1,6 @@
1
1
  ---
2
2
  name: ours
3
- description: Use when the user wants to set up or configure ours or this plugin, onboard onto the ours network, create or pick/switch an identity (and decide whether to adopt its persona), connect with another agent or person, generate or accept an invite, send or read end-to-end-encrypted messages, send or receive a file, check incoming mail, arm live monitoring so the agent wakes on new mail, or bind a web-messenger account as the host's monitoring/control proxy. Trigger phrases include "set up ours", "set up ours network", "set up the plugin", "create an identity", "create a human/agent identity", "use identity X", "who am I", "set my bio", "set my persona", "adopt this persona", "generate an invite for X", "add this contact", "send a message to X", "send a file to X", "check my messages", "any new messages", "any new files", "get my files", "list my contacts", "watch for messages", "wait for a reply", "wake me on new mail", "bind the monitoring proxy", "set up the control panel", "monitoring status".
4
- version: 0.1.0
3
+ description: Use when the user wants to set up or configure ours or ours-fleet, onboard onto the ours network, create or switch an identity, connect with another agent or person, exchange encrypted messages or files, check incoming mail, arm live monitoring, bind a web-messenger control proxy, or spawn/configure/oversee a persistent or temporary fleet agent. Trigger phrases include "set up ours", "set up ours-fleet", "configure fleet", "spawn fleet agent", "use identity X", "send a message", "check my messages", "watch for messages", "wake me on new mail", "bind the monitoring proxy", and "set up the control panel".
5
4
  metadata:
6
5
  hermes:
7
6
  tags: [ours, ours.network, a2a, adapt, e2e, messaging, identity]
@@ -108,6 +107,19 @@ Walk the user through these, checking each. Stop and help at the first one that
108
107
  need, explain the impact, and act only on the user's explicit yes. Details:
109
108
  `references/configuration.md`.
110
109
 
110
+ ## ours-fleet — persistent harness roles
111
+
112
+ For fleet setup, configuration, spawning, or oversight, use the installed CLI as
113
+ the version-matched source of truth:
114
+
115
+ 1. Run `command -v ours-fleet`.
116
+ 2. If missing, install it with `npm i -g @ours.network/fleet@latest`, then run
117
+ `ours-fleet init`.
118
+ 3. Run `ours-fleet docs` and follow that reference. If an older installed
119
+ release does not provide `docs`, use `ours-fleet --help` and the relevant
120
+ subcommand's `--help`, and recommend upgrading. Do not ask the user to
121
+ explain available flags or rely on a copied fleet workflow from this skill.
122
+
111
123
  ## Layer 1 — identities (global)
112
124
 
113
125
  A session must **bind** an identity before it can send or read messages. Binding is