[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PMP9GMSAP0ACB23Q82N0R":3,"skill-same:01M75PMP9GMSAP0ACB23Q82N0R":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M75PMP9GMSAP0ACB23Q82N0R","tms",null,"Manage downloads via Telegram Media Server (TMS) REST API — add by URL (video\u002Fmagnet\u002Ftorrent), list, delete, search torrents.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnikitadmitryuk\u002Ftms\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: tms\nversion: \"1.0.6\"\ndescription: Manage downloads via Telegram Media Server (TMS) REST API — add by URL (video\u002Fmagnet\u002Ftorrent), list, delete, search torrents.\nmetadata:\n  {\"openclaw\":{\"requires\":{\"env\":[]},\"primaryEnv\":\"TMS_API_URL\"}}\n---\n\n# TMS (Telegram Media Server) API skill\n\nUse this skill when the user wants to add downloads, check download status, stop a download, or search for torrents via the TMS backend. All requests go to the TMS REST API.\n\n**How to use:** This skill does not add a \"tms\" command. The agent must make HTTP requests (GET\u002FPOST\u002FDELETE) to the TMS endpoints. The **full API contract** (paths, request\u002Fresponse schemas, examples) is included in this document below — no need to fetch any URL to get the API spec. Use the OpenAPI spec (inline) section to build and invoke API calls.\n\n## Base URL and authentication\n\n- **Base URL:** Use env `TMS_API_URL` if set; otherwise, when TMS and OpenClaw run on the **same host**, use **`http:\u002F\u002F127.0.0.1:8080`** (TMS default API listen). Do not add a trailing slash. All endpoint paths in the spec use the prefix `\u002Fapi\u002Fv1` — e.g. `GET \u002Fhealth` means **`GET {BaseURL}\u002Fapi\u002Fv1\u002Fhealth`**.\n- **Authentication:** Optional. When TMS and OpenClaw run on the same host, TMS accepts requests from localhost without a key — `TMS_API_KEY` can be omitted. When OpenClaw runs on another host (or you want auth), set `TMS_API_KEY` and send every API request with either `Authorization: Bearer \u003CTMS_API_KEY>` or header `X-API-Key: \u003CTMS_API_KEY>`.\n\n## Operations (summary)\n\n1. **Health check** — `GET {BaseURL}\u002Fapi\u002Fv1\u002Fhealth` — returns `{\"status\":\"ok\"}` if the API is up.\n2. **List downloads** — `GET {BaseURL}\u002Fapi\u002Fv1\u002Fdownloads` — returns a JSON array of downloads with `id`, `title`, `status` (queued, downloading, converting, completed, failed, stopped), `progress`, `conversion_progress`, `error` (if failed), `position_in_queue` (if queued). Snapshot is best-effort.\n3. **Add download** — `POST {BaseURL}\u002Fapi\u002Fv1\u002Fdownloads` with JSON body `{\"url\": \"\u003Curl>\", \"title\": \"\u003Coptional>\"}`. URL can be: video URL (yt-dlp), magnet link (`magnet:...`), .torrent file URL, or (when Prowlarr is configured on TMS) Prowlarr proxy download URL. Prefer **magnet** from search results when adding a torrent. Optional `title` overrides the display name. Response: `201` with `{\"id\": \u003Cnumber>, \"title\": \"\u003Cstring>\"}`. Use `id` for delete or status.\n4. **Delete download** — `DELETE {BaseURL}\u002Fapi\u002Fv1\u002Fdownloads\u002F{id}` — stops and removes the download. Response: `204` no body. `id` is the numeric id from the add response or list.\n5. **Search torrents** — `GET {BaseURL}\u002Fapi\u002Fv1\u002Fsearch?q=\u003Cquery>&limit=20&quality=1080` — requires Prowlarr configured on TMS. `q` is required; `limit` (1–100, default 20) and `quality` (optional filter) may be used. Returns array of `{title, size, magnet, torrent_url, indexer_name, peers}`. When adding from search, use the **magnet** field in POST \u002Fdownloads (or torrent_url); you may pass `title` from the result.\n\nDetailed request\u002Fresponse schemas and status codes are in the **OpenAPI spec (inline)** below.\n\n## OpenAPI spec (inline)\n\nThe following YAML is the full TMS API contract. Paths are relative to base path `\u002Fapi\u002Fv1`; full URL = `{BaseURL}` + path (e.g. `{BaseURL}\u002Fapi\u002Fv1\u002Fhealth`). Inline spec is copied from `internal\u002Fapi\u002Fopenapi\u002Fopenapi-llm.yaml`; keep in sync when API changes.\n\n```yaml\nopenapi: 3.1.0\ninfo:\n  title: TMS REST API\n  description: |\n    Telegram Media Server API. Use to add downloads by URL (video\u002Fmagnet\u002Ftorrent), list downloads with status,\n    delete a download, or search torrents. All endpoints require Authorization Bearer or X-API-Key.\n  version: 1.0.0\n\nservers:\n  - url: \u002Fapi\u002Fv1\n    description: Base path (prepend your TMS base URL, e.g. from TMS_API_URL)\n\ntags:\n  - name: health\n  - name: downloads\n  - name: search\n\nsecurity:\n  - BearerAuth: []\n  - ApiKeyHeader: []\n\npaths:\n  \u002Fhealth:\n    get:\n      tags: [health]\n      summary: Check API availability\n      description: Call to verify TMS API is reachable. Returns 200 and {\"status\":\"ok\"}. No auth required for this endpoint in some setups; if 401, send Bearer or X-API-Key.\n      operationId: getHealth\n      responses:\n        '200':\n          description: OK\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FHealthResponse' }\n\n  \u002Fdownloads:\n    get:\n      tags: [downloads]\n      summary: List downloads\n      description: |\n        Call to get current downloads (queued, active, completed). Returns array of items with id, title, status (queued|downloading|converting|completed|failed|stopped), progress (0-100), conversion_progress, error (if failed), position_in_queue (if queued). Snapshot is best-effort.\n      operationId: listDownloads\n      responses:\n        '200':\n          description: Array of download items\n          content:\n            application\u002Fjson:\n              schema:\n                type: array\n                items: { $ref: '#\u002Fcomponents\u002Fschemas\u002FDownloadItem' }\n    post:\n      tags: [downloads]\n      summary: Create a download\n      description: |\n        Call to add a download. Body: JSON with \"url\" (required) and optional \"title\" (display name, e.g. from search). URL can be: video URL (yt-dlp), magnet link (magnet:...), .torrent file URL, or Prowlarr proxy download URL when Prowlarr is configured. Prefer magnet from search results. Response gives id (number) and title (string). Use this id for DELETE \u002Fdownloads\u002F{id}.\n      operationId: addDownload\n      requestBody:\n        required: true\n        content:\n          application\u002Fjson:\n            schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FAddDownloadRequest' }\n            example: { url: \"magnet:?xt=urn:btih:abc123\" }\n      responses:\n        '201':\n          description: Download created\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FAddDownloadResponse' }\n        '400':\n          description: Missing url or invalid URL\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '401':\n          description: Unauthorized\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '500':\n          description: Server error\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n\n  \u002Fdownloads\u002F{id}:\n    delete:\n      tags: [downloads]\n      summary: Stop and remove a download\n      description: Call to stop the download with given id and remove it. id is the numeric id returned by POST \u002Fdownloads. Returns 204 with no body on success.\n      operationId: deleteDownload\n      parameters:\n        - name: id\n          in: path\n          required: true\n          schema: { type: integer, minimum: 1 }\n      responses:\n        '204':\n          description: Download stopped\n        '400':\n          description: Invalid id (not a number)\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '401':\n          description: Unauthorized\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '500':\n          description: Server error\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n\n  \u002Fsearch:\n    get:\n      tags: [search]\n      summary: Search torrents\n      description: |\n        Call to search torrents (requires Prowlarr configured). Query param \"q\" (required): search string. \"limit\" (optional, 1-100, default 20): max results. \"quality\" (optional): filter by substring in release title (e.g. 1080). Returns array of objects with title, size, magnet, torrent_url, indexer_name, peers. When adding a download, prefer the magnet field in POST \u002Fdownloads; you may also pass title from the result.\n      operationId: searchTorrents\n      parameters:\n        - name: q\n          in: query\n          required: true\n          schema: { type: string }\n        - name: limit\n          in: query\n          schema: { type: integer, minimum: 1, maximum: 100, default: 20 }\n        - name: quality\n          in: query\n          schema: { type: string }\n      responses:\n        '200':\n          description: Array of search results\n          content:\n            application\u002Fjson:\n              schema:\n                type: array\n                items: { $ref: '#\u002Fcomponents\u002Fschemas\u002FSearchResultItem' }\n        '400':\n          description: Missing q\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '401':\n          description: Unauthorized\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '503':\n          description: Search not configured or Prowlarr error\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n\ncomponents:\n  securitySchemes:\n    BearerAuth:\n      type: http\n      scheme: bearer\n      bearerFormat: API Key\n    ApiKeyHeader:\n      type: apiKey\n      in: header\n      name: X-API-Key\n\n  schemas:\n    HealthResponse:\n      type: object\n      required: [status]\n      properties:\n        status: { type: string, example: \"ok\" }\n\n    DownloadItem:\n      type: object\n      properties:\n        id: { type: integer }\n        title: { type: string }\n        status: { type: string, enum: [queued, downloading, converting, completed, failed, stopped] }\n        progress: { type: integer, minimum: 0, maximum: 100 }\n        conversion_progress: { type: integer, minimum: 0, maximum: 100 }\n        error: { type: string }\n        position_in_queue: { type: integer }\n\n    AddDownloadRequest:\n      type: object\n      required: [url]\n      properties:\n        url: { type: string }\n        title: { type: string, description: Optional display name e.g. from search result }\n\n    AddDownloadResponse:\n      type: object\n      properties:\n        id: { type: integer }\n        title: { type: string }\n\n    SearchResultItem:\n      type: object\n      properties:\n        title: { type: string }\n        size: { type: integer }\n        magnet: { type: string }\n        torrent_url: { type: string }\n        indexer_name: { type: string }\n        peers: { type: integer }\n\n    ErrorResponse:\n      type: object\n      required: [error]\n      properties:\n        error: { type: string }\n```\n\n## Webhook (optional)\n\nIf TMS is configured with `TMS_WEBHOOK_URL` pointing to an endpoint OpenClaw can receive, TMS will POST to that URL when a download completes, fails, or is stopped. Body: `id`, `title`, `status` (completed|failed|stopped), `error` (if failed), `event_id` (UUID). When `TMS_WEBHOOK_TOKEN` is set in TMS config, TMS sends `Authorization: Bearer \u003CTMS_WEBHOOK_TOKEN>` (required for OpenClaw gateway hooks). Delivery is best-effort (no guaranteed delivery). Use this to notify the user in chat when a download finishes.\n","# TMS (Telegram Media Server) API skill\n\nUse this skill when the user wants to add downloads, check download status, stop a download, or search for torrents via the TMS backend. All requests go to the TMS REST API.\n\n**How to use:** This skill does not add a \"tms\" command. The agent must make HTTP requests (GET\u002FPOST\u002FDELETE) to the TMS endpoints. The **full API contract** (paths, request\u002Fresponse schemas, examples) is included in this document below — no need to fetch any URL to get the API spec. Use the OpenAPI spec (inline) section to build and invoke API calls.\n\n## Base URL and authentication\n\n- **Base URL:** Use env `TMS_API_URL` if set; otherwise, when TMS and OpenClaw run on the **same host**, use **`http:\u002F\u002F127.0.0.1:8080`** (TMS default API listen). Do not add a trailing slash. All endpoint paths in the spec use the prefix `\u002Fapi\u002Fv1` — e.g. `GET \u002Fhealth` means **`GET {BaseURL}\u002Fapi\u002Fv1\u002Fhealth`**.\n- **Authentication:** Optional. When TMS and OpenClaw run on the same host, TMS accepts requests from localhost without a key — `TMS_API_KEY` can be omitted. When OpenClaw runs on another host (or you want auth), set `TMS_API_KEY` and send every API request with either `Authorization: Bearer \u003CTMS_API_KEY>` or header `X-API-Key: \u003CTMS_API_KEY>`.\n\n## Operations (summary)\n\n1. **Health check** — `GET {BaseURL}\u002Fapi\u002Fv1\u002Fhealth` — returns `{\"status\":\"ok\"}` if the API is up.\n2. **List downloads** — `GET {BaseURL}\u002Fapi\u002Fv1\u002Fdownloads` — returns a JSON array of downloads with `id`, `title`, `status` (queued, downloading, converting, completed, failed, stopped), `progress`, `conversion_progress`, `error` (if failed), `position_in_queue` (if queued). Snapshot is best-effort.\n3. **Add download** — `POST {BaseURL}\u002Fapi\u002Fv1\u002Fdownloads` with JSON body `{\"url\": \"\u003Curl>\", \"title\": \"\u003Coptional>\"}`. URL can be: video URL (yt-dlp), magnet link (`magnet:...`), .torrent file URL, or (when Prowlarr is configured on TMS) Prowlarr proxy download URL. Prefer **magnet** from search results when adding a torrent. Optional `title` overrides the display name. Response: `201` with `{\"id\": \u003Cnumber>, \"title\": \"\u003Cstring>\"}`. Use `id` for delete or status.\n4. **Delete download** — `DELETE {BaseURL}\u002Fapi\u002Fv1\u002Fdownloads\u002F{id}` — stops and removes the download. Response: `204` no body. `id` is the numeric id from the add response or list.\n5. **Search torrents** — `GET {BaseURL}\u002Fapi\u002Fv1\u002Fsearch?q=\u003Cquery>&limit=20&quality=1080` — requires Prowlarr configured on TMS. `q` is required; `limit` (1–100, default 20) and `quality` (optional filter) may be used. Returns array of `{title, size, magnet, torrent_url, indexer_name, peers}`. When adding from search, use the **magnet** field in POST \u002Fdownloads (or torrent_url); you may pass `title` from the result.\n\nDetailed request\u002Fresponse schemas and status codes are in the **OpenAPI spec (inline)** below.\n\n## OpenAPI spec (inline)\n\nThe following YAML is the full TMS API contract. Paths are relative to base path `\u002Fapi\u002Fv1`; full URL = `{BaseURL}` + path (e.g. `{BaseURL}\u002Fapi\u002Fv1\u002Fhealth`). Inline spec is copied from `internal\u002Fapi\u002Fopenapi\u002Fopenapi-llm.yaml`; keep in sync when API changes.\n\n```yaml\nopenapi: 3.1.0\ninfo:\n  title: TMS REST API\n  description: |\n    Telegram Media Server API. Use to add downloads by URL (video\u002Fmagnet\u002Ftorrent), list downloads with status,\n    delete a download, or search torrents. All endpoints require Authorization Bearer or X-API-Key.\n  version: 1.0.0\n\nservers:\n  - url: \u002Fapi\u002Fv1\n    description: Base path (prepend your TMS base URL, e.g. from TMS_API_URL)\n\ntags:\n  - name: health\n  - name: downloads\n  - name: search\n\nsecurity:\n  - BearerAuth: []\n  - ApiKeyHeader: []\n\npaths:\n  \u002Fhealth:\n    get:\n      tags: [health]\n      summary: Check API availability\n      description: Call to verify TMS API is reachable. Returns 200 and {\"status\":\"ok\"}. No auth required for this endpoint in some setups; if 401, send Bearer or X-API-Key.\n      operationId: getHealth\n      responses:\n        '200':\n          description: OK\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FHealthResponse' }\n\n  \u002Fdownloads:\n    get:\n      tags: [downloads]\n      summary: List downloads\n      description: |\n        Call to get current downloads (queued, active, completed). Returns array of items with id, title, status (queued|downloading|converting|completed|failed|stopped), progress (0-100), conversion_progress, error (if failed), position_in_queue (if queued). Snapshot is best-effort.\n      operationId: listDownloads\n      responses:\n        '200':\n          description: Array of download items\n          content:\n            application\u002Fjson:\n              schema:\n                type: array\n                items: { $ref: '#\u002Fcomponents\u002Fschemas\u002FDownloadItem' }\n    post:\n      tags: [downloads]\n      summary: Create a download\n      description: |\n        Call to add a download. Body: JSON with \"url\" (required) and optional \"title\" (display name, e.g. from search). URL can be: video URL (yt-dlp), magnet link (magnet:...), .torrent file URL, or Prowlarr proxy download URL when Prowlarr is configured. Prefer magnet from search results. Response gives id (number) and title (string). Use this id for DELETE \u002Fdownloads\u002F{id}.\n      operationId: addDownload\n      requestBody:\n        required: true\n        content:\n          application\u002Fjson:\n            schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FAddDownloadRequest' }\n            example: { url: \"magnet:?xt=urn:btih:abc123\" }\n      responses:\n        '201':\n          description: Download created\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FAddDownloadResponse' }\n        '400':\n          description: Missing url or invalid URL\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '401':\n          description: Unauthorized\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '500':\n          description: Server error\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n\n  \u002Fdownloads\u002F{id}:\n    delete:\n      tags: [downloads]\n      summary: Stop and remove a download\n      description: Call to stop the download with given id and remove it. id is the numeric id returned by POST \u002Fdownloads. Returns 204 with no body on success.\n      operationId: deleteDownload\n      parameters:\n        - name: id\n          in: path\n          required: true\n          schema: { type: integer, minimum: 1 }\n      responses:\n        '204':\n          description: Download stopped\n        '400':\n          description: Invalid id (not a number)\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '401':\n          description: Unauthorized\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '500':\n          description: Server error\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n\n  \u002Fsearch:\n    get:\n      tags: [search]\n      summary: Search torrents\n      description: |\n        Call to search torrents (requires Prowlarr configured). Query param \"q\" (required): search string. \"limit\" (optional, 1-100, default 20): max results. \"quality\" (optional): filter by substring in release title (e.g. 1080). Returns array of objects with title, size, magnet, torrent_url, indexer_name, peers. When adding a download, prefer the magnet field in POST \u002Fdownloads; you may also pass title from the result.\n      operationId: searchTorrents\n      parameters:\n        - name: q\n          in: query\n          required: true\n          schema: { type: string }\n        - name: limit\n          in: query\n          schema: { type: integer, minimum: 1, maximum: 100, default: 20 }\n        - name: quality\n          in: query\n          schema: { type: string }\n      responses:\n        '200':\n          description: Array of search results\n          content:\n            application\u002Fjson:\n              schema:\n                type: array\n                items: { $ref: '#\u002Fcomponents\u002Fschemas\u002FSearchResultItem' }\n        '400':\n          description: Missing q\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '401':\n          description: Unauthorized\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n        '503':\n          description: Search not configured or Prowlarr error\n          content:\n            application\u002Fjson:\n              schema: { $ref: '#\u002Fcomponents\u002Fschemas\u002FErrorResponse' }\n\ncomponents:\n  securitySchemes:\n    BearerAuth:\n      type: http\n      scheme: bearer\n      bearerFormat: API Key\n    ApiKeyHeader:\n      type: apiKey\n      in: header\n      name: X-API-Key\n\n  schemas:\n    HealthResponse:\n      type: object\n      required: [status]\n      properties:\n        status: { type: string, example: \"ok\" }\n\n    DownloadItem:\n      type: object\n      properties:\n        id: { type: integer }\n        title: { type: string }\n        status: { type: string, enum: [queued, downloading, converting, completed, failed, stopped] }\n        progress: { type: integer, minimum: 0, maximum: 100 }\n        conversion_progress: { type: integer, minimum: 0, maximum: 100 }\n        error: { type: string }\n        position_in_queue: { type: integer }\n\n    AddDownloadRequest:\n      type: object\n      required: [url]\n      properties:\n        url: { type: string }\n        title: { type: string, description: Optional display name e.g. from search result }\n\n    AddDownloadResponse:\n      type: object\n      properties:\n        id: { type: integer }\n        title: { type: string }\n\n    SearchResultItem:\n      type: object\n      properties:\n        title: { type: string }\n        size: { type: integer }\n        magnet: { type: string }\n        torrent_url: { type: string }\n        indexer_name: { type: string }\n        peers: { type: integer }\n\n    ErrorResponse:\n      type: object\n      required: [error]\n      properties:\n        error: { type: string }\n```\n\n## Webhook (optional)\n\nIf TMS is configured with `TMS_WEBHOOK_URL` pointing to an endpoint OpenClaw can receive, TMS will POST to that URL when a download completes, fails, or is stopped. Body: `id`, `title`, `status` (completed|failed|stopped), `error` (if failed), `event_id` (UUID). When `TMS_WEBHOOK_TOKEN` is set in TMS config, TMS sends `Authorization: Bearer \u003CTMS_WEBHOOK_TOKEN>` (required for OpenClaw gateway hooks). Delivery is best-effort (no guaranteed delivery). Use this to notify the user in chat when a download finishes.\n",{"name":5,"version":24,"metadata":25,"description":7},"1.0.6",{"openclaw":26},{"requires":27,"primaryEnv":29},{"env":28},[],"TMS_API_URL","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fnikitadmitryuk\u002Ftms",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill tms",{"tool":45,"command":46},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill tms",{"tool":48,"command":49},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill tms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnikitadmitryuk\u002Ftms\u002FSKILL.md",true,[],[54,62,69,76,83,90],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":61},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":61},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":61},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":61},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":61},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":61},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]