# Send EVC Team Relay to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - 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. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "evc-team-relay", "name": "EVC Team Relay", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/venturecrew/evc-team-relay", "canonicalUrl": "https://clawhub.ai/venturecrew/evc-team-relay", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/evc-team-relay", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=evc-team-relay", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "README.md", "SKILL.md", "scripts/upsert-file.sh", "scripts/read-file.sh", "scripts/read.sh", "scripts/create-file.sh" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "evc-team-relay", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T13:55:50.901Z", "expiresAt": "2026-05-06T13:55:50.901Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=evc-team-relay", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=evc-team-relay", "contentDisposition": "attachment; filename=\"evc-team-relay-1.1.2.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "evc-team-relay" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/evc-team-relay" }, "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." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/evc-team-relay", "downloadUrl": "https://openagent3.xyz/downloads/evc-team-relay", "agentUrl": "https://openagent3.xyz/skills/evc-team-relay/agent", "manifestUrl": "https://openagent3.xyz/skills/evc-team-relay/agent.json", "briefUrl": "https://openagent3.xyz/skills/evc-team-relay/agent.md" } } ``` ## Documentation ### EVC Team Relay REST API skill for reading and writing collaborative Obsidian vault documents via EVC Team Relay. ### Environment variables VariableRequiredDescriptionRELAY_CP_URLyesControl plane URL, e.g. https://cp.tr.entire.vcRELAY_EMAILyesUser email for authenticationRELAY_PASSWORDyesUser passwordRELAY_TOKENnoJWT token (set via export RELAY_TOKEN=$(scripts/auth.sh)) ### Quick start # 1. Authenticate — get a JWT token (stored in env var, not visible in ps) export RELAY_TOKEN=$(scripts/auth.sh) # 2. List shares to find available documents scripts/list-shares.sh # 3. Read a file from a folder share BY PATH (most common) scripts/read-file.sh "Marketing/plan.md" # 4. Create or update a file in a folder share scripts/upsert-file.sh "note.md" "# Content" # 5. List all files in a folder share scripts/list-files.sh # 6. Delete a file from a folder share scripts/delete-file.sh "old-note.md" # 7. Read a doc share (single document, share_id = doc_id) scripts/read.sh # 8. Write to a doc share scripts/write.sh "# Updated content" All scripts accept the token via RELAY_TOKEN env var (preferred) or as the first CLI argument (backward-compatible). ### Two kinds of shares Doc shareFolder shareContainsSingle documentMultiple filesdoc_idSame as share_idEach file has its own doc_id (in folder metadata)Readread.sh read-file.sh "path/to/file.md"Writewrite.sh upsert-file.sh "path" DeleteN/Adelete-file.sh "path" Most shares are folder shares. Use read-file.sh and upsert-file.sh — they handle path resolution automatically. Warning: write.sh does NOT work for folder shares — it writes content but does not register the file in folder metadata, so Obsidian will never see it. The script detects folder shares and refuses with an error. ### Scripts reference ScriptPurposeArgsauth.shGet JWT token—list-shares.shList all shares[kind] [owned_only]list-files.shList files in folder shareread-file.shRead file by path (folder share) read.shRead by doc_id (low-level) [doc_id]upsert-file.shCreate/update file (folder share) write.shWrite by doc_id (doc shares only) delete-file.shDelete file from folder share create-file.shCreate new file (low-level) Bold = recommended for most use cases. All scripts use RELAY_TOKEN env var (or accept token as first arg). ### Authentication All API calls require a Bearer JWT token. Get one via login: curl -s -X POST "$RELAY_CP_URL/v1/auth/login" \\ -H "Content-Type: application/json" \\ -d '{"email": "'$RELAY_EMAIL'", "password": "'$RELAY_PASSWORD'"}' \\ | jq -r '.access_token' Response: { "access_token": "eyJ...", "refresh_token": "...", "token_type": "bearer", "expires_in": 3600 } Use the access_token as Authorization: Bearer header on all subsequent requests. When the token expires (1 hour), refresh it: curl -s -X POST "$RELAY_CP_URL/v1/auth/refresh" \\ -H "Content-Type: application/json" \\ -d '{"refresh_token": "'$REFRESH_TOKEN'"}' ### Listing shares Shares are the access units — each share maps to a document or folder in the Obsidian vault. curl -s "$RELAY_CP_URL/v1/shares" \\ -H "Authorization: Bearer $TOKEN" | jq Response (array): [ { "id": "a1b2c3d4-...", "kind": "doc", "path": "Projects/meeting-notes.md", "visibility": "private", "is_owner": true, "user_role": null, "web_published": false }, { "id": "e5f6g7h8-...", "kind": "folder", "path": "Projects/", "visibility": "private", "is_owner": false, "user_role": "editor" } ] Key fields: id — share UUID, used as share_id in all operations kind — doc (single file) or folder (directory) path — Obsidian vault-relative path user_role — viewer (read-only), editor (read-write), or null (owner) Filter options: ?kind=doc, ?owned_only=true, ?member_only=true, ?skip=0&limit=50. ### Listing files in a folder share scripts/list-files.sh Response: { "doc_id": "e5f6g7h8-...", "files": { "meeting-notes.md": {"doc_id": "abc123-...", "type": "markdown"}, "project-plan.md": {"doc_id": "def456-...", "type": "markdown"} } } Each key is the file's path within the folder. The doc_id field is the document identifier used for content operations. The share_id for content requests is always the folder share's ID. Note: The API response uses id as the field name. This is the same as doc_id — use it wherever doc_id is needed. ### By path (recommended for folder shares) scripts/read-file.sh "Marketing/plan.md" This resolves the path to a doc_id internally and returns: { "doc_id": "abc123-...", "content": "# Marketing Plan\\n\\nContent here...", "format": "text", "path": "Marketing/plan.md" } ### By doc_id (low-level) scripts/read.sh [doc_id] [key] For doc shares, omit doc_id (defaults to share_id). For folder shares, pass the file's doc_id from list-files.sh. ### Folder shares — use upsert-file.sh # Create or update — auto-detects which operation is needed scripts/upsert-file.sh "note.md" "# Updated content" # Pipe content from stdin echo "# Content" | scripts/upsert-file.sh "note.md" - Response includes an operation field: "created" or "updated". ### Doc shares — use write.sh scripts/write.sh "# Updated Notes" write.sh refuses folder shares — if you accidentally pass a folder share_id as doc_id, it detects this and exits with an error directing you to upsert-file.sh. ### Read a specific note by path (most common) # If you know the folder share_id: scripts/read-file.sh "Marketing/docs/plan.md" # If you need to find the share first: scripts/list-shares.sh # find the folder share scripts/read-file.sh "path/to/file.md" ### Create or update a file # Always works, whether the file exists or not scripts/upsert-file.sh "note.md" "# Content" ### Delete a file scripts/delete-file.sh "old-note.md" ### Error codes StatusMeaning400Invalid share_id format401Missing or expired token — re-authenticate403Insufficient permissions (viewer trying to write, or non-member)404Share or file not found (check path spelling, use list-files.sh to verify)422Missing required field (share_id, content)502Relay server unavailable — retry later ### Terminology TermMeaningshare_idUUID of a share (doc or folder). Used for ACL checks in all requests.doc_idUUID of an individual document. For doc shares, equals share_id. For folder shares, each file has its own doc_id.idSame as doc_id — the API response field name. Use interchangeably.file_pathRelative path within a folder share (e.g. "Marketing/plan.md"). ### References references/api.md — full API reference with all endpoints ## Trust - Source: tencent - Verification: Indexed source record - Publisher: venturecrew - Version: 1.1.2 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T13:55:50.901Z - Expires at: 2026-05-06T13:55:50.901Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/evc-team-relay) - [Send to Agent page](https://openagent3.xyz/skills/evc-team-relay/agent) - [JSON manifest](https://openagent3.xyz/skills/evc-team-relay/agent.json) - [Markdown brief](https://openagent3.xyz/skills/evc-team-relay/agent.md) - [Download page](https://openagent3.xyz/downloads/evc-team-relay)