AF gemini-worker
Run Gemini CLI as a headless worker agent for long-running or parallelizable tasks. Use when: (1) Anthropic API is overloaded/unavailable (529 errors) and you need a fallback worker, (2) spawning parallel analysis jobs that benefit from Gemini's 1M context window, (3) running validation, deep research, or code analysis without blocking the main agent, (4) any task where `gemini -p "..." --yolo --include-directories ...` is the right pattern. NOT for: interactive sessions, tasks requiring OpenClaw tools (web_search, memory, cron), or tasks needing the full agent loop.
As a process F 39/100 · Will not run — References files that are not bundled: scripts/gemini-run.ps1
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/gemini-run.ps1 - note
frontmatter-keyunknown frontmatter key "bins" - note
frontmatter-keyunknown frontmatter key "requires" - note
frontmatter-keyunknown frontmatter key "install"
Process rating: all ten parameters 39/100
- 0Tools and files. 1 referenced file(s) missing: scripts/gemini-run.ps1
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 10 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1064 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 573: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.