teamclaws 1.0.3 → 1.0.4

package/dist/constants.js

@@ -1,5 +1,5 @@
 export const PACKAGE_NAME = "teamclaws";
-export const PACKAGE_VERSION = "1.0.3";
+export const PACKAGE_VERSION = "1.0.4";
 export const CLIENT_NAME = "teamclaws-cli";
 export const CONTRACT_VERSION = 1;
 export const OUTPUT_SCHEMA_VERSION = 1;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "teamclaws",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "description": "Official TeamClaws command-line client and agent skills",
   "license": "PolyForm-Shield-1.0.0",
   "homepage": "https://teamclaws.com",

package/skills/teamclaws-onboard/SKILL.md

@@ -33,8 +33,10 @@ failures; report the actual result without claiming success.
 ## Choose workspaces
 
 Run `teamclaws servers list --json`. Use only a successful `servers_list` event;
-errors are not empty inventories. Display aliases, retaining `server_id` for
-commands. Explain readiness separately from ownership.
+errors are not empty inventories. Show each server's display name (`alias`) and
+returned `description` to the user, retaining `server_id` for commands. If a
+description is empty or absent, say "No description set." Explain readiness
+separately from ownership.
 
 If discovery emits `server_metadata_prompt`, show its question and explain that
 the owner can always change the server's name and description later. Ask for the
@@ -55,10 +57,11 @@ deliver it when received. Never offer this edit for a shared server whose
   list does not prove an empty account. Ask the user to check their workspaces at
   https://teamclaws.com/app/; only if they confirm they have none, direct them to
   purchase there. Do not claim inventory support is deployed from local code alone.
-- With one pairing-ready workspace, name its alias and ask, “Would you like to
-  pair with **[alias]** now?” Never automatically pair it.
-- With several, list aliases and ask, “Would you like to pair with any of these
-  now?” If aliases repeat, distinguish them using their workspace addresses.
+- With one pairing-ready workspace, show its alias and description and ask,
+  “Would you like to pair with **[alias]** now?” Never automatically pair it.
+- With several, list each alias and description and ask, “Would you like to pair
+  with any of these now?” If aliases repeat, distinguish them using their
+  workspace addresses.
 
 For each selected workspace, follow [teamclaws-pair](../teamclaws-pair/SKILL.md)
 with its stable identifier. A prior explicit selection already authorizes that

package/skills/teamclaws-pair/SKILL.md

@@ -55,9 +55,11 @@ Use `--no-open` only when automatic browser opening is undesirable. The
 `pairing_browser_required` event still provides the safe approval address.
 
 When no selected stable identifier is known, run `teamclaws servers list --json`,
-show aliases and readiness, and ask which workspace the user wants to pair—even
-when only one is available. Pass the selected `server_id`; aliases are display
-labels, not unique command targets. Targetless `teamclaws pair --json` returns
+show each server's display name (`alias`), returned `description`, and readiness,
+and ask which workspace the user wants to pair—even when only one is available.
+If a description is empty or absent, say "No description set." Pass the selected
+`server_id`; aliases are display labels, not unique command targets.
+Targetless `teamclaws pair --json` returns
 `server_selection_required` for any nonempty pairing-ready list and never
 creates approval automatically. Interactive targetless pairing also requires a
 selection. An empty or not-ready list is not proof that the account owns no