swe-bench
Run SWE-bench instances with an OpenSquilla agent inside the official Docker images. Trigger when the user wants to run/solve/evaluate a SWE-bench instance (e.g. 'run django__django-16429', 'test OpenSquilla on SWE-bench', '跑一道 SWE-bench 题'), benchmark the agent on SWE-bench_Verified or SWE-bench_Multilingual, or check whether a generated patch resolves an instance. Optional dependency — install via `pip install opensquilla[swebench]`; also needs the docker CLI and an OPENROUTER_API_KEY.
Profile →npx skills add opensquilla/opensquilla --skill swe-bench --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# swe-bench Run a SWE-bench instance end-to-end: ensure the instance's Docker image is available (pull from Docker Hub if missing), start a container, run an OpenSquilla agent against the issue, collect the patch, and optionally run the official evaluation. ## Prerequisites — guide the user, don't dead-end SWE-bench mode runs the official evaluation images, so it needs the **Docker CLI**. Docker is NOT a hard gate on this skill: if it is missing, the `opensquilla swebench` command prints the exact install command for the user's OS and exits. When that happens, relay the install guidance to the user ("SWE-bench needs Docker — install it with `...`, then I can run this") instead of saying the task is impossible. Also mention that solving a **real-repository** coding task (not a benchmark instance) does NOT need Docker — that is what the `code-task` skill is for. ## Commands Solve one instance (auto-pulls the image when missing): ``` opensquilla swebench solve <instance_id> --dataset verified --json ``` - `--dataset` accepts `verified`, `multilingual`, or a full HuggingFace dataset name. - Add `--evaluate` to run the official harness afterwards and report whether the patch actually re
- Prerequisites — guide the user, don't dead-end
- Commands
- Reading the result
- What to tell the user
- Constraints
What does the swe-bench skill do?
Run SWE-bench instances with an OpenSquilla agent inside the official Docker images. Trigger when the user wants to run/solve/evaluate a SWE-bench instance (e.g. 'run django__django-16429', 'test OpenSquilla on SWE-bench', '跑一道 SWE-bench 题'), benchmark the agent on SWE-bench_Verified or SWE-bench_Multilingual, or check whether a generated patch resolves an instance. Optional dependency — install via `pip install opensquilla[swebench]`; also needs the docker CLI and an OPENROUTER_API_KEY.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill swe-bench --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.