@sage-protocol/pi-adapter 0.2.1 → 0.3.0

package/skills/sage-bridge/SKILL.md

@@ -50,6 +50,11 @@ sage_status({})
 
 Returns bridge health, wallet connection, network, and session info.
 
+If `sage_status` reports a degraded or unavailable bridge, do not keep retrying
+silently. Tell the user the Sage MCP bridge is unavailable and suggest
+restarting Pi/Sage bridge or verifying `sage mcp start`. Only suggest
+`sage daemon start` when the reported failure is specifically daemon reachability.
+
 ---
 
 ## Behavior Loop
@@ -85,13 +90,40 @@ sage_search({ domain: "rlm", action: "stats" })
 **5. Earn & Collaborate** — Publish, vote, tip, bounty.
 
 ```bash
-sage library push my-library
+sage library push my-library --bump patch
 sage governance proposals vote 1 for
 sage bounties list
 ```
 
 ---
 
+## Choose a Sage distribution surface by intent
+
+Do not collapse every write path into a generic idea of "publish." Choose the smallest surface that matches the actual goal:
+
+- **P2P** — sync trusted machines/agents privately.
+- **Shared library** — collaborate privately with explicit members/invites.
+- **Personal cloud** — host a creator-controlled canonical library; it starts private by default.
+- **Public personal cloud** — make a hosted library publicly discoverable only when the user explicitly asks, with `sage library visibility <library-id> public`.
+- **Marketplace** — sell a polished public personal library as a packaged capability.
+- **DAO promotion** — make a library canonical for a group/community and unlock curation, legitimacy, on-chain reputation, tips, bounties, and community-driven improvement.
+
+**Governance chooser**
+- **personal DAO** — fastest operator-controlled canon
+- **team DAO** — trusted shared stewardship
+- **community DAO** — strongest public curation and legitimacy
+
+Pi routing rules:
+- If the user says **direct share** or **share privately**, think **shared library** first.
+- If the goal is trusted fleet propagation, think **P2P**, not governance.
+- If the goal is creator-controlled hosting, think **personal cloud** and remember it is private by default.
+- If the goal is public web/discovery access, confirm explicit intent before making a library public.
+- If the goal is monetization, think **marketplace**.
+- If the goal is public canon, stronger provenance, future bounties, and repeated community improvement, think **DAO promotion**.
+- If one surface is clearly implied, proactively suggest it instead of waiting for the user to name the exact Sage term.
+- Install/expose is local harness visibility only; do not treat it as publishing.
+- Public feeds/search should only advertise anonymously readable prompts and skills; keep owner-only, unpinned, expired, or otherwise non-openable CIDs out of public discovery until republished or made public.
+
 ## When to Trigger
 
 Proactively search Sage when:
@@ -131,7 +163,7 @@ Recommended `.pi/settings.json` shape in a local monorepo:
     "-../.agents/skills/frontend-design/SKILL.md",
     "-~/.pi/agent/skills/prompt-builder/SKILL.md",
     "-~/.pi/agent/skills/sage/SKILL.md",
-    "-~/.pi/agent/skills/sage-codebase/SKILL.md"
+    "-~/.pi/agent/skills/sage-workflow/SKILL.md"
   ],
   "enableSkillCommands": true
 }
@@ -190,8 +222,9 @@ sage library list
 sage library create <name>
 sage library skill add <path> -l <library>
 sage library prompt add <name> -l <library> --file <path>
-sage library push <library>
+sage library push <library> --bump patch
 sage library promote <library> --dao 0x... --collection default --yes
+# Use `major`, `minor`, or `patch` for `--bump`; exact SemVer and `status --across` are not current CLI commands.
 sage library discover
 sage library sync
 ```
@@ -237,7 +270,9 @@ sage social post "message"
 ```bash
 sage wallet balance
 sage wallet current
-sage wallet connect privy
+sage wallet create sage-wallet
+sage wallet connect ows -n sage-wallet
+sage wallet connect privy --device-code
 sage wallet delegate
 sage delegation create --delegation-profile voter
 sage delegation list
@@ -247,7 +282,9 @@ sage agent register
 sage agent quickstart
 ```
 
-`sage wallet delegate` is ERC20Votes self-delegation for governance voting power. `sage delegation ...` is ERC-7710 scoped agent delegation management.
+Preserve the user's already-working wallet/session preference when one exists. The examples above show common direct-wallet and provider-session paths, not a requirement to force one provider.
+
+`sage wallet delegate` is ERC20Votes self-delegation for governance voting power. `sage delegation ...` is scoped agent delegation management.
 
 ### RLM Capture
 
@@ -274,6 +311,7 @@ sage mcp call <tool> --args '{...}'
 ## Common Pitfalls
 
 - **Hook mode vs query mode**: `sage suggest hook skill` reads the `PROMPT` environment variable or stdin — don't pass the prompt as a positional argument.
+- **Bridge vs daemon wording**: Pi primarily talks to Sage through the MCP bridge. When `sage_status` shows bridge degradation, say "Sage MCP bridge unavailable" and verify `sage mcp start`; don't default to daemon-start advice unless the daemon is the reported failure.
 - **`external/search` requires `tool_name`**: Always include `tool_name` in params when searching via external domain (e.g., `tool_name: "web_search"`).
 - **Domain routing**: Each domain has its own set of actions. Use `sage_search({ domain: "help", action: "list" })` to discover available actions.
 - **Legacy commands removed**: Do not use `sage dao ...`, `sage proposals ...`, or `sage ipfs ...` — these are replaced by `sage governance dao ...`, `sage governance proposals ...`, and `sage config ipfs ...`.