返回顶部
o

ollang

Master skill for the Ollang translation platform. Routes to the right Ollang sub-skill based on intent — upload files, create orders, check status, manage revisions, run QC, browse projects and folders. Use when the user mentions Ollang or wants to perform any translation/captioning/dubbing workflow.

作者: admin | 来源: ClawHub
源自
ClawHub
版本
V 1.0.3
安全检测
已通过
109
下载量
0
收藏
概述
安装方式
版本历史

ollang

# Ollang — Master Skill This is the entry point for all Ollang API operations. Based on the user's intent, delegate to the appropriate sub-skill below. ## Sub-Skills | Sub-Skill | When to Use | |-----------|-------------| | `ollang-health` | User wants to check if the API is up | | `ollang-upload` | User wants to upload a video, audio, document, or VTT file | | `ollang-order-create` | User wants to create a translation, CC, subtitle, or dubbing order | | `ollang-order-get` | User wants to check the status or details of a specific order | | `ollang-orders-list` | User wants to list, search, or filter their orders | | `ollang-order-cancel` | User wants to cancel an order | | `ollang-order-rerun` | User wants to rerun or regenerate an order | | `ollang-revision` | User wants to report an issue or manage revisions on an order | | `ollang-human-review` | User wants to request or cancel human (linguist) review | | `ollang-qc-eval` | User wants to run a quality control evaluation on an order | | `ollang-project` | User wants to list or inspect projects | | `ollang-folder` | User wants to list or find folders | ## Full Workflow A complete end-to-end translation workflow looks like this: ``` 1. Upload file → ollang-upload → returns projectId 2. Create order → ollang-order-create → returns orderId(s) 3. Monitor status → ollang-order-get → poll until "completed" 4. Quality check → ollang-qc-eval → scores + segment analysis 5. Report issues → ollang-revision → create revisions if needed 6. Upgrade to human → ollang-human-review → optional linguist review ``` ## Authentication All endpoints (except health check) require the `X-Api-Key` header. The API key is read from the `OLLANG_API_KEY` environment variable. If the variable is not set, instruct the user to configure it: ```bash export OLLANG_API_KEY=<your-api-key> ``` Get your API key at https://lab.ollang.com. ## API Base URL ``` https://api-integration.ollang.com ``` ## Behavior 1. Identify the user's intent from their message 2. Map it to the correct sub-skill from the table above 3. Read the API key from the `OLLANG_API_KEY` environment variable. If not set, tell the user to set it with: `export OLLANG_API_KEY=<your-api-key>` 4. Execute the operation and present results clearly 5. Suggest logical next steps (e.g., after upload → offer to create an order)

标签

skill ai

通过对话安装

该技能支持在以下平台通过对话安装:

OpenClaw WorkBuddy QClaw Kimi Claude

方式一:安装 SkillHub 和技能

帮我安装 SkillHub 和 ollang-skills-1776018084 技能

方式二:设置 SkillHub 为优先技能安装源

设置 SkillHub 为我的优先技能安装源,然后帮我安装 ollang-skills-1776018084 技能

通过命令行安装

skillhub install ollang-skills-1776018084

下载 Zip 包

⬇ 下载 ollang v1.0.3

文件大小: 18.44 KB | 发布时间: 2026-4-13 11:16

v1.0.3 最新 2026-4-13 11:16
- The .claude/settings.local.json file was removed.
- Updated API key handling: the skill now reads the API key from the OLLANG_API_KEY environment variable instead of asking for it during the session.
- SKILL.md guidance improved to tell users how to set the OLLANG_API_KEY variable if not configured.

Archiver·手机版·闲社网·闲社论坛·羊毛社区· 多链控股集团有限公司 · 苏ICP备2025199260号-1

Powered by Discuz! X5.0   © 2024-2025 闲社网·线报更新论坛·羊毛分享社区·http://xianshe.com

p2p_official_large
返回顶部