task-status

Constraints

• Platform: TikTok only.

• This skill checks an existing task. It does not create a new one.

• The model's final user-facing response should match the user's input language, default English.

• Avoid technical wording in the user-facing reply unless the user explicitly needs details for debugging or to share with a developer.

• Follow shared guidance in ../shared/references/common-rules.md .

• Input: an existing task_id from a previous task request.

• Artifacts must be written under task-status/.artifacts/<run_id>/... .

Workflow

• Collect an existing task id

• Ask for the existing task_id if the user has not provided it yet.

• If the user has a previous task artifact, read the stored task_id from there instead of asking them to restate everything.

• Check status

• Call CreatOK: GET /api/open/skills/tasks/status?task_id=...

• If the user wants to keep waiting, continue polling until the task reaches a terminal state.

• Persist artifacts + respond

• Write:

• outputs/result.json with task_id/status/video_url/raw/error

• outputs/result.md

• If the task succeeded, return the final video_url .

• If the task is still queued or running, explain that clearly and offer to keep checking.

• If the task failed, explain the failure message if available and suggest the next best step.

Thin Client Boundary

• This skill only checks an existing task.

• It should not ask the user to restate the creative brief if a task_id is already available.

• When paired with creatok:video-generate , it should help the user recover from interrupted generation flows. The naming stays generic so it can cover more task types later.