SkillAgentSearch skills...

yao-job

Background job management — start, monitor, wait, stop long-running commands. ALWAYS invoke this skill when the user asks to run background tasks, check job status, read job output, or manage long-running commands.

Install / Use

npx skills add YaoApp/yao --skill yao-job

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Category

Operations

Supported Platforms

Universal

Tags

Our assessment of yao-job

yao-job scores 92/100 on our quality scale, 216th of 747 Operations skills we index (top 29%).

Its SKILL.md is 4.1 KB long, well organised into 15 sections with 6 code examples: a solid amount of guidance for an agent.

With 8,101 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
17/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so yao-job is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

yao-job compared with similar skills

All 4 of these similar skills score higher than yao-job; compare them before choosing.

SkillScoreStarsUpdatedFormat
yao-job (this skill)by YaoApp928.1ktodaySKILL.md
algorithmic-artby anthropics100177.9k16d agoSKILL.md
pptxby anthropics100177.9k16d agoSKILL.md
designby nextlevelbuilder100133.6k5d agoSKILL.md
ui-ux-pro-maxby nextlevelbuilder100133.6k5d agoSKILL.md

Frequently asked questions

How do I install yao-job?
Run npx skills add YaoApp/yao --skill yao-job. The install tabs above show the steps for each supported agent.
Which AI agents does yao-job work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is yao-job safe to use?
It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is yao-job still maintained?
The repository was last updated today, so yao-job is actively maintained.

name: yao-job description: "Background job management — start, monitor, wait, stop long-running commands. ALWAYS invoke this skill when the user asks to run background tasks, check job status, read job output, or manage long-running commands."

Background Jobs

Tools

  • yao_job_start — Start a command. background false (default) blocks until done and returns output_tail; background true returns job_id immediately.
  • yao_job_list — List jobs. Supports --status filter and --limit/--offset pagination.
  • yao_job_get — Get full details for a job (or daemon by ID).
  • yao_job_output — Read process output (works for both job and daemon IDs).
  • yao_job_wait — Block until a background job finishes or timeout expires. Jobs only, not daemons.
  • yao_job_stop — Kill a running job.

Parameters

yao_job_start

| Param | Required | Default | Description | |-------|----------|---------|-------------| | command | yes | — | Shell command to execute | | description | yes | — | Concise 5–10 word summary | | background | no | false | true returns immediately; false blocks until done | | args | no | — | Additional arguments (rarely needed; prefer inline in command) | | working_dir | no | workspace | Working directory | | max_duration_ms | no | — | Kill the job after this many milliseconds |

yao_job_list

| Param | Default | Description | |-------|---------|-------------| | status | all | Filter: running, stopping, completed, failed, cancelled, all | | limit | 20 | Max items per page | | offset | 0 | Skip first N items |

yao_job_output

| Param | Required | Description | |-------|----------|-------------| | job_id | yes | Job or daemon ID | | offset | no | Byte offset to read from (0 = beginning) |

Output read behavior:

  • Returns all available content from offset in a single read (no limit parameter).
  • Ring buffer caps at 10 MB; older content beyond this is discarded.
  • When content has been discarded, lossy=true in the response.
  • size = total bytes the process has produced; offset = earliest readable byte position.
  • Example: a 20 MB output has size=20000000, offset≈10000000, lossy=true — the first ~10 MB was discarded.

yao_job_wait

| Param | Required | Default | Description | |-------|----------|---------|-------------| | job_id | yes | — | Job ID | | timeout_ms | no | 60000 | Timeout in milliseconds |

Response Fields

All responses are JSON. Job objects contain:

id, kind, session_id, status, description, background,
command, command_argv, command_line, pid, pgid, user,
started_at, finished_at, duration_ms, exit_code, signal, detail, seq

Foreground start (background=false)

Returns the job object plus output_tail (≤4KB tail of stdout+stderr):

{ "id": "job_...", "status": "completed", "exit_code": 0, ..., "output_tail": "hello world\n" }

List (paginated)

{ "jobs": [...], "total": 130, "offset": 0, "limit": 20, "has_more": true }

Wait

{ "job": { ... }, "timed_out": false }

Stop (already terminal)

{ "job": { ... }, "detail": "already in terminal state (failed); no action taken" }

Errors

Structured JSON with code and message:

{ "error": { "code": "invalid_argument", "message": "job_id is required" } }

Codes: invalid_argument, not_found, internal.

Usage Rules

  1. Use background true (not bare --background) for commands expected to run longer than 30 seconds.
  2. Always provide a description.
  3. Foreground is default — the result and output come back in one call.
  4. Monitor background output with yao_job_output to check progress.
  5. Use yao_job_wait to block until a background job completes rather than polling.

BackgroundJobReceipt

When a background job finishes, the system delivers a <BackgroundJobReceipt> XML message. Upon receiving it:

  1. Review the status, exit_code, cause, and output_tail.
  2. If status=failed, investigate and take corrective action.
  3. If status=completed, acknowledge and continue the task.

Related Skills

View on GitHub
GitHub Stars8.1k
CategoryOperations
Updated15h ago
Forks721

Languages

Go

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium