{
  "schemaVersion": "1.0",
  "item": {
    "slug": "anytype",
    "name": "Anytype",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/tadas-subonis/anytype",
    "canonicalUrl": "https://clawhub.ai/tadas-subonis/anytype",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/anytype",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=anytype",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SETUP.md",
      "SKILL.md",
      "scripts/anytype_api.py",
      "references/api.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/anytype"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/anytype",
    "agentPageUrl": "https://openagent3.xyz/skills/anytype/agent",
    "manifestUrl": "https://openagent3.xyz/skills/anytype/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/anytype/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Anytype Skill",
        "body": "Binary: anytype (install via https://github.com/anyproto/anytype-cli)\nAPI base: http://127.0.0.1:31012\nAuth: Authorization: Bearer <ANYTYPE_API_KEY> (key stored in .env as ANYTYPE_API_KEY)\nAPI docs: https://developers.anytype.io\n\nInstance config: Space IDs, tag IDs, collection IDs, and sharing links are in SETUP.md (same directory). Read that alongside this file."
      },
      {
        "title": "Check Status First",
        "body": "anytype auth status     # is an account set up?\nanytype space list      # is the service running + spaces joined?\n\nIf either fails → follow Setup below. Otherwise skip to API Usage."
      },
      {
        "title": "Setup (one-time)",
        "body": "# 1. Create a dedicated bot account (generates a key, NOT mnemonic-based)\nanytype auth create my-bot\n\n# 2. Install and start as a user service\nanytype service install\nanytype service start\n\n# 3. Have the space owner send an invite link from Anytype desktop, then join\nanytype space join <invite-link>\n\n# 4. Create an API key\nanytype auth apikey create my-key\n\n# 5. Store the key\necho \"ANYTYPE_API_KEY=<key>\" >> ~/.openclaw/workspace/.env"
      },
      {
        "title": "API Usage",
        "body": "Load the API key (reads only ANYTYPE_API_KEY from env or .env):\n\nimport os, requests\n\ndef load_api_key():\n    if \"ANYTYPE_API_KEY\" in os.environ:\n        return os.environ[\"ANYTYPE_API_KEY\"]\n    env_path = os.path.expanduser(\"~/.openclaw/workspace/.env\")\n    if os.path.exists(env_path):\n        for line in open(env_path):\n            if line.strip().startswith(\"ANYTYPE_API_KEY=\"):\n                return line.strip().split(\"=\", 1)[1]\n    return \"\"\n\nAPI_KEY = load_api_key()\nBASE = 'http://127.0.0.1:31012'\nHEADERS = {'Authorization': f'Bearer {API_KEY}', 'Content-Type': 'application/json'}\n\nSee references/api.md for all endpoints and request shapes."
      },
      {
        "title": "Common Patterns",
        "body": "List spaces:\n\nGET /v1/spaces\n\nSearch objects globally:\n\nPOST /v1/search\n{\"query\": \"meeting notes\", \"limit\": 10}\n\nList objects in a space:\n\nGET /v1/spaces/{space_id}/objects?limit=50\n\nCreate an object:\n\nPOST /v1/spaces/{space_id}/objects\n{\"type_key\": \"page\", \"name\": \"My Page\", \"body\": \"Markdown content here\"}\n\nUpdate an object (patch body/properties):\n\nPATCH /v1/spaces/{space_id}/objects/{object_id}\n{\"markdown\": \"Updated content\"}\n\n⚠️ Create uses body, Update uses markdown — different field names for the same content. Easy to mix up.\n\n⚠️ CRITICAL: PATCH does NOT update the body/content field. Sending body or markdown in a PATCH silently succeeds (HTTP 200) but the content is NOT updated in Anytype. Only metadata fields like name are updated via PATCH.\n\nThe only reliable way to update an object's content is: DELETE + recreate.\n\n⚠️ This is destructive. Always save the old content before deleting:\n\n# Step 0: fetch and save existing content before deleting\nold = requests.get(f\"{BASE}/v1/spaces/{space_id}/objects/{old_id}\", headers=headers).json()\nold_content = old.get(\"object\", {}).get(\"snippet\", \"\")  # keep a local copy\n\n# Step 1: delete old object (irreversible via API — confirm before running)\nrequests.delete(f\"{BASE}/v1/spaces/{space_id}/objects/{old_id}\", headers=headers)\n\n# Step 2: create new object with full updated content\nresp = requests.post(f\"{BASE}/v1/spaces/{space_id}/objects\",\n    json={\"name\": name, \"type_key\": \"page\", \"body\": new_content},\n    headers=headers)\nnew_id = resp.json()[\"object\"][\"id\"]\n\nStore the new object ID — callers must update any references (e.g. related_pages) after recreation. Deleted objects may be recoverable from the Anytype bin in the desktop app.\n\nUse scripts/anytype_api.py as a ready-made helper for making API calls."
      },
      {
        "title": "Key Constraints (learned from testing)",
        "body": "links property is read-only — system-managed, populated only by the desktop editor. API returns 400 if you try to set it.\nCollections cannot have an icon set on create — causes a 500. Create without icon, add it after.\nbody vs markdown — create uses body, update uses markdown.\nPATCH cannot update content — body/markdown fields in PATCH are silently ignored. HTTP 200 is returned but content is unchanged. To update content: DELETE + recreate.\nrelated_pages custom property (key: related_pages, format: objects) — writable via API for linking objects. Must be created in the space first if it doesn't exist."
      },
      {
        "title": "Object Type Preference",
        "body": "Default to page for all content. Notes (note type) are the exception — use only when content is informal/scratchpad and doesn't need linking into the knowledge graph.\n\nEverything meaningful (call notes, research, hub pages, product docs, meeting summaries) → type_key: \"page\"."
      },
      {
        "title": "Knowledge Graph Principles — Apply These Always",
        "body": "Anytype is a linked knowledge base, not a flat file store. Every time you create or update content, ask: how does this connect to what already exists?"
      },
      {
        "title": "1. Link Everything",
        "body": "Use [[Page Name]] style inline links in the markdown body to reference related objects.\nWhen creating a new page, search for related existing pages first and link back to them.\nWhen updating an existing page, add links to any newly created pages that are related."
      },
      {
        "title": "2. Collections as Cluster Containers",
        "body": "For any topic cluster, create a Collection (type_key: collection) — not a plain page hub.\nCollections are Anytype's native container type. They appear in the sidebar, support multiple views (grid, list, kanban), and are queryable.\nUse the Lists API to add child objects to a collection.\nAlso maintain a hub page inside the collection as the written overview (description + links).\n\nCreate + populate a collection:\n\n# 1. Create (no icon on create — causes 500)\ncol = api('POST', f'/v1/spaces/{SPACE}/objects', {'type_key': 'collection', 'name': 'My Cluster'})\ncol_id = col['object']['id']\n\n# 2. Add objects\napi('POST', f'/v1/spaces/{SPACE}/lists/{col_id}/objects', {'objects': [id1, id2, id3]})\n\nSidebar note: Sidebar pinning is manual only — no API. Ask the user to pin collections in the Anytype desktop app."
      },
      {
        "title": "3. Bidirectional Awareness",
        "body": "Anytype shows backlinks automatically, but you must write forward links in the body.\nAfter creating content, update the hub page to include a link to the new object."
      },
      {
        "title": "4. Before Creating a Page",
        "body": "1. Search: POST /v1/spaces/{space_id}/search {\"query\": \"<topic>\", \"limit\": 10}\n2. Check if a page already exists — update it rather than duplicate\n3. Identify the parent hub page(s) this belongs to\n4. Create the page with inline links to related pages in the body\n5. Update the hub page(s) to add a link to the new page"
      },
      {
        "title": "5. Hub Page Template",
        "body": "When creating a hub page, use this structure:\n\n## Overview\n<2-3 sentence summary>\n\n## Pages\n- [Child Page Name](anytype://object?objectId=<id>&spaceId=<space_id>) — one-line description\n- [Another Page](anytype://object?objectId=<id>&spaceId=<space_id>) — one-line description\n\n## Key Facts\n- Fact 1\n- Fact 2"
      },
      {
        "title": "6. Native Object Links (Anytype Graph Feature)",
        "body": "Anytype has two link mechanisms. Use both:\n\nA. System links property (read-only via API)\n\nThe built-in links property is auto-populated by the Anytype desktop app when you use @mention or [[]] syntax in the rich text editor. The API cannot set it directly — attempting to do so returns 400.\n\nB. Custom related_pages property (writable via API) ✅\n\nCreate a custom objects-type property called related_pages (key: related_pages) in your space. This shows up in each object's sidebar and lets the API express object relationships.\n\n// On create:\n{\n  \"type_key\": \"page\",\n  \"name\": \"My Page\",\n  \"body\": \"...\",\n  \"properties\": [\n    {\"key\": \"related_pages\", \"objects\": [\"<hub_id>\", \"<sibling_id>\"]}\n  ]\n}\n\nRule: Hub pages → related_pages set to all children. Child pages → related_pages set back to their hub. This creates visible edges in the graph view."
      },
      {
        "title": "7. Inline Links Syntax",
        "body": "Use anytype:// deep links — NOT object.any.coop URLs — for links inside the app.\n\nobject.any.coop URLs in body text render as plain text and are NOT clickable inside Anytype. The only format that renders as a clickable internal link is:\n\n[Link Text](anytype://object?objectId=<object_id>&spaceId=<space_id>)\n\nHelper function:\n\ndef anytype_link(name, obj_id, space_id):\n    return f\"[→ Open: {name}](anytype://object?objectId={obj_id}&spaceId={space_id})\"\n\n⚠️ Do NOT put links inside markdown headings — Anytype strips the link and renders only plain text. Links only work as inline body text.\n\nUse object.any.coop links only when sharing with external users (outside the Anytype app)."
      },
      {
        "title": "8. Tags",
        "body": "Tags require pre-existing tag option IDs in the space — you cannot pass free-text strings directly.\n\nCreate a new tag:\n\nPOST /v1/spaces/{space_id}/properties/{tag_property_id}/tags\n{\"name\": \"my-tag\", \"color\": \"blue\"}\n→ returns tag.id — use that ID in multi_select\n\nSet tags on an object:\n\nPATCH /v1/spaces/{space_id}/objects/{object_id}\n{\n  \"properties\": [\n    {\"key\": \"tag\", \"multi_select\": [\"<tag_id_1>\", \"<tag_id_2>\"]}\n  ]\n}\n\nSee SETUP.md for the tag property ID and all defined tag IDs for this instance."
      },
      {
        "title": "9. Proactive Organization Checklist",
        "body": "After any write operation, run through:\n\nDoes a hub page exist for this topic? If not, create one.\n Did I link the new/updated page from the hub?\n Did I link related pages from within the new content?\n Are there orphan pages (no incoming links) I should connect?\n Did I set tag (project + content type + domain) on the new page?\n Did I set related_pages pointing to the hub?"
      },
      {
        "title": "Sharing Links",
        "body": "Use the public web link format when sharing externally:\n\nhttps://object.any.coop/{object_id}?spaceId={space_id}&inviteId={invite_id}#{hash}\n\nThe inviteId and #hash are space-level constants. Only object_id changes per object.\n\nSee SETUP.md for this instance's spaceId, inviteId, and hash."
      }
    ],
    "body": "Anytype Skill\n\nBinary: anytype (install via https://github.com/anyproto/anytype-cli) API base: http://127.0.0.1:31012 Auth: Authorization: Bearer <ANYTYPE_API_KEY> (key stored in .env as ANYTYPE_API_KEY) API docs: https://developers.anytype.io\n\nInstance config: Space IDs, tag IDs, collection IDs, and sharing links are in SETUP.md (same directory). Read that alongside this file.\n\nCheck Status First\nanytype auth status     # is an account set up?\nanytype space list      # is the service running + spaces joined?\n\n\nIf either fails → follow Setup below. Otherwise skip to API Usage.\n\nSetup (one-time)\n# 1. Create a dedicated bot account (generates a key, NOT mnemonic-based)\nanytype auth create my-bot\n\n# 2. Install and start as a user service\nanytype service install\nanytype service start\n\n# 3. Have the space owner send an invite link from Anytype desktop, then join\nanytype space join <invite-link>\n\n# 4. Create an API key\nanytype auth apikey create my-key\n\n# 5. Store the key\necho \"ANYTYPE_API_KEY=<key>\" >> ~/.openclaw/workspace/.env\n\nAPI Usage\n\nLoad the API key (reads only ANYTYPE_API_KEY from env or .env):\n\nimport os, requests\n\ndef load_api_key():\n    if \"ANYTYPE_API_KEY\" in os.environ:\n        return os.environ[\"ANYTYPE_API_KEY\"]\n    env_path = os.path.expanduser(\"~/.openclaw/workspace/.env\")\n    if os.path.exists(env_path):\n        for line in open(env_path):\n            if line.strip().startswith(\"ANYTYPE_API_KEY=\"):\n                return line.strip().split(\"=\", 1)[1]\n    return \"\"\n\nAPI_KEY = load_api_key()\nBASE = 'http://127.0.0.1:31012'\nHEADERS = {'Authorization': f'Bearer {API_KEY}', 'Content-Type': 'application/json'}\n\n\nSee references/api.md for all endpoints and request shapes.\n\nCommon Patterns\n\nList spaces:\n\nGET /v1/spaces\n\n\nSearch objects globally:\n\nPOST /v1/search\n{\"query\": \"meeting notes\", \"limit\": 10}\n\n\nList objects in a space:\n\nGET /v1/spaces/{space_id}/objects?limit=50\n\n\nCreate an object:\n\nPOST /v1/spaces/{space_id}/objects\n{\"type_key\": \"page\", \"name\": \"My Page\", \"body\": \"Markdown content here\"}\n\n\nUpdate an object (patch body/properties):\n\nPATCH /v1/spaces/{space_id}/objects/{object_id}\n{\"markdown\": \"Updated content\"}\n\n\n⚠️ Create uses body, Update uses markdown — different field names for the same content. Easy to mix up.\n\n⚠️ CRITICAL: PATCH does NOT update the body/content field. Sending body or markdown in a PATCH silently succeeds (HTTP 200) but the content is NOT updated in Anytype. Only metadata fields like name are updated via PATCH.\n\nThe only reliable way to update an object's content is: DELETE + recreate.\n\n⚠️ This is destructive. Always save the old content before deleting:\n\n# Step 0: fetch and save existing content before deleting\nold = requests.get(f\"{BASE}/v1/spaces/{space_id}/objects/{old_id}\", headers=headers).json()\nold_content = old.get(\"object\", {}).get(\"snippet\", \"\")  # keep a local copy\n\n# Step 1: delete old object (irreversible via API — confirm before running)\nrequests.delete(f\"{BASE}/v1/spaces/{space_id}/objects/{old_id}\", headers=headers)\n\n# Step 2: create new object with full updated content\nresp = requests.post(f\"{BASE}/v1/spaces/{space_id}/objects\",\n    json={\"name\": name, \"type_key\": \"page\", \"body\": new_content},\n    headers=headers)\nnew_id = resp.json()[\"object\"][\"id\"]\n\n\nStore the new object ID — callers must update any references (e.g. related_pages) after recreation. Deleted objects may be recoverable from the Anytype bin in the desktop app.\n\nUse scripts/anytype_api.py as a ready-made helper for making API calls.\n\nKey Constraints (learned from testing)\nlinks property is read-only — system-managed, populated only by the desktop editor. API returns 400 if you try to set it.\nCollections cannot have an icon set on create — causes a 500. Create without icon, add it after.\nbody vs markdown — create uses body, update uses markdown.\nPATCH cannot update content — body/markdown fields in PATCH are silently ignored. HTTP 200 is returned but content is unchanged. To update content: DELETE + recreate.\nrelated_pages custom property (key: related_pages, format: objects) — writable via API for linking objects. Must be created in the space first if it doesn't exist.\nObject Type Preference\n\nDefault to page for all content. Notes (note type) are the exception — use only when content is informal/scratchpad and doesn't need linking into the knowledge graph.\n\nEverything meaningful (call notes, research, hub pages, product docs, meeting summaries) → type_key: \"page\".\n\nKnowledge Graph Principles — Apply These Always\n\nAnytype is a linked knowledge base, not a flat file store. Every time you create or update content, ask: how does this connect to what already exists?\n\n1. Link Everything\nUse [[Page Name]] style inline links in the markdown body to reference related objects.\nWhen creating a new page, search for related existing pages first and link back to them.\nWhen updating an existing page, add links to any newly created pages that are related.\n2. Collections as Cluster Containers\nFor any topic cluster, create a Collection (type_key: collection) — not a plain page hub.\nCollections are Anytype's native container type. They appear in the sidebar, support multiple views (grid, list, kanban), and are queryable.\nUse the Lists API to add child objects to a collection.\nAlso maintain a hub page inside the collection as the written overview (description + links).\n\nCreate + populate a collection:\n\n# 1. Create (no icon on create — causes 500)\ncol = api('POST', f'/v1/spaces/{SPACE}/objects', {'type_key': 'collection', 'name': 'My Cluster'})\ncol_id = col['object']['id']\n\n# 2. Add objects\napi('POST', f'/v1/spaces/{SPACE}/lists/{col_id}/objects', {'objects': [id1, id2, id3]})\n\n\nSidebar note: Sidebar pinning is manual only — no API. Ask the user to pin collections in the Anytype desktop app.\n\n3. Bidirectional Awareness\nAnytype shows backlinks automatically, but you must write forward links in the body.\nAfter creating content, update the hub page to include a link to the new object.\n4. Before Creating a Page\n1. Search: POST /v1/spaces/{space_id}/search {\"query\": \"<topic>\", \"limit\": 10}\n2. Check if a page already exists — update it rather than duplicate\n3. Identify the parent hub page(s) this belongs to\n4. Create the page with inline links to related pages in the body\n5. Update the hub page(s) to add a link to the new page\n\n5. Hub Page Template\n\nWhen creating a hub page, use this structure:\n\n## Overview\n<2-3 sentence summary>\n\n## Pages\n- [Child Page Name](anytype://object?objectId=<id>&spaceId=<space_id>) — one-line description\n- [Another Page](anytype://object?objectId=<id>&spaceId=<space_id>) — one-line description\n\n## Key Facts\n- Fact 1\n- Fact 2\n\n6. Native Object Links (Anytype Graph Feature)\n\nAnytype has two link mechanisms. Use both:\n\nA. System links property (read-only via API)\n\nThe built-in links property is auto-populated by the Anytype desktop app when you use @mention or [[]] syntax in the rich text editor. The API cannot set it directly — attempting to do so returns 400.\n\nB. Custom related_pages property (writable via API) ✅\n\nCreate a custom objects-type property called related_pages (key: related_pages) in your space. This shows up in each object's sidebar and lets the API express object relationships.\n\n// On create:\n{\n  \"type_key\": \"page\",\n  \"name\": \"My Page\",\n  \"body\": \"...\",\n  \"properties\": [\n    {\"key\": \"related_pages\", \"objects\": [\"<hub_id>\", \"<sibling_id>\"]}\n  ]\n}\n\n\nRule: Hub pages → related_pages set to all children. Child pages → related_pages set back to their hub. This creates visible edges in the graph view.\n\n7. Inline Links Syntax\n\nUse anytype:// deep links — NOT object.any.coop URLs — for links inside the app.\n\nobject.any.coop URLs in body text render as plain text and are NOT clickable inside Anytype. The only format that renders as a clickable internal link is:\n\n[Link Text](anytype://object?objectId=<object_id>&spaceId=<space_id>)\n\n\nHelper function:\n\ndef anytype_link(name, obj_id, space_id):\n    return f\"[→ Open: {name}](anytype://object?objectId={obj_id}&spaceId={space_id})\"\n\n\n⚠️ Do NOT put links inside markdown headings — Anytype strips the link and renders only plain text. Links only work as inline body text.\n\nUse object.any.coop links only when sharing with external users (outside the Anytype app).\n\n8. Tags\n\nTags require pre-existing tag option IDs in the space — you cannot pass free-text strings directly.\n\nCreate a new tag:\n\nPOST /v1/spaces/{space_id}/properties/{tag_property_id}/tags\n{\"name\": \"my-tag\", \"color\": \"blue\"}\n→ returns tag.id — use that ID in multi_select\n\n\nSet tags on an object:\n\nPATCH /v1/spaces/{space_id}/objects/{object_id}\n{\n  \"properties\": [\n    {\"key\": \"tag\", \"multi_select\": [\"<tag_id_1>\", \"<tag_id_2>\"]}\n  ]\n}\n\n\nSee SETUP.md for the tag property ID and all defined tag IDs for this instance.\n\n9. Proactive Organization Checklist\n\nAfter any write operation, run through:\n\n Does a hub page exist for this topic? If not, create one.\n Did I link the new/updated page from the hub?\n Did I link related pages from within the new content?\n Are there orphan pages (no incoming links) I should connect?\n Did I set tag (project + content type + domain) on the new page?\n Did I set related_pages pointing to the hub?\nSharing Links\n\nUse the public web link format when sharing externally:\n\nhttps://object.any.coop/{object_id}?spaceId={space_id}&inviteId={invite_id}#{hash}\n\n\nThe inviteId and #hash are space-level constants. Only object_id changes per object.\n\nSee SETUP.md for this instance's spaceId, inviteId, and hash."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/tadas-subonis/anytype",
    "publisherUrl": "https://clawhub.ai/tadas-subonis/anytype",
    "owner": "tadas-subonis",
    "version": "1.0.3",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/anytype",
    "downloadUrl": "https://openagent3.xyz/downloads/anytype",
    "agentUrl": "https://openagent3.xyz/skills/anytype/agent",
    "manifestUrl": "https://openagent3.xyz/skills/anytype/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/anytype/agent.md"
  }
}