agy-jobs
Agent skill fromkeli-wen/agy-staff
Manage agy staffer background jobs - collect results, check status, cancel, follow-up conversation, and setup. Use when an agy job needs collecting, when the user asks "is the agy job done", "show agy's result", "cancel the agy job", "continue the agy conversation", or "set up agy". This is the orchestrator's skill; the persona skills (staffer/researcher/reviewer/implementer) point here.
How to install agy-jobs
install agy-jobs
# install the agy-staff pack with the skills CLI
npx skills add keli-wen/agy-staff# or add only this skill to Claude Code: copy the folder
opencode-skills/agy-jobs/
# into
~/.claude/skills/agy-jobs/ (all projects)
.claude/skills/agy-jobs/ (one project)
1<!-- Generated from skills/jobs/SKILL.md; run npm run generate:opencode. Do not edit here. -->23# agy jobs45Manage background staffer/research/review/implement jobs. State is per repository in `.agy-staff/` (git-excluded via `.git/info/exclude`). Always invoke the companion from the target repository so AGY attaches that repository as its workspace; `.agy-staff/` is companion state rather than a repository source modification, so do not relocate companion calls to `/tmp` or delete `.agy-staff/`. Only ask runs synchronously.67This file lives at `<plugin-root>/opencode-skills/agy-jobs/SKILL.md`:89```bash10node "<skill-dir>/../../companion/agy-companion.mjs" <command> [args]11```1213## Collect the result1415Default flow: prepare the prompt → dispatch → wait for the final result → validate as needed. While a job is running, do not proactively call `observe`/`status`, read logs or inspect intermediate artifacts. Do not query progress for routine updates or create sleep/observe loops. Observe only when the user explicitly asks for progress; diagnose after receiving a failure or a result requiring intervention.16171. Keep the returned job id. Run `wait <id> --timeout 10m` using the same unsandboxed context as launch (in the background when the host supports background sessions or completion delivery, or directly in the foreground when the host only provides a synchronous shell tool). Use a separate wait for each job; never wait for several jobs serially in one shell.18…
Excerpt shown under the repository's MIT license.
