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.
Evaluates whether a triaged GitHub issue is eligible for the factory auto-implement queue.
$ npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install warpdotdev/oz-for-oss evaluate-auto-implement-eligibility --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "evaluate-auto-implement-eligibility" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/evaluate-auto-implement-eligibility-local into .claude/skills/evaluate-auto-implement-eligibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evaluate-auto-implement-eligibility", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/evaluate-auto-implement-eligibility-localType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install warpdotdev/oz-for-oss evaluate-auto-implement-eligibility --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/evaluate-auto-implement-eligibility-local .agents/skills/evaluate-auto-implement-eligibility && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "evaluate-auto-implement-eligibility" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/evaluate-auto-implement-eligibility-local into .agents/skills/evaluate-auto-implement-eligibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evaluate-auto-implement-eligibility", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install warpdotdev/oz-for-oss evaluate-auto-implement-eligibility --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/evaluate-auto-implement-eligibility-local .cursor/skills/evaluate-auto-implement-eligibility && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "evaluate-auto-implement-eligibility" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/evaluate-auto-implement-eligibility-local into .cursor/skills/evaluate-auto-implement-eligibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evaluate-auto-implement-eligibility", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/warpdotdev/oz-for-oss.git --path .agents/skills/evaluate-auto-implement-eligibility-local--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install warpdotdev/oz-for-oss evaluate-auto-implement-eligibility --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/evaluate-auto-implement-eligibility-local .gemini/skills/evaluate-auto-implement-eligibility && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "evaluate-auto-implement-eligibility" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/evaluate-auto-implement-eligibility-local into .gemini/skills/evaluate-auto-implement-eligibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evaluate-auto-implement-eligibility", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install warpdotdev/oz-for-oss evaluate-auto-implement-eligibilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/evaluate-auto-implement-eligibility-local .github/skills/evaluate-auto-implement-eligibility && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "evaluate-auto-implement-eligibility" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/evaluate-auto-implement-eligibility-local into .github/skills/evaluate-auto-implement-eligibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evaluate-auto-implement-eligibility", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add warpdotdev/oz-for-oss --skill evaluate-auto-implement-eligibility -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install warpdotdev/oz-for-oss evaluate-auto-implement-eligibility --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/evaluate-auto-implement-eligibility-local .opencode/skills/evaluate-auto-implement-eligibility && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "evaluate-auto-implement-eligibility" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/evaluate-auto-implement-eligibility-local into .opencode/skills/evaluate-auto-implement-eligibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evaluate-auto-implement-eligibility", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
evaluate-auto-implement-eligibilityEvaluates 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. 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.
Read from SKILL.md and the folder at commit a2bb45f. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from warpdotdev/oz-for-oss at commit a2bb45f, republished under its MIT licence (© warpdotdev). 524 words, ~969 tokens.
.claude/skills/evaluate-auto-implement-eligibility/SKILL.md (or your agent's skills folder).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.
All of the following gates must pass. If any gate fails, or if you are
uncertain about any gate, the answer is false.
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.
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.
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.
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.
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.
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.
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).
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.
Add these two fields to triage_result.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.
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
Just SKILL.md in .agents/skills/evaluate-auto-implement-eligibility-local of warpdotdev/oz-for-oss.
Open the folder on GitHubat commit a2bb45f
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Evaluate Auto Implement Eligibility this skillwarpdotdev/oz-for-oss | 313 | — | ~969 | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK | 4.7k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK | 4.7k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 |
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
microsoft/WindowsAppSDK
Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
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.
microsoft/WindowsAppSDK
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
a2ui-project/a2ui
Automates the triage of GitHub issues in the A2UI repository.
warpdotdev/oz-for-oss
Update the repo-local dedupe-issue-local companion skill using closed-as-duplicate signals.
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.
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.
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).
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.
warpdotdev/oz-for-oss
Review a spec/plan pull request diff and write structured feedback to review.json for the workflow to publish.
Works with
Categories
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.
Evaluate Auto Implement Eligibility fits situations like: tasks that involve Issue triage.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Evaluate Auto Implement Eligibility is instructions for the agent only.
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.
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.
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.
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.
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.
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.