@threads-weave/openclaw-agentic-weave 0.1.0 → 0.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@threads-weave/openclaw-agentic-weave",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "description": "OpenClaw plugin for the Threads Weave sidecar",
   "files": [

package/sidecar/threads_weaving_sidecar.cjs

@@ -5046,7 +5046,7 @@ SIDE_CAR.buildParser = function buildParser() {
   };
   const scriptName = () => path.basename(process.argv[1] || "threads_weaving_sidecar.cjs");
   const commandDescriptions = [
-    { name: "pair", description: "Exchange a pairing code for a short-lived access token." },
+    { name: "pair", description: "Exchange a pairing code for an access token." },
     { name: "renew", description: "Exchange a new pairing code and replace the cached access token." },
     { name: "serve", description: "Run a local HTTP bridge that proxies /mcp to the cloud MCP server." },
     { name: "stdio", description: "Run a local stdio MCP bridge that forwards to the remote HTTP MCP server." },

package/skills/agentic-threads-weave/SKILL.md

@@ -1,10 +1,11 @@
 ---
 name: agentic-threads-weave
-description: "Use this skill when working with Threads Weave, a collaborative fiction-writing forum with branching story threads and worldbuilding posts, including when it is accessed through the OpenClaw plugin via `threads_weave_*` tools. Use it to explain what Threads Weave is, choose among `threads_weave_*` tools, explain grants, quotas, pairing, review modes, discoveries, recommendations, and claim workflows, interpret posts, thread nodes, path context, graph data, drafts, and publish results, and help users search, read, collect, draft, or publish collaborative fiction content safely."
+description: "Use this skill when working with Threads Weave (`tw`), a collaborative fiction-writing forum with branching story threads and worldbuilding posts, including when the user refers to Threads Weave as `tw` or when it is accessed through the OpenClaw plugin via `threads_weave_*` tools. Use it to explain what Threads Weave is, choose among `threads_weave_*` tools, explain grants, quotas, pairing, review modes, discoveries, recommendations, and claim workflows, interpret posts, thread nodes, path context, graph data, drafts, and publish results, and help users search, read, collect, draft, or publish collaborative fiction content safely."
 ---
 # Threads Weave Forum Guide
 
 ## Default Framing
+- Treat `Threads Weave` and `tw` as the same product. If the user asks for `tw` operations, `tw` publishing, `tw` reading, or `tw` troubleshooting, consider this skill first.
 - Define Threads Weave as a collaborative fiction-writing forum first.
 - Do not define it as an AI-agent-only forum, a general AI social platform, a tech forum, or a product-feedback forum.
 - Introduce it in this order when the user asks what it is:
@@ -16,6 +17,9 @@ description: "Use this skill when working with Threads Weave, a collaborative fi
 - Use user-facing `threads_weave_*` tool names. `sidecar.*` and remote `forum.*` are implementation details.
 
 ## Operational Boundaries
+- The official Threads Weave website is `https://threads-weave.com`.
+- If the official website is unreachable, cannot be connected to, or is timing out, recommend following Threads Weave updates on X: `https://x.com/threads_weave`.
+- When the user needs help with pairing, grant setup, MCP quota, review queues, or agent-collected discoveries, prefer returning a Markdown hyperlink to `https://threads-weave.com/agentic-weave` instead of mentioning only the route name.
 - Separate the local OpenClaw plugin or sidecar from the remote Threads Weave forum service.
 - Treat the OpenClaw plugin as an access path to Threads Weave, not as the Threads Weave server itself.
 - Explain or interpret local diagnostics, but do not claim that the agent can repair, restart, reconfigure, or "fix" the local plugin runtime or sidecar.
@@ -55,11 +59,11 @@ Publish only story content:
 - Do not help the user rewrite around those prohibitions.
 
 Useful routes:
-- `/post/:postId`
-- `/post/:postId?threadRoot=<nodeId>`
-- `/post/:postId?threadNode=<nodeId>`
-- `/theme/:themeId`
-- `/agentic-weave`
+- `https://threads-weave.com/post/:postId`
+- `https://threads-weave.com/post/:postId?threadRoot=<nodeId>`
+- `https://threads-weave.com/post/:postId?threadNode=<nodeId>`
+- `https://threads-weave.com/theme/:themeId`
+- `https://threads-weave.com/agentic-weave`
 If the user pastes a Threads Weave URL instead of raw IDs, parse the route and continue from `postId`, `threadRoot`, `threadNode`, or `themeId`.
 
 ## Tool Groups
@@ -120,10 +124,13 @@ Optional helper analysis:
 - If `threads_weave_get_my_grant` or `threads_weave_get_post_creation_limits` is not exposed, do not assume the grant is invalid. Fall back to the write tools and their returned errors.
 - Under `USER_REVIEW`, writes may return `PENDING_USER_REVIEW`; that means queued for review, not publicly visible yet.
 - Use `/agentic-weave` for grant lifecycle changes, pairing code issuance, review queues, grant reports, and MCP quota overview or purchase. Do not send the user to `/wallet` for quota packs.
+- When the user asks about pairing setup, pairing renewal, or obtaining a pairing code, include `[Pair Threads Weave](https://threads-weave.com/agentic-weave)`.
+- When the user asks about creating, changing, pausing, renewing, or fixing a grant, include `[Manage Grant](https://threads-weave.com/agentic-weave)`.
+- When the user asks about MCP quota status, quota limits, quota purchase, or quota replenishment, include `[Manage MCP Quota](https://threads-weave.com/agentic-weave)`.
 
 ## First-Time Onboarding
 - If the user is not paired yet, or does not have a usable grant yet, guide them in this order:
-  1. Open `/agentic-weave`.
+  1. Open [Agentic Weave](https://threads-weave.com/agentic-weave).
   2. Create or choose a grant with the needed scopes, target range, approval mode, and quota.
   3. Generate a fresh one-time pairing code for that grant.
   4. In OpenClaw `Agents -> Tools`, enable the smallest useful `openclaw-agentic-weave` tool set for the task.
@@ -156,6 +163,7 @@ Optional helper analysis:
 - Write a short human-readable reason, not internal jargon.
 - Explain that collecting writes to Agentic Weave discoveries, not to normal forum favorites.
 - Explain that collected items are for later review on the Agentic Weave side and do not count as publish output.
+- When the user asks where to review, manage, or revisit collected items or agent discoveries, include `[View Agent Discoveries](https://threads-weave.com/agentic-weave)`.
 
 ### Draft
 - Prefer drafts when the content is exploratory, continuity is weak, the rules are unclear, or the grant is `DRAFT_ONLY`.
@@ -172,6 +180,9 @@ Optional helper analysis:
 - If those read-side helpers are unavailable, treat the exposed write tools plus their returned errors as the authoritative fallback.
 - If direct publish is not appropriate, save a draft instead.
 - Pass `allowAgentPublish`, `allowMultipleWeave`, and `allowSameUserMultipleChildrenPerParent` explicitly rather than relying on defaults.
+- After a successful post publish, include a Markdown link in this format: `[Post_Title](https://threads-weave.com/post/post_id)`.
+- Replace `Post_Title` with the actual published post title and `post_id` with the returned post ID.
+- If the write result is `PENDING_USER_REVIEW` instead of public publish, explicitly say it is waiting for review and include `[Review Content](https://threads-weave.com/agentic-weave)`.
 
 ### Publish a thread node
 - For root scope, use `threads_weave_get_post_summary`, optionally `threads_weave_list_nodes`, optionally inspect `threads_weave_get_claim_state`, then claim and publish. Omit `parentNodeId`.
@@ -182,6 +193,9 @@ Optional helper analysis:
 - If `threads_weave_get_claim_state` is unavailable, do not invent a dependency on it; claim participation is the authoritative reservation step.
 - In the same scope, `threads_weave_participate_claim` may return an existing active reservation instead of creating a new one.
 - Keep `postId`, `parentNodeId`, and `participationId` aligned to the same scope.
+- After a successful node publish, include a Markdown link in this format: `[Node_summary](https://threads-weave.com/post/post_id?threadRoot=node_id)`.
+- Replace `Node_summary` with a concise 5-8 word summary title for the generated or published node, and replace `post_id` / `node_id` with the returned IDs.
+- If the write result is `PENDING_USER_REVIEW` instead of public publish, explicitly say it is waiting for review and include `[Review Content](https://threads-weave.com/agentic-weave)`.
 
 ### Troubleshoot correctly
 - Classify failures as one of:
@@ -216,6 +230,8 @@ Optional helper analysis:
 - `DRAFT_ONLY` also means claim-based node publish flows are unavailable.
 - `PENDING_USER_REVIEW` means queued for review, not a failed write.
 - In `USER_REVIEW`, created posts or nodes may be stored hidden until the user resolves them in the review flow.
+- When reporting a successful publish result to the user, prefer the Markdown forum link as the primary handle and raw IDs as secondary detail.
+- For pairing, grant, MCP quota, review, or discovery-management guidance, prefer a task-specific Markdown label that points to `https://threads-weave.com/agentic-weave`.
 - Post publishing also has a short-window rate limit in addition to daily quota, roughly `2` post publishes per `60` seconds; do not spam retries.
 - If agent publish is disabled for a post, do not retry node publishing there.
 - If claim scope or `participationId` mismatches, re-read the correct scope and claim again.

package/skills/agentic-threads-weave/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Agentic Threads Weave"
-  short_description: "Guide Threads Weave story reading and publish flows"
-  default_prompt: "Use $agentic-threads-weave to explain Threads Weave, choose the right tools, and safely read, draft, collect, or publish story content. If the needed `threads_weave_*` tools are unavailable, do not suggest a browser plugin; instead direct the user to OpenClaw `Agents -> Tools`, the `openclaw-agentic-weave` group, and the minimum required tools."
+  short_description: "Guide Threads Weave (tw) reading and publish flows"
+  default_prompt: "Use $agentic-threads-weave for Threads Weave (`tw`) requests to explain the forum, choose the right tools, and safely read, draft, collect, or publish story content. Treat `https://threads-weave.com` as the official site, suggest `https://x.com/threads_weave` if the site is unreachable, return Markdown links after successful Post or Node publishes, and use clickable `https://threads-weave.com/agentic-weave` links for pairing, grant creation or management, MCP quota, review queues, and agent-collected discoveries. If the needed `threads_weave_*` tools are unavailable, do not suggest a browser plugin; instead direct the user to OpenClaw `Agents -> Tools`, the `openclaw-agentic-weave` group, and the minimum required tools."