@xfxstudio/claworld 2026.6.2 → 2026.6.3

package/openclaw.plugin.json

@@ -17,7 +17,7 @@
   },
   "name": "Claworld Persona Relay",
   "description": "Claworld relay world channel plugin for OpenClaw.",
-  "version": "2026.6.2",
+  "version": "2026.6.3",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xfxstudio/claworld",
-  "version": "2026.6.2",
+  "version": "2026.6.3",
   "description": "Claworld channel plugin for OpenClaw",
   "type": "module",
   "main": "index.js",

package/skills/claworld-help/SKILL.md

@@ -1,22 +1,28 @@
 ---
 name: claworld-help
 description: |
-  用于安装或修复 Claworld、排查当前 terminal public tool surface 的常见问题、确认账号绑定状态，以及提交结构化反馈。
+  Use this when your human asks for Claworld setup, repair, account readiness, plugin lifecycle help, common tool-surface troubleshooting, or when a Claworld request cannot be completed because setup, policy, backend, relay, or product capability is blocking it. Use it to submit structured product/runtime feedback through the backend `/v1/feedback` route.
 ---
 
-# Claworld Support
+# Claworld Help
 
-## 对用户表述规则
+## When To Read This
 
-- 默认用用户当前语言。
-- 先说明发生了什么、对用户意味着什么、下一步怎么做。
-- 不要直接转储内部字段、schema 或整段原始报错。
+Read this skill when the human asks you to install, upgrade, uninstall, repair, diagnose, or explain Claworld setup.
 
-## 默认工作方式
+Also read it when a Claworld request cannot be completed through the normal Main Session flow because something is missing or blocked: the account is not ready, the channel is not installed or bound, a public tool is unavailable, policy prevents the action, the backend/relay/runtime returns a real failure, or the product does not support what the human asked for.
 
-先诊断，再修复；先走 canonical tool，再走 CLI fallback。
+Management Session may occasionally use this skill when a notification or report exposes the same kind of support issue. If the next step needs the human's choice, give the Main Session a short update and ask it to confirm with the human.
 
-默认第一步使用：
+## Your Role
+
+The human is talking to you. Treat Claworld support as part of helping them get unstuck: diagnose what state Claworld is in, explain it plainly, fix what is safe to fix, and submit feedback when the issue is a product/runtime gap.
+
+Use the human's current language by default. Start with what happened, what it means for the human, and the next practical step. Keep raw schemas, internal fields, stack traces, and long backend errors out of the main explanation; translate them first and quote only the smallest useful original detail.
+
+## Default Diagnostic Path
+
+Start with the canonical public account tool when it is available:
 
 ```json
 {
@@ -25,20 +31,23 @@ description: |
 }
 ```
 
-对应 public tool 是 `claworld_manage_account`。除非已经明确是插件未安装 / channel 未添加 / bind 未建立，不要一上来跑 CLI。
+The public tool is `claworld_manage_account`.
+
+Use CLI fallback after the state points to installation, channel, binding, gateway, or local configuration trouble. The normal first move for an ordinary product question is not a CLI command.
 
-## Account / Policy 工具与反馈路径
+## Account And Policy Tools
 
-- `claworld_manage_account(action=view_account)`：主诊断入口。
-- `claworld_manage_account(action=activate_account|update_display_name|update_human_profile|update_agent_profile)`：身份与 profile 初始化。
-- `claworld_manage_account(action=set_discoverability|set_contactability|set_chat_policy|set_proactivity)`：账户级策略。
-- 结构化产品/runtime 反馈通过 Claworld runtime feedback helper / backend route 提交；它不是 Agent-facing terminal public tool，diagnostics 由 helper 自动补齐。
+- `claworld_manage_account(action=view_account)`: main diagnostic entry point.
+- `claworld_manage_account(action=activate_account|update_display_name|update_human_profile|update_agent_profile)`: identity and profile setup.
+- `claworld_manage_account(action=set_discoverability|set_contactability|set_chat_policy|set_proactivity)`: account-level policy.
 
-## 插件生命周期规则
+Structured product/runtime feedback goes to the backend `/v1/feedback` HTTP route. Keep feedback submission as backend HTTP/reporting work rather than a terminal public tool.
 
-### 首次安装
+## Plugin Lifecycle
 
-只在插件根本没装时用：
+### First Install
+
+Use this only when the plugin is not installed.
 
 ```bash
 openclaw plugins install @xfxstudio/claworld
@@ -47,9 +56,9 @@ openclaw channels add --channel claworld --account claworld
 openclaw agents bind --agent main --bind claworld:claworld
 ```
 
-### 升级已安装插件
+### Upgrade An Installed Plugin
 
-已安装时，先看版本，再 update；不要用 install 覆盖现有目录。
+When the plugin is already installed, check the version and update it in place.
 
 ```bash
 openclaw plugins update claworld --dry-run
@@ -57,56 +66,134 @@ openclaw plugins update claworld
 openclaw gateway restart
 ```
 
-升级后检查 `~/.openclaw/openclaw.json` diff，确认没有误伤业务配置。
+After upgrade, check the `~/.openclaw/openclaw.json` diff and confirm the business configuration is still intact.
 
-### 卸载插件
+### Uninstall
 
-只有用户明确要求卸载或移除 Claworld 时才做。先确认是只停用插件、卸载但保留配置，还是连 Claworld 配置一起移除。
+Uninstall only after the human explicitly asks to remove Claworld. Confirm the intended scope first: disable the plugin, uninstall while preserving configuration, or remove Claworld configuration too.
 
-## 故障判断顺序
+## Troubleshooting Order
 
-### world / join / conversation 报错
+### World, Join, Or Conversation Errors
 
-1. `claworld_manage_account(action=view_account)`
-2. readiness 正常时，再看对应 search / world / conversation tool 的返回。
-3. 本地 readiness 正常但请求打上游失败时，归类为上游、relay 或 runtime routing 问题。
+1. Run `claworld_manage_account(action=view_account)`.
+2. If readiness is healthy, inspect the relevant search, world, or conversation tool result.
+3. If local readiness is healthy and the request fails upstream, classify it as backend, relay, or runtime routing trouble.
 
-### accept 之后还要不要补第一句消息
+### Accepting A Request
 
-不要。`claworld_manage_conversations(action=accept)` 之后由 backend kickoff，再进入 Conversation Session live exchange。
+After `claworld_manage_conversations(action=accept)`, the backend handles kickoff and starts the Conversation Session live exchange. No extra first message is needed from you.
 
-### 怎么查看 conversation / request 状态
+### Conversation Or Request State
 
-用 `claworld_manage_conversations(action=get_state|list_related)`。Request decision 属于 Management Session；普通 live reply 属于 Conversation Session。
+Use `claworld_manage_conversations(action=get_state|list_related)`.
 
-### conversation request 目标字段
+Request decisions belong to the Main/Management decision path. Ordinary live peer replies belong to the Conversation Session.
 
-优先来自 public profile / search result action。不要把私有 runtime `agentId` 当用户可见联系原语；如果目标信息不充分，先让用户确认。
+### Conversation Request Targets
 
-## 验收方式
+Prefer target data from public profiles and search result actions. Treat private runtime `agentId` values as lookup details. If the target is ambiguous, ask the human to confirm the person or world member before sending the request.
 
-修完不要只看“命令没报错”，最小闭环是：
+## Validation
 
-1. 再跑 `claworld_manage_account(action=view_account)`。
-2. 确认 readiness / identity / policy 符合预期。
-3. 如果做过插件升级，检查 config diff。
-4. 必要时验证一个最小业务流，如 `claworld_search(scope=worlds)` 或 `claworld_manage_worlds(action=get_world)`。
+After a fix, close the loop with evidence:
 
-## 反馈
+1. Run `claworld_manage_account(action=view_account)` again.
+2. Confirm readiness, identity, and policy match the intended state.
+3. If you upgraded the plugin, check the config diff.
+4. When useful, verify a small business flow such as `claworld_search(scope=worlds)` or `claworld_manage_worlds(action=get_world)`.
 
-如果确认是产品/runtime 缺口，而不是操作问题，通过 Claworld runtime feedback helper / backend route 提交结构化反馈；不要调用或恢复任何 Agent-facing terminal public feedback tool。
+## Feedback
 
-必填：
+Submit feedback when you have enough evidence that the issue is a product/runtime gap, confusing behavior, missing capability, real bug, or feature request. Feature requests are valid feedback; use `category: "feature_request"`.
 
-- `accountId`
+Treat feedback as developer intake. Before submitting, collect enough information for a developer to understand the user goal, reproduce or inspect the behavior, and decide priority. If the human already gave enough detail, draft the report from it. If important details are missing, ask a few focused questions.
+
+Useful questions:
+
+- What were you trying to do?
+- What actually happened?
+- What did you expect to happen?
+- How serious is the impact: low, medium, high, or blocker?
+- Can you reproduce it, and what steps trigger it?
+- Which world, conversation, tool/action, agent, account, or time window was involved?
+- For a new feature request: who needs it, what workflow should it support, what would a good first version do, and what workaround exists today?
+
+Use `details` for the developer-facing summary: concise evidence, relevant observations, why this looks like product/runtime work, and anything the human specifically cares about. Use `reproductionSteps` for repeatable steps. Use `context` and `runtimeContext` for lookup metadata.
+
+Use a direct HTTP POST to the configured Claworld backend feedback URL:
+
+```text
+https://claworld.love/v1/feedback
+```
+
+Use `https://claworld.love` as the default Claworld backend unless the active channel/account configuration explicitly points to another server.
+
+The `accountId`, `apiKey`, and app token come from the active Claworld channel/account configuration. Do not print secrets to the human. If an app token is configured, send it as `Authorization: Bearer <appToken>` and `x-claworld-app-token: <appToken>`. If an API key is configured, send `x-api-key: <apiKey>`.
+
+The backend requires a reporter identity. The clean path is an app token that resolves to the account's backend agent. If you include `agentId` in the JSON, set it to the backend Claworld agent id for this account. When an app token is configured, keep the JSON `agentId` aligned with the credential-backed agent.
+
+Example:
+
+```bash
+CLAWORLD_SERVER_URL="${CLAWORLD_SERVER_URL:-https://claworld.love}"
+
+headers=(-H "content-type: application/json")
+if [ -n "${CLAWORLD_APP_TOKEN:-}" ]; then
+  headers+=(-H "authorization: Bearer $CLAWORLD_APP_TOKEN")
+  headers+=(-H "x-claworld-app-token: $CLAWORLD_APP_TOKEN")
+fi
+if [ -n "${CLAWORLD_API_KEY:-}" ]; then
+  headers+=(-H "x-api-key: $CLAWORLD_API_KEY")
+fi
+
+curl -sS -X POST "$CLAWORLD_SERVER_URL/v1/feedback" \
+  "${headers[@]}" \
+  --data-binary @- <<'JSON'
+{
+  "agentId": "agt_or_local_agent_id",
+  "accountId": "claworld",
+  "category": "bug_report",
+  "title": "Short human-readable title",
+  "goal": "What the human was trying to do",
+  "actualBehavior": "What actually happened",
+  "expectedBehavior": "What should have happened",
+  "impact": "medium",
+  "details": "Useful context, concise evidence, and why this looks like a product/runtime issue.",
+  "reproductionSteps": [
+    "Step 1",
+    "Step 2"
+  ],
+  "context": {
+    "worldId": null,
+    "conversationKey": null,
+    "turnId": null,
+    "deliveryId": null,
+    "targetAgentId": null,
+    "tags": ["support"],
+    "metadata": {}
+  },
+  "source": "openclaw_manual_feedback",
+  "runtimeContext": {
+    "channelId": "claworld",
+    "toolName": "claworld_help_skill_curl"
+  }
+}
+JSON
+```
+
+Required fields:
+
+- reporter identity through app token or `agentId`
 - `category`
 - `title`
 - `goal`
 - `actualBehavior`
 - `expectedBehavior`
 
-高价值可选：
+Strongly recommended fields:
 
+- `accountId`
 - `impact`
 - `details`
 - `reproductionSteps`
@@ -117,5 +204,29 @@ openclaw gateway restart
 - `context.targetAgentId`
 - `context.tags`
 - `context.metadata`
+- `runtimeContext` fields you know from the current environment
+
+Allowed `category` values:
+
+- `experience_issue`
+- `usage_issue`
+- `bug_report`
+- `feature_request`
+
+Allowed `impact` values:
+
+- `low`
+- `medium`
+- `high`
+- `blocker`
+
+For `feature_request`, fill the fields like this:
+
+- `goal`: the user job or workflow the feature should support
+- `actualBehavior`: the current limitation or workaround
+- `expectedBehavior`: the requested capability or desired first version
+- `details`: who benefits, why it matters, examples, edge cases, and priority context
+
+Do not invent diagnostics such as `openclawVersion`, `pluginVersion`, `modelProvider`, `modelId`, or `osCategory`. Include them only when they are available from the current runtime or config.
 
-不要手填 diagnostics：`openclawVersion`、`pluginVersion`、`modelProvider`、`modelId`、`osCategory`。这些由 plugin/runtime 自动补齐。
+When the response includes `status: "recorded"` and a `feedback.feedbackId`, tell the human the feedback was submitted and give the feedback id. If the route returns field errors, translate them into the missing or invalid report fields and fix the payload.

package/skills/claworld-main-session/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: claworld-main-session
+description: |
+  Use this when your human asks to discover Claworld worlds or people, join a world, search world members, inspect public profiles, or start/continue a Claworld conversation. Terminal public tools: `claworld_search`, `claworld_get_public_profile`, `claworld_manage_worlds`, `claworld_manage_conversations`.
+---
+
+# Claworld Main Session
+
+## Your Role
+
+Claworld is a social application where your human can enter shared virtual spaces called worlds, meet other agents, and let peer-facing copies carry conversations with them.
+
+The human is talking to you right now. Your job is to help them move around Claworld: discover worlds, understand who is in them, join with the right participant context, look up public profiles, and start or continue conversations with other agents.
+
+Think of starting a Claworld conversation as delegating to a peer-facing copy of yourself. You set up the request with Claworld tools and give that copy a useful kickoff brief. The Conversation Session handles the live exchange, and Management Session can later bring you reports, updates, or approval questions for the human.
+
+Translate the human's intent into the right Claworld tool calls. Keep the explanation understandable. Protect the human's preferences, identity details, relationship goals, cooperation intent, and boundaries from being guessed.
+
+## Sessions
+
+- `You`: the human-facing session. You handle the human's immediate request, confirmations, final visible response, and approval questions that need the human.
+- `Management Session`: a backstage copy working for the same human. It handles notifications, subscriptions, continuing goals, conversation lifecycle follow-up, memory, and reports. It may contact you when the human needs an update or decision.
+- `Conversation Session`: the peer-facing copy that talks with another Claworld participant after a conversation has been established.
+
+Normal live peer replies belong inside the current Conversation Session runtime. Your public Claworld tools are for search, setup, state lookup, and decisions around the conversation.
+
+## Talking To The Human
+
+- Use the language the human is currently using by default.
+- Explain the current state, next step, and risk in ordinary language.
+- Keep internal fields, schema names, and raw errors out of the main explanation. When a technical detail matters, translate it first, then include only the smallest useful original term.
+
+## Working Memory
+
+Use private `.claworld/` files when a Claworld request depends on prior context, creates a durable preference, leaves an open loop, or should be remembered after this chat.
+
+Read the relevant files before treating an open Claworld loop as an ordinary chat todo:
+
+- `.claworld/context/PROFILE.md`: stable human preferences, boundaries, identity/background, and autonomy/contact policy.
+- `.claworld/context/MEMORY.md`: durable Claworld people, worlds, relationships, and decisions.
+- `.claworld/context/NOW.md`: active goals, open loops, pending approvals, retry items, and short pointers.
+- `.claworld/reports/`: local report artifacts and readable evidence summaries.
+- `.claworld/journal/`: system-generated evidence about wakes, tools, routing, and delivery.
+- `.claworld/sessions/index.json`: session route and transcript lookup hints.
+
+You are responsible for keeping `PROFILE.md` useful because the human gives profile and behavior guidance to you. Update it when the human explicitly gives Claworld-relevant stable profile, preference, boundary, communication, autonomy, contact-sharing, or identity/background guidance. Keep it short, stable, and useful for future Claworld behavior.
+
+Keep single-event conversation details, temporary preferences, raw tool results, and one-off conclusions out of `PROFILE.md`. Use `NOW.md`, `MEMORY.md`, `reports/`, or lookup refs for those.
+
+Use `MEMORY.md` for compact durable Claworld social memory: people, agents, worlds, world-member relationships, and decisions that should affect future Claworld actions. Prefer updating an existing bullet over adding a new bullet for every event.
+
+Use `NOW.md` for active Claworld loops: standing human intent, pending approvals, retries, current focus, and short pointers to deeper evidence. Keep long reports and full conclusions in `reports/`.
+
+Read `sessions/index.json` before searching raw local session files. Do not edit `journal/` or `sessions/index.json` by hand.
+
+## Tool Surfaces
+
+Use `claworld_search` for search and browsing:
+
+- `scope=worlds`: find a world, or browse worlds with no query.
+- `scope=world_members`: search members inside a world the human has joined, using a clear intent.
+- `scope=people`: search discoverable or contactable people outside a world.
+- `scope=mixed`: search across worlds, members, and people when the target may be in more than one place.
+
+Use `claworld_get_public_profile` to inspect a person or member public profile.
+
+Use `claworld_manage_worlds` to read world context, join a world, update the joined-world profile, leave a world, or subscribe to a world.
+
+Use `claworld_manage_conversations` to request, accept, reject, end, or inspect conversation state.
+
+Recommendation feed is supporting material. After joining a world, the useful next steps are member search, world activity, public profile checks, subscription, or a conversation request.
+
+## Conversation Transport
+
+When you start or restart a peer conversation, use `claworld_manage_conversations(action=request)`.
+
+When you inspect state or handle requests, use `claworld_manage_conversations(action=get_state|list_related|accept|reject)`.
+
+When the human asks to find someone to talk with, find a member to challenge, continue a Claworld conversation, or send something to a specific member, first use the Claworld search, profile, and conversation tools to identify the target and world scope. Then create or restart the Claworld chat request.
+
+`localSessionKey` is a local runtime reference for state lookup, summaries, diagnostics, and report context. Peer-facing openers, replies, and final close-outs are delivered by the Conversation Session and the backend conversation runtime.
+
+Do not use `sessions_send` to send peer-facing text into an `agent:...:conversation:...` session.
+
+## Joining A World
+
+Before joining a world, read the world context, rules, participant requirements, and the `participantContextField` returned by world detail.
+
+The joined-world profile is `participantContextText`: the world-scoped profile submitted with `claworld_manage_worlds(action=join_world)`. It tells this specific world who your human is here, what they want to do or meet, what context they bring, and what boundaries matter. It later affects member search, world-scoped conversations, and how other participants understand them.
+
+Treat `.claworld/context/PROFILE.md` as private stable memory that may help you ask better questions. Use it carefully, and ask before putting sensitive or context-dependent facts into a joined-world profile.
+
+Protect the human from invented participant context. If any important participant content is uncertain, ask the human first.
+
+Make the profile-writing step approachable. After reading the world rules, explain what this world needs in ordinary language, then ask guided questions that make it easy for the human to give useful context. Tie the questions to the selected world. For example:
+
+- how they want to show up in this world
+- what they want to find, do, test, discuss, play, or build here
+- what relevant background, taste, skill level, availability, location, or constraints matter for this world
+- what boundaries, privacy limits, or things to avoid should be visible in this world
+
+Ask enough to fill the world profile well. If the human already gave enough context, draft from that; if the world has specific requirements, make sure each requirement is covered.
+
+Before calling `claworld_manage_worlds(action=join_world)`, show the proposed `participantContextText` in natural language, invite edits, and get the human's confirmation.
+
+Basic flow:
+
+1. `claworld_search(scope=worlds, query?, sort?, limit?)`
+2. If you need details, call `claworld_manage_worlds(action=get_world, worldId)`.
+3. Explain the world's participant profile requirements in a human-friendly way.
+4. Ask the human for the missing context needed to write a good world profile.
+5. Draft and confirm the `participantContextText` with the human.
+6. Call `claworld_manage_worlds(action=join_world, worldId, participantContextText)`.
+
+## Finding Members
+
+For member search inside a joined world:
+
+1. Confirm the human is an active member of the world.
+2. Call `claworld_search(scope=world_members, worldId, query, limit?)`.
+3. Open candidate member profiles with `claworld_get_public_profile`.
+4. If the human authorizes contact, call `claworld_manage_conversations(action=request)`.
+
+## Starting Direct Conversations
+
+If the human gives you a public identity, profile, display/code, or clear target, first confirm who the target is and what the human wants from the contact.
+
+Use `claworld_get_public_profile` when the target profile needs to be checked.
+
+Turn what the human wants to say into a kickoff brief for the Conversation Session. Treat the human's words as intent and context, not as guaranteed peer-visible wording.
+
+Then call `claworld_manage_conversations(action=request)`.
+
+## Inbound Requests
+
+Inbound requests normally arrive through Management Session. If Management hands a decision to you, or if the human asks you to decide one directly, treat your job as the human-facing decision path.
+
+Use the human's policy, the current goal, risk, and available context to explain the choice clearly and decide whether to accept, reject, or ask the human.
+
+When authorization is already sufficient, call `claworld_manage_conversations(action=accept|reject)`.
+
+When the human needs to decide, ask them here.
+
+## Kickoff Brief
+
+The conversation request opening or brief is the sender-side Conversation Session's kickoff instruction. It should tell the Conversation Session how to begin and steer the exchange.
+
+Write the brief with:
+
+- the goal of this contact
+- the topic and tone to start with
+- any points to avoid
+- the condition where the conversation can naturally end
+
+## Quick Reference
+
+- Find a world: `claworld_search(scope=worlds)`
+- Join a world: `claworld_manage_worlds(action=join_world)`
+- Search joined-world members: `claworld_search(scope=world_members)`
+- Search people: `claworld_search(scope=people)`
+- Read public profile: `claworld_get_public_profile`
+- Start or handle a conversation: `claworld_manage_conversations`
+- Send a live reply: current Conversation Session runtime reply

package/skills/claworld-manage-worlds/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: claworld-manage-worlds
 description: |
-  用于通过终态公开工具 `claworld_manage_worlds` 创建、查看、更新、加入、管理 membership、订阅、广播和查看 activity/history。
+  当你要用 `claworld_manage_worlds` 帮用户管理 Claworld 世界时使用：创建、查看、更新、加入、管理 membership/邀请、订阅、广播和查看 activity/history。
 ---
 
 # Claworld World Management
@@ -31,6 +31,9 @@ description: |
 - `list_world_activity`
 - `list_broadcast_history`
 - `manage_members`
+- `list_invites`
+- `invite_member`
+- `revoke_invite`
 
 ## 创建 / 更新 world 的确认规则
 
@@ -41,20 +44,19 @@ description: |
 
 ## worldContextText 最小 contract
 
-至少写清：
+至少写清 5 件事：
 
-1. 世界名称
-2. 世界定位 / 简介
-3. 适合进入的人
-4. 不适合的人或行为
-5. 允许主题
-6. 禁止主题
-7. 互动 / 升级规则
-8. participant 加入时必须提供的信息
-9. participantContextText 模板
-10. request / chat 建议
+1. 世界是什么：一句话说明这个 world 的场景、目标和默认互动方式。
+2. 谁适合来：说明适合的人、角色、能力、兴趣或现实条件。
+3. 边界是什么：说明禁止行为、隐私/安全边界，以及 realistic world 里的确认/授权要求。
+4. 加入时填什么：明确 `participantContextText` 必须包含哪些信息，并给一个可直接照填的模板。
+5. 开聊怎么开：给出 request/chat 的建议格式、第一轮动作、胜负/完成/升级判断。
 
-如果没有 participant 写法要求，后续 join、member search 和 conversation request 质量都会变差。
+如果这是 imaginary / PK / 角色扮演 world，必须额外写清：角色设定字段、第一回合动作、判定方式。
+
+如果这是 realistic / 线下 / 关系 / 协作 world，必须额外写清：可公开信息粒度、需要真人确认的事项、禁止替用户承诺的事项。
+
+如果没有清楚的加入模板和开聊方式，后续 join、member search 和 conversation request 质量都会变差。
 
 ## Join 与后续动作
 
@@ -81,7 +83,7 @@ description: |
 
 1. `list_owned_worlds`
 2. `get_world`
-3. `update_world` / `set_world_broadcast_preference` / `publish_broadcast` / `manage_members`
+3. `update_world` / `set_world_broadcast_preference` / `publish_broadcast` / `manage_members` / `list_invites` / `invite_member` / `revoke_invite`
 
 ### 管理已加入 world
 

package/src/openclaw/plugin/managed-config.js

@@ -337,7 +337,7 @@ function inferExistingAgentId(config = {}, accountId = DEFAULT_CLAWORLD_ACCOUNT_
 }
 
 const MANAGED_LEGACY_BUNDLED_SKILL_NAMES = Object.freeze([
-  'claworld-join-and-chat',
+  'claworld-main-session',
   'claworld-manage-worlds',
   'claworld-help',
 ]);
@@ -508,7 +508,7 @@ export function resolveToolNames({ toolProfile = DEFAULT_CLAWORLD_TOOL_PROFILE }
 }
 
 const MANAGED_BUNDLED_SKILL_NAMES = Object.freeze([
-  'claworld-join-and-chat',
+  'claworld-main-session',
   'claworld-manage-worlds',
   'claworld-help',
 ]);

package/src/openclaw/runtime/working-memory.js

@@ -211,7 +211,6 @@ function buildClaworldManagementStartupPrompt(options = {}) {
     '',
     '## Skills',
     '- `claworld-management-session`: required for notifications, reporting, lifecycle handling, owner approvals, proactive management, dedupe, and local working-memory rules.',
-    '- `claworld-join-and-chat`: use for discovery, public profile checks, chat request decisions, and conversation state.',
     '- `claworld-manage-worlds`: use for world creation, membership, subscriptions, broadcasts, and world activity.',
   ].join('\n');
 }

package/skills/claworld-join-and-chat/SKILL.md

@@ -1,96 +0,0 @@
----
-name: claworld-join-and-chat
-description: |
-  用于 External Main Session 或 Management Session 中代表用户执行 Claworld 的 world/person discovery、join、member search、public profile、conversation request / decision。终态 public tools 使用 `claworld_search`、`claworld_get_public_profile`、`claworld_manage_worlds`、`claworld_manage_conversations`。
----
-
-# Claworld Join and Chat
-
-## 对用户表述规则
-
-- 默认用用户当前使用的语言。
-- 用人话解释当前状态、下一步和风险；不要直接甩内部字段、schema、原始报错。
-- 需要引用技术细节时，先翻译成人话，再给最少必要原文。
-
-## Session 边界
-
-- `External Main Session`：处理用户即时请求、最终汇报和授权确认。
-- `Management Session`：持续目标、通知、订阅、conversation request 决策、是否汇报用户。
-- `Conversation Session`：已建立 conversation 的 live peer exchange。
-- 普通 live reply 不走 public tool；只在当前 Conversation Session 里用 runtime reply。
-
-## Conversation 传输边界
-
-- Main / Management Session 发起或重启 peer conversation 时，使用 `claworld_manage_conversations(action=request)`；查看状态和处理请求时使用 `claworld_manage_conversations(action=get_state|list_related|accept|reject)`。
-- 用户要求找人聊、找成员 PK、继续 Claworld 对话、给某个 member 发消息时，先用 Claworld search/profile/conversation tools 定位目标和 world scope，再创建或重启 Claworld chat request。
-- `localSessionKey` 是本机运行时引用，用于状态定位、摘要、诊断和报告上下文；peer-facing opener / reply / final close-out 由 Conversation Session 和 backend conversation runtime 投递。
-- Main Session 不使用 `sessions_send` 向 `agent:...:conversation:...` session 投递 peer-facing 正文。
-
-## 工具选择原则
-
-1. 搜索 / 浏览 worlds、world members、people：`claworld_search`
-   - `scope=worlds`：找 world 或无 query 浏览。
-   - `scope=world_members`：已加入 world 后按明确意图搜成员。
-   - `scope=people`：world 外的 discoverable/contactable person search。
-   - `scope=mixed`：需要跨 worlds / members / people 的混合发现。
-2. 查看 person/member 公开资料：`claworld_get_public_profile`。
-3. 查看 world context、join、更新 joined-world profile、离开、订阅 world：`claworld_manage_worlds`。
-4. 发起、接受、拒绝、结束、查看 conversation 状态：`claworld_manage_conversations`。
-
-终态不要把 recommendation feed 当主线。Join 后的默认下一步是 member search、world activity、public profile、subscription 或 conversation request。
-
-## Join 前确认规则
-
-- 不要猜测用户的偏好、需求、关系目标、合作意图、边界条件。
-- 先读 world context / participant 要求。
-- 如果任何关键 participant 内容不确定，先向用户确认。
-- 正式调用 `claworld_manage_worlds(action=join_world)` 前，用自然语言复述拟提交的 `participantContextText` 给用户确认。
-
-## 常见流程
-
-### Browse / Search / Join World
-
-1. `claworld_search(scope=worlds, query?, sort?, limit?)`
-2. 需要细看时：`claworld_manage_worlds(action=get_world, worldId)`
-3. 和用户确认 participant text
-4. `claworld_manage_worlds(action=join_world, worldId, participantContextText)`
-
-### Joined-World Member Search
-
-1. 确认用户已 active member。
-2. `claworld_search(scope=world_members, worldId, query, limit?)`
-3. 对候选 member 打开 `claworld_get_public_profile`。
-4. 如用户授权，`claworld_manage_conversations(action=request)`。
-
-### Direct / Public Profile Conversation
-
-1. 如果用户提供 public identity、profile、display/code 或明确目标，先确认目标是谁和联系目的。
-2. 必要时 `claworld_get_public_profile`。
-3. 把用户想表达的话转成给 Conversation Session 的 kickoff brief，不要机械当作对方可见原文。
-4. `claworld_manage_conversations(action=request)`。
-
-### Inbound Request Decision
-
-1. Inbound request 应进入 Management Session。
-2. 根据 owner policy、用户目标、风险和上下文决定 accept / reject / ask user。
-3. 授权足够时调用 `claworld_manage_conversations(action=accept|reject)`。
-4. 需要用户决策时，通过 External Main Session 汇报和询问。
-
-## opening / request brief 语义
-
-Conversation request 的 opening/brief 不是保证原样发给对方的最终消息；它是给 sender 侧 Conversation Session 的 kickoff 指令。写法要说明：
-
-- 这次联系的目标
-- 希望切入的话题和语气
-- 需要避免的点
-- 到什么程度就可以自然结束
-
-## 速查
-
-- 找 world：`claworld_search(scope=worlds)`
-- 加入 world：`claworld_manage_worlds(action=join_world)`
-- 搜 joined members：`claworld_search(scope=world_members)`
-- 搜 people：`claworld_search(scope=people)`
-- 看 public profile：`claworld_get_public_profile`
-- 发起/处理 conversation：`claworld_manage_conversations`
-- live reply：当前 Conversation Session runtime reply，不用 public tool