--- name: ai-task-hub description: AI task hub for image analysis, background removal, speech-to-text, text-to-speech, markdown conversion, and points queries. Default host path is connector-first and result-first; async poll/presentation remain compatibility or asset-delivery follow-up surfaces. version: 3.3.14 metadata: openclaw: skillKey: ai-task-hub emoji: "🧩" homepage: https://gateway.binaryworks.app transport: preferredEntrypoint: /agent/public-bridge/invoke trustedHostEntrypoint: /agent/skill/bridge/invoke requires: bins: - node ---

AI Task Hub

Formerly skill-hub-gateway.

Public package boundary:

• Only orchestrates portal.skill.execute, portal.skill.poll, portal.skill.presentation, portal.account.connect, portal.account.balance, and portal.account.ledger.
• Does not exchange api_key or userToken inside this package.
• Does not handle recharge or payment flows inside this package.
• Optional env hints PUBLIC_BRIDGE_ENTRY_HOST and AI_TASK_HUB_ENTRY_HOST are only host-side entry_host fallbacks, not API secrets, auth tokens, or billing credentials.
• Prefers attachment URLs, and when host runtime explicitly exposes attachment bytes for the current request, forwards only that explicit attachment material through the public bridge before execution.
• When the published skill is invoked directly by a third-party agent runtime, it uses POST /agent/public-bridge/invoke.
• published skill persistence = disabled.
• continuity owner = host_or_private_wrapper.

Data Handling Boundary

• Only forwards attachment bytes that the host runtime explicitly provides for the current request.
• Off-host media transfer is limited to the gateway-controlled host https://gateway-api.binaryworks.app.
• Public upload handoff is limited to POST /agent/public-bridge/upload-file for the same request flow.
• Does not read local paths, scan the local filesystem, or guess files outside explicit host-provided attachment material.
• Does not persist uploaded bytes or credentials to local disk, and does not write skill/config state.
• Host/runtime should obtain user consent before forwarding media and should avoid sending sensitive or regulated data unless the user explicitly approved that transfer.

Read This First

• Do not mix connector lifecycle commands with published skill actions.
• connect / status / invoke / logout are connector lifecycle commands for host/runtime installation state.
• portal.account.connect / portal.skill.execute / portal.skill.poll / portal.skill.presentation / portal.account.balance / portal.account.ledger are the published skill actions.
• Do not treat portal.skill.execute -> portal.skill.poll -> portal.skill.presentation as the default path for every capability. Default behavior must follow the capability delivery mode.
• Public capability inventory below lists only enabled capabilities intentionally advertised to agents. Disabled or internal-only routes may still exist in backend code but are not part of the advertised package surface.

Two Operational Surfaces

• Connector lifecycle commands:

- connect: start or resume browser authorization for one connector installation - status: read whether the connector installation already has continuity - invoke: call one published skill action through the connector runtime - logout: clear continuity for that connector installation

• Published skill actions:

- portal.account.connect: explicit account bind or connection-status check - portal.skill.execute: submit a capability run - portal.skill.poll: poll a submitted run - portal.skill.presentation: fetch rendered outputs for a run - portal.account.balance: read current points balance - portal.account.ledger: read points ledger rows

Public Capability Inventory (Enabled And Available)

• Image analysis:

- human_detect - image_tagging - face-detect - body-keypoints-2d - face-emotion-recognition

• Background removal / cutout / mask:

- person-instance-segmentation - person-semantic-segmentation - concert-cutout - full-body-matting - head-matting - product-cutout

• Audio:

- asr - tts_report

• Document:

- markdown_convert

• Retrieval:

- embeddings - reranker

• Generation:

- image-generation

• Video:

- Video Face Generation

Delivery Mode Guidance

• instant_result

- Default host behavior: prefer a result-first entrypoint and return the final result in the same interaction. - Typical capabilities: tts_report, image analysis, retrieval. - Default product path: use result-first host flow; portal.skill.execute is usually enough.

• aggregated_short_wait

- Default host behavior: prefer a result-first entrypoint with short internal waiting, then fall back to poll only if the short wait does not complete. - Typical capabilities: image-generation. - Default product path: start with result-first host flow; only use portal.skill.poll when the short wait does not complete.

• asset_delivery

- Default host behavior: keep presentation or rendered files as part of the formal result surface. - Typical capabilities: segmentation, matting, cutout. - Default product path: portal.skill.execute -> portal.skill.poll, then portal.skill.presentation when files or rendered outputs are needed.

• long_running

- Default host behavior: treat the capability as an explicit async job and do not promise single-turn completion. - Typical capabilities: asr, markdown_convert, video-face-generation. - Default product path: portal.skill.execute with later portal.skill.poll; use portal.skill.presentation only when that capability later exposes a rendered result surface.

Minimal Architecture Rules

• Default path stays connector-first. Do not invent a host-specific continuity or identity model beside connector/runtime.
• Default path stays result-first. Do not teach every capability as execute -> poll -> presentation.
• portal.skill.poll and portal.skill.presentation are follow-up surfaces, not universal default steps.
• Published skill keeps compatibility and asset-delivery surfaces, but it does not own long-lived continuity.
• Do not ask end users for manual URLs, JSON field names, local paths, or internal bridge details unless they explicitly ask for debugging.

Non-Recommended Patterns

• Do not bypass connector/runtime as the default host product path when hosted connector or local bootstrap is available.
• Do not describe raw published skill actions as if they were the primary UX for every capability.
• Do not add host-specific auth, continuity, or capability-routing rules outside the existing connector/runtime and gateway contracts.
• Do not expose debugging payload structure, bridge layering, or upload choreography to end users unless troubleshooting is explicitly requested.

Official Host Integration

...