CtrlK
BlogDocsLog inGet started
Tessl Logo

run-deep-swe

Score any AI model on the DeepSWE coding-agent benchmark via the OpenRouter API. Use when the user wants an independent, reproducible coding-agent eval — "run DeepSWE", "benchmark this model on DeepSWE", "score model X on the coding benchmark", "test a model via OpenRouter on DeepSWE", or to verify vendor-reported coding scores. Covers setup, the OpenRouter wiring for mini-swe-agent, single-task / subset / full 113-task runs, and leaderboard submission.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, executable runbook: concrete commands, an explicit smoke-test validation gate before token-heavy runs, and a failure-mode table for recovery. It assumes Claude's intelligence and avoids tutorial-style padding.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — it does not explain Docker, git, or what a benchmark is, and every section earns its tokens with executable commands and non-obvious wiring notes.

3 / 3

Actionability

Provides fully executable `pier run` commands with exact flags, OpenRouter slugs, env vars, and a copy-paste-ready single-task smoke test rather than pseudocode.

3 / 3

Workflow Clarity

Sequences state-check → setup → wiring → smoke test → subset → full → output, with an explicit pass-criteria checkpoint before the costly full run and a failure-mode table for error recovery.

3 / 3

Progressive Disclosure

No external bundle files exist, but the self-contained ~90-line body is organized into well-labeled sections with clear navigation and no nested references, fitting the simple-skill guidance.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise yet complete, naming concrete capabilities, natural trigger phrasings, and explicit use-when guidance. It clearly distinguishes this skill from others and would reliably surface for the right requests.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — scoring models on the DeepSWE benchmark, single-task/subset/full 113-task runs, and leaderboard submission — rather than vague language.

3 / 3

Completeness

Explicitly states what the skill does (score AI models on DeepSWE via OpenRouter) and when to use it via an explicit 'Use when...' clause with concrete triggers.

3 / 3

Trigger Term Quality

Quotes natural phrasings a user would actually say ('run DeepSWE', 'benchmark this model on DeepSWE', 'score model X on the coding benchmark'), giving good trigger coverage.

3 / 3

Distinctiveness Conflict Risk

A clearly scoped niche — coding-agent eval on the DeepSWE benchmark via OpenRouter — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mishatojk/davidskills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.