The general-purpose persona: a clean entry point for tasks that none of the specialists fit. Its prompt template is deliberately minimal — the task text, the environment (cwd, branch, date), and the safety guardrails, nothing else. No role framing, no rules, no output format: the task defines its own output, and no unrelated template context can pull the run off course.
Prefer a specialist when one fits: researcher for surveys and deep dives, reviewer for second opinions on code or plans, implementer for edits to the working tree, ask for a cheap one-shot question.
staffer is also the route to agy-native tools no specialist covers — notably image generation: agy ships a generate_image tool (verified on v1.1.15; a 1024×1024 PNG in ~30s). Name the output path in the task, e.g. staffer --prompt "generate a pixel-art robot mascot, save it as assets/mascot.png".
Locating the companion
This skill file lives at <plugin-root>/opencode-skills/agy-staffer/SKILL.md; resolve the companion path relative to this skill directory:
node "<skill-dir>/../../companion/agy-companion.mjs" staffer [flags] --prompt "task"
Pass the user's task text verbatim via --prompt; use --prompt-file <path> or --stdin for long text.
[!IMPORTANT] Run this command unsandboxed — agy needs a localhost port and its OAuth token file, which harness sandboxes hide. In Codex, request escalated permissions for the command. Details:
../agy-jobs/references/troubleshooting.md.
Collecting the result
The command returns a job id. Read ../agy-jobs/SKILL.md for result collection and recovery: dispatch, wait for the final result, then validate as needed. Do not proactively observe progress, read logs or inspect intermediate artifacts while running. Observe only when the user explicitly asks for progress; diagnose a failure or a result requiring intervention under the jobs protocol.
Flags (all optional)
--prompt <text>/--prompt-file <path>/--stdin— the task, from exactly one of these three sources. Use file/stdin for long prompts instead of shell quoting.--model <id>or--effort low|medium|high— default model isgemini-3.8-flash-medium.--restricted/--unrestricted— permission profile; staffer defaults to unrestricted like the other tool-using personas,--restrictedis the opt-in hardening path.--continue(or--conversation <id>),--timeout <dur>(default 60m, maximum 120m hard execution limit).
Rules
- Pass the user's task through verbatim. Because the template imposes no output format, state the desired format in the task text when the caller needs a specific one.
- Pass the user's explicit authorizations through verbatim. The template default-denies costly or irreversible side effects (commits/pushes, deleting files outside the workspace, side-effectful network calls, paid-quota commands); that default opens only when the task itself asks for the operation.
- A general task may legitimately edit files. The companion reports any working-tree delta with the result — inspect it (
git diff) and confirm it is what the task asked for before building on it. - For errors and recovery, follow
../agy-jobs/SKILL.md.
For an existing conversation, --continue / --conversation <id> inherit its recorded model and permission profile unless explicitly overridden. The unrestricted defaults above apply to new tasks.
Host compatibility
When this skill or its referenced instructions require a tool that the current environment does not provide, use available capabilities to achieve an equivalent result. Adapt only the tool-specific execution method; preserve the task goal, authorization requirements, explicit confirmation steps, result delivery, and stopping conditions.
If an equivalent result cannot be achieved, or you cannot establish that an alternative is equivalent, explain the missing capability and its impact, and ask the user for help. Do not silently skip requirements or bypass the environment's restrictions.