CtrlK
BlogDocsLog inGet started
Tessl Logo

e2e-testing

Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response payloads. Trigger on mentions of E2E testing, headless testing, MCP tool testing, or reproducing issues.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

An exemplary operational skill body: dense, copy-paste-ready, well-sequenced with checkpoints, and properly offloading detail to real one-level-deep reference and script files.

DimensionReasoningScore

Conciseness

Lean and information-dense: concrete commands, jq filters, exact flag combos, and non-obvious gotchas, with no padding explaining concepts Claude already knows. Not anchor-2 because nothing reads as tighten-able fluff.

3 / 3

Actionability

Fully executable, copy-paste-ready bash, jq, and tmux commands with exact flags and field names throughout, e.g. the headless invocation, the 'esc to cancel' poll loop, and the API-logging command.

3 / 3

Workflow Clarity

The tmux flow is a clear sequence (launch, send with delay, poll-for-completion, capture, cleanup) with an explicit completion checkpoint and error-filtering guidance; not anchor-2 because validation is explicit rather than implicit.

3 / 3

Progressive Disclosure

Overview body cleanly signals one-level-deep references ('read references/mcp-testing.md', 'read references/mock-openai-server.md') and scripts, all of which exist as real bundle files; content is appropriately split rather than inlined.

3 / 3

Total

12

/

12

Passed

Description

90%

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

A strong, specific description with explicit trigger guidance and a clear niche. The only ding is the second-person phrasing ('you need to'), which the rubric penalizes on specificity.

Suggestions

Rewrite in third person to avoid the specificity penalty, e.g. 'Guides end-to-end testing of the Qwen Code CLI... Use when verifying CLI behavior with real model calls, reproducing user-reported bugs, testing MCP tool integrations, or inspecting raw API payloads.'

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('verify CLI behavior with real model calls', 'reproduce user-reported bugs end-to-end', 'test MCP tool integrations', 'inspect raw API request/response payloads'), which is anchor-3 material, but the explicit second-person voice ('Use this skill whenever you need to') triggers the rubric's -1 specificity penalty for non-third-person phrasing.

2 / 3

Completeness

Explicitly answers both what ('Guide for running end-to-end tests... including headless mode, MCP server testing, and API traffic inspection') and when ('Use this skill whenever... Trigger on mentions of...'), satisfying the anchor-3 bar for both halves.

3 / 3

Trigger Term Quality

Natural, user-utterable trigger terms with good coverage: 'E2E testing', 'headless testing', 'MCP tool testing', and 'reproducing issues' match how a developer would phrase the need.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Qwen Code CLI E2E testing with distinct triggers, occupying a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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
QwenLM/qwen-code
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.