OpenClaw

batchjob-async-job

Use BatchJob HTTP APIs for strict upload validation, precheck, submit, polling, and cancellation. Full-auto file source resolution (file_id/local path/public URL/channel attachment path) with fallback interaction only when source is not readable.

cocovs0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install cocovs/ssy-batchjob-async-job

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

BatchJob Async Job Skill

Use this skill when the user wants to run or manage batch jobs through the BatchJob service.

Required Environment

BATCHJOB_BASE_URL
BATCHJOB_BEARER_TOKEN

All HTTP requests must include:

-H "Authorization: Bearer ${BATCHJOB_BEARER_TOKEN}"
-H "Content-Type: application/json"

API Endpoints

POST /v1/batch/files:upload
POST /v1/batch/jobs:precheck
POST /v1/batch/jobs
GET /v1/batch/jobs/{job_id}
GET /v1/batch/jobs?page=1&page_size=10&status=...
POST /v1/batch/jobs/{job_id}:cancel

Automation Policy (Default)

Always run in full-auto mode.
Do not ask user for file_id first.
Resolve file source from current message/context, then upload automatically when needed.
Ask follow-up questions only when no readable file source can be obtained.
Accepted input file formats for upload: jsonl, csv, xlsx, xls (BatchJob normalizes to internal JSONL).
For jsonl, each line must be either:
- canonical Vertex format (contents + optional generationConfig)
- simple prompt format (prompt + optional aspect_ratio / image_urls, where image_urls must be publicly reachable URLs)
If user gives only model mode after a file message, treat it as confirmation and continue automatically.

Guardrails (Must Follow)

Do not auto-retry by creating a second job unless user explicitly asks.
Do not auto-rewrite dataset format after a terminal failure unless user explicitly asks.
Before upload, auto-normalization is allowed only once for known safe mappings (e.g. simple prompt JSONL -> Vertex JSONL).
Upload failure is terminal for this run: do not continue to precheck/submit when upload fails.
Never submit when row_count <= 0.
Do not fetch or parse output_summary_url automatically; only do it when user asks for detailed failure reason.
After reaching terminal status (completed, failed, partially_failed), stop execution and return summary immediately.

JSO...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/cocovs/ssy-batchjob-async-job
Version: —
Commit: 39e111faf25a40ec72ef5f416d261c38ecfde314
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# BatchJob Async Job Skill

Use this skill when the user wants to run or manage batch jobs through the BatchJob service.

## Required Environment

- `BATCHJOB_BASE_URL`
- `BATCHJOB_BEARER_TOKEN`

All HTTP requests must include:

```bash
-H "Authorization: Bearer ${BATCHJOB_BEARER_TOKEN}"
-H "Content-Type: application/json"
```

## API Endpoints

- `POST /v1/batch/files:upload`
- `POST /v1/batch/jobs:precheck`
- `POST /v1/batch/jobs`
- `GET /v1/batch/jobs/{job_id}`
- `GET /v1/batch/jobs?page=1&page_size=10&status=...`
- `POST /v1/batch/jobs/{job_id}:cancel`

## Automation Policy (Default)

- Always run in full-auto mode.
- Do not ask user for `file_id` first.
- Resolve file source from current message/context, then upload automatically when needed.
- Ask follow-up questions only when no readable file source can be obtained.
- Accepted input file formats for upload: `jsonl`, `csv`, `xlsx`, `xls` (BatchJob normalizes to internal JSONL).
- For `jsonl`, each line must be either:
- canonical Vertex format (`contents` + optional `generationConfig`)
- simple prompt format (`prompt` + optional `aspect_ratio` / `image_urls`, where `image_urls` must be publicly reachable URLs)
- If user gives only `model mode` after a file message, treat it as confirmation and continue automatically.

## Guardrails (Must Follow)

- Do not auto-retry by creating a second job unless user explicitly asks.
- Do not auto-rewrite dataset format after a terminal failure unless user explicitly asks.
- Before upload, auto-normalization is allowed only once for known safe mappings (e.g. simple prompt JSONL -> Vertex JSONL).
- Upload failure is terminal for this run: do not continue to precheck/submit when upload fails.
- Never submit when `row_count <= 0`.
- Do not fetch or parse `output_summary_url` automatically; only do it when user asks for detailed failure reason.
- After reaching terminal status (`completed`, `failed`, `partially_failed`), stop execution and return summary immediately.

## JSO...

搜索