Agent skill

Evaluate Auto Implement Eligibility

by warpdotdev in warpdotdev/oz-for-oss

Evaluates whether a triaged GitHub issue is eligible for the factory auto-implement queue.

MITAuto-check passedDevelopment

Install Evaluate Auto Implement Eligibility

skills CLI
$ npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install warpdotdev/oz-for-oss evaluate-auto-implement-eligibility --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/evaluate-auto-implement-eligibility-local .claude/skills/evaluate-auto-implement-eligibility && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
evaluate-auto-implement-eligibility
GitHub stars
313
Token cost
~969 tokens
SKILL.md length
524 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Evaluates whether a triaged GitHub issue is eligible for the factory auto-implement queue.

  • Tasks that involve Issue triage
  • SKILL.md covers Decision rule, Output and Default
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Evaluate Auto Implement Eligibility is an agent skill from warpdotdev/oz-for-oss. Evaluates whether a triaged GitHub issue is eligible for the factory auto-implement queue. Use during issue triage after the primary triage pass is complete.

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Issue triage. It works with GitHub. The repository describes itself as: Workflows and skills to help people and agents collaborate on open-source software with the power of Oz! The licence is MIT.

When your agent uses it

  • Tasks that involve Issue triage

Example prompts

  • “Use the evaluate-auto-implement-eligibility skill to evaluate whether a triaged GitHub issue is eligible for the factory auto-implement queue”
  • “/evaluate-auto-implement-eligibility”

What it can do on your machine

Read from SKILL.md and the folder at commit a2bb45f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Evaluate Auto Implement Eligibility loads about 969 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 524 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~969

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from warpdotdev/oz-for-oss at commit a2bb45f, republished under its MIT licence (© warpdotdev). 524 words, ~969 tokens.

Download SKILL.mdSave it as .claude/skills/evaluate-auto-implement-eligibility/SKILL.md (or your agent's skills folder).
name
evaluate-auto-implement-eligibility
description
Evaluates whether a triaged GitHub issue is eligible for the factory auto-implement queue. Use during issue triage after the primary triage pass is complete.

Factory Auto-Implement Eligibility

Determine whether this issue is a candidate for the factory auto-implement queue. When eligible, the workflow adds the factory-auto-implement label only. It does not assign oz-agent and does not apply the creation-time auto-implement label (that label is reserved for trusted issues labeled at open time, which skip triage entirely). The bar is deliberately high.

Decision rule

All of the following gates must pass. If any gate fails, or if you are uncertain about any gate, the answer is false.

Gate 1: Bug only

The issue describes an observed behavior that is clearly wrong. Enhancements, feature requests, performance improvements, and vague improvement requests are never eligible, even if fully specified.

Gate 2: Visual bugs must be objectively wrong, not a matter of taste

Exclude issues where the desired outcome is a judgment call — e.g. "this button should be a different color", "this spacing feels off", or any report that expresses a personal opinion about appearance. A visual bug is eligible only when the correct state is unambiguous: a missing icon, a broken layout that clearly corrupts the UI, text that is visibly truncated or overlapping, or a rendering glitch with a clear non-rendering root cause. When in doubt, exclude it.

Gate 3: Root cause known with high or medium confidence

The triage investigation must have identified a plausible root cause and relevant code. If the root cause is unknown or speculative, the answer is false — even if reproducibility is high.

Gate 4: Unambiguous definition of done

There is exactly one reasonable interpretation of what "fixed" means. A maintainer reading the issue would agree on the expected outcome without discussion. Exclude anything where the correct fix depends on a product judgment call.

Gate 5: Client-side only

The fix touches only the client-side desktop app. Exclude any issue involving: server or API, authentication, billing, cloud sync, session sharing, telemetry backend, or the Oz platform backend. When in doubt, the answer is false.

Show full SKILL.md (202 more words)Show less
Gate 6: Localized scope

The fix touches one component or subsystem. Exclude issues requiring cross-cutting changes, modifications to shared core primitives, or anything that would move architectural boundaries.

Gate 7: Not security- or data-sensitive

The issue does not touch auth, permissions, billing, or data integrity. The failure mode if the implementation is wrong is recoverable (behavioral glitch, not data loss or a security hole).

Gate 8: Small estimated effort

The fix path is apparent from the issue description and likely touches a small number of files. A confident engineer could complete it in a few hours without needing to understand a large or unfamiliar subsystem.

Output

Add these two fields to triage_result.json:

json
{
  "factory_auto_implement": true,
  "factory_auto_implement_reasoning": "one sentence naming the determining factor"
}

Always populate both fields. When false, factory_auto_implement_reasoning must name the specific gate that failed. When true, briefly state the positive case (e.g. "client-side crash with known root cause, clear fix path, and no follow-up questions needed").

Do not emit the legacy auto_implement / auto_implement_reasoning fields. Do not request oz-agent assignment or the auto-implement label from this skill.

Default

When in doubt, the answer is false. A missed candidate is a minor inefficiency. A false positive queues factory work that should not run, wasting compute and potentially producing an unwanted draft PR.

© warpdotdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/evaluate-auto-implement-eligibility-local of warpdotdev/oz-for-oss.

Open the folder on GitHubat commit a2bb45f

Compare with similar skills

Evaluate Auto Implement Eligibility next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Evaluate Auto Implement Eligibility compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Evaluate Auto Implement Eligibility this skillwarpdotdev/oz-for-oss313—~969Automated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK4.7k—~3.4kAutomated safety check: PassApache-2.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK4.7k—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Official

    Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.

    4.7k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed
  • WinAppSDK Triage Meeting Prep

    microsoft/WindowsAppSDK

    Official

    Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.

    4.7k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

More from warpdotdev/oz-for-oss

All 17 skills in this repo
  • Update Dedupe

    warpdotdev/oz-for-oss

    Update the repo-local dedupe-issue-local companion skill using closed-as-duplicate signals.

    313 GitHub stars~927 tokensUpdated 20 days ago
    Auto-check passed
  • Update PR Review

    warpdotdev/oz-for-oss

    Update the repo-local review-pr-local and review-spec-local companion skills using human feedback left on pull request conversations.

    313 GitHub stars~1.6k tokensUpdated 20 days ago
    Auto-check passed
  • Bootstrap Issue Config

    warpdotdev/oz-for-oss

    Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate .github/issue-triage/config.json and .github/STAKEHOLDERS.

    313 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Update Triage

    warpdotdev/oz-for-oss

    Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments).

    313 GitHub stars~1k tokensUpdated 20 days ago
    Auto-check passed
  • Implement Issue

    warpdotdev/oz-for-oss

    Implement a GitHub issue in this repository by applying the shared implement-specs workflow with Oz-specific issue, spec-context, and summary-file handling.

    313 GitHub stars~2k tokensUpdated 20 days ago
    Auto-check passed
  • Review Spec

    warpdotdev/oz-for-oss

    Review a spec/plan pull request diff and write structured feedback to review.json for the workflow to publish.

    313 GitHub stars~1.9k tokensUpdated 20 days ago
    Auto-check passed

Works with

Categories

Questions about Evaluate Auto Implement Eligibility

What does Evaluate Auto Implement Eligibility do?

Evaluates whether a triaged GitHub issue is eligible for the factory auto-implement queue. Evaluate Auto Implement Eligibility is an agent skill from warpdotdev/oz-for-oss. Evaluates whether a triaged GitHub issue is eligible for the factory auto-implement queue.

When should I use Evaluate Auto Implement Eligibility?

Evaluate Auto Implement Eligibility fits situations like: tasks that involve Issue triage.

How do I install Evaluate Auto Implement Eligibility in Claude Code?

Run `npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a claude-code`. Or copy the skill folder (.agents/skills/evaluate-auto-implement-eligibility-local in warpdotdev/oz-for-oss) into .claude/skills/evaluate-auto-implement-eligibility in your project. Claude Code loads it when a task matches its description.

How do I install Evaluate Auto Implement Eligibility in Codex?

Run `npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a codex`. Or copy the skill folder (.agents/skills/evaluate-auto-implement-eligibility-local in warpdotdev/oz-for-oss) into .agents/skills/evaluate-auto-implement-eligibility in your project. Codex loads it when a task matches its description.

Can I use Evaluate Auto Implement Eligibility in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/evaluate-auto-implement-eligibility, .gemini/skills/evaluate-auto-implement-eligibility, .github/skills/evaluate-auto-implement-eligibility and .opencode/skills/evaluate-auto-implement-eligibility in your project.

What does Evaluate Auto Implement Eligibility need to run?

SKILL.md names no scripts, command-line tools or credentials: Evaluate Auto Implement Eligibility is instructions for the agent only.

Does Evaluate Auto Implement Eligibility access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Evaluate Auto Implement Eligibility safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Evaluate Auto Implement Eligibility use?

Evaluate Auto Implement Eligibility is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Evaluate Auto Implement Eligibility use?

About 969 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Evaluate Auto Implement Eligibility?

Skills that share tags, products or a category with Evaluate Auto Implement Eligibility: Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Evaluate Auto Implement Eligibility?

warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-for-oss, which has 313 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 17, 2026.

Source: warpdotdev/oz-for-oss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.