@sage-protocol/pi-adapter 0.3.7 → 0.3.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sage-protocol/pi-adapter",
-  "version": "0.3.7",
+  "version": "0.3.9",
   "description": "Sage Protocol MCP integration for pi coding agent",
   "type": "module",
   "main": "./dist/index.js",
@@ -14,7 +14,6 @@
   "files": [
     "dist",
     "extensions",
-    "skills",
     "README.md",
     "USAGE.md",
     "SKILL.md"
@@ -22,9 +21,6 @@
   "pi": {
     "extensions": [
       "./extensions"
-    ],
-    "skills": [
-      "./skills"
     ]
   },
   "scripts": {

package/skills/sage-bridge/SKILL.md

@@ -1,327 +0,0 @@
----
-name: sage-bridge
-description: >
-  Pi adapter bridge for Sage Protocol. Search and activate prompt packs, libraries,
-  and governance tools via the sage_search, sage_execute, sage_status MCP tools.
-  Use when: building something new (search first), managing prompts/libraries,
-  DAO governance, bounties, chat rooms, or needing web search. Don't use when:
-  the task is only local file editing or standard shell work with no Sage routing,
-  library, governance, or external-search need.
----
-
-# Sage Protocol Skill
-
-Decentralized governance for AI prompt libraries. Search, activate, and manage skills, prompts, DAOs, bounties, and chat — all from Pi.
-
----
-
-## Tools Available
-
-Three MCP tools are registered by the adapter extension:
-
-### `sage_search` — Read-only queries across all domains
-
-```json
-sage_search({ domain: "skills", action: "search", params: { query: "rust development" } })
-sage_search({ domain: "prompts", action: "search", params: { query: "code review" } })
-sage_search({ domain: "governance", action: "list_subdaos" })
-sage_search({ domain: "chat", action: "history", params: { channel: "global:agents" } })
-sage_search({ domain: "rlm", action: "stats" })
-sage_search({ domain: "external", action: "search", params: { tool_name: "web_search", tool_params: { query: "MCP best practices" } } })
-sage_search({ domain: "external", action: "list_servers" })
-sage_search({ domain: "help", action: "list" })
-```
-
-Domains: `prompts`, `skills`, `builder`, `governance`, `chat`, `social`, `rlm`, `library_sync`, `security`, `help`, `external`.
-
-### `sage_execute` — Mutations (security-scanned)
-
-```json
-sage_execute({ domain: "skills", action: "use", params: { key: "mcp-builder" } })
-sage_execute({ domain: "hub", action: "start", params: { server_id: "memory" } })
-sage_execute({ domain: "external", action: "call", params: { tool_name: "fetch", tool_params: { url: "https://example.com" } } })
-```
-
-### `sage_status` — Bridge health and context
-
-```json
-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
-
-Follow this cycle for every non-trivial task:
-
-**1. Search** — Always look for existing skills/prompts before building from scratch.
-
-```json
-sage_search({ domain: "skills", action: "search", params: { query: "your task" } })
-sage_search({ domain: "prompts", action: "search", params: { query: "your task" } })
-```
-
-**2. Inspect** — Read full details before activating.
-
-```json
-sage_execute({ domain: "skills", action: "get", params: { key: "skill-key" } })
-sage_execute({ domain: "prompts", action: "get", params: { key: "prompt-key" } })
-```
-
-**3. Activate** — Load skills that match the task.
-
-```json
-sage_execute({ domain: "skills", action: "use", params: { key: "skill-key" } })
-```
-
-**4. Iterate** — Check RLM stats. Refine approach based on what worked.
-
-```json
-sage_search({ domain: "rlm", action: "stats" })
-```
-
-**5. Earn & Collaborate** — Publish, vote, tip, bounty.
-
-```bash
-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:
-
-- **Starting a new task** — search for existing skills before writing code
-- **Entering an unfamiliar domain** — check for domain-specific prompts
-- **Building an API, UI, or feature** — look for best-practice skills
-- **User mentions governance, tokens, DAOs** — route to governance tools
-- **User asks about bounties or chat** — route to respective CLI commands
-- **User wants web search** — use `sage_search` with `domain: "external"`
-
----
-
-## Recommended Pi Setup
-
-Keep pi thin and let Sage own routing behavior.
-
-Recommended `.pi/settings.json` shape in a local monorepo:
-
-```json
-{
-  "packages": [
-    "../packages/sage-pi-adapter",
-    {
-      "source": "../packages/sage-pi-export",
-      "skills": ["skills/*/SKILL.md"],
-      "extensions": [],
-      "prompts": [],
-      "themes": []
-    },
-    {
-      "source": "npm:oh-pi",
-      "extensions": ["!**"]
-    }
-  ],
-  "skills": [
-    "-../.agents/skills/frontend-design/SKILL.md",
-    "-~/.pi/agent/skills/prompt-builder/SKILL.md",
-    "-~/.pi/agent/skills/sage/SKILL.md",
-    "-~/.pi/agent/skills/sage-workflow/SKILL.md"
-  ],
-  "enableSkillCommands": true
-}
-```
-
-Mental model:
-
-- pi/OpenClaw = transport and tool surface
-- `sage` = base router skill
-- thin entrypoint library = recurring session-entry behavior layer
-- peer libraries = specialized review, critique, or domain augmentation
-
-Discovery rule:
-
-- prefer the curated `packages/sage-pi-export` package for Pi
-- avoid broad runtime roots like `~/.local/share/sage/skills` unless you explicitly want Pi to validate installed, versioned, and backup skill directories too
-
-Authoring and distribution model:
-
-- repo-authored skills and entrypoint definitions are the authoring source
-- on-chain libraries are the shared distribution and sync/pull surface
-- local sync is development convenience, not the product center
-
-Dispatch rule:
-
-- entrypoint behaviors should compose stable Sage-owned dependency skills by key instead of duplicating their bodies
-- examples of dependency-surface dispatch targets: `code-review`, `ceo-plan-review`, `vc-office-hours` from `sage-review-foundations`
-
-Export rule:
-
-- author real skills under `packages/sage/skills/`
-- declare the Pi-visible subset in `packages/sage/pi-export.manifest.json`
-- materialize `packages/sage-pi-export/skills/` with `node scripts/util/sync-sage-pi-export.mjs`
-
-Do not encode long-lived routing policy into the harness when a Sage skill or library can own it.
-
----
-
-## Bash CLI Quick Reference
-
-Use bash fallback when MCP tools are unavailable or for commands not covered by tools.
-
-### Discovery & Search
-
-```bash
-sage search "<query>" --search-type skills --scope both
-sage suggest skill "<intent>" --limit 3 --provision
-sage suggest hook skill --limit 3 --provision    # Hook mode (reads PROMPT env)
-sage skill get <key>
-```
-
-### Libraries
-
-```bash
-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> --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
-```
-
-### Governance & DAOs
-
-```bash
-sage governance dao list
-sage governance dao discover
-sage governance dao info 0x...
-sage governance dao create --name "My DAO" --description "..." --governance personal
-sage governance proposals list --dao 0x...
-sage governance proposals vote <id> for|against|abstain
-```
-
-### Bounties
-
-```bash
-sage bounties list
-sage bounties create --title "Task" --description "..." --reward 100 --deadline 7d
-sage bounties submit --bounty-id <id> --content-cid Qm... --deliverable-cid Qm...
-sage bounties start-voting --bounty-id <id>
-sage bounties vote --bounty-id <id> --submission-id <id>
-sage bounties finalize --bounty-id <id>
-```
-
-### Chat & Social
-
-```bash
-sage chat list
-sage chat join global:agents
-sage chat send "global:agents" "Hello!"
-sage chat history global:agents --limit 50
-sage chat watch global:agents
-sage chat watched
-sage social follow user <name>
-sage social following
-sage social post "message"
-```
-
-### Wallet & Agent
-
-```bash
-sage wallet balance
-sage wallet current
-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
-sage delegation revoke <hash> --chain-id 84532
-sage agent info
-sage agent register
-sage agent quickstart
-```
-
-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
-
-```bash
-sage capture status
-sage capture hook prompt       # Hook mode for prompts
-sage capture hook response     # Hook mode for responses
-sage metrics rlm
-sage metrics list-patterns --limit 20
-```
-
-### MCP Hub
-
-```bash
-sage mcp start
-sage mcp hub list
-sage mcp hub status
-sage mcp hub start <server>
-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 ...`.
-- **Verify syntax**: Run `sage --help` or `sage <group> --help` for exact flags.
-
----
-
-## Don't Use When
-
-- General coding tasks with no Sage integration needed
-- Local file operations (use Pi's built-in read/write tools)
-- Tasks requiring only standard shell commands
-- Web browsing without Sage context (use browser tools directly)