CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-pr

This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr <n>", "/verify-pr <n> --publish" (local round that also posts the report comment), "深度验证这个 PR", "验证这个 PR 并把报告发到评论", "有更新了,重新验证", "重新验证 PR <n>", "re-verify after update", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr<n>-verify-<ts>/report.md plus a machine-readable verdict. Designed for the token-free CI verify job; also usable locally.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

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

The body delivers exceptional actionability and workflow discipline — executable commands, exact artifact contracts, and validation gates at every step — and nearly all of its content is hard-won, non-obvious guidance rather than padding. Its weaknesses are size and placement: a ~2,200-line monolith with one reference file, containing repeated measured examples and whole operational recipes that belong in progressive-disclosure reference files.

Suggestions

Move the self-contained operational recipes — the Docker/model-proxy container recipe, Watch mode setup, and the maintainer-driven local publish rules — into references/*.md files, keeping SKILL.md to the entry paths, environment contract, scope selection, method summary, and artifact contract.

Deduplicate measured examples that appear in multiple sections (e.g. the parked-Turn-2 cancel example in both Scope selection item 1 and Wire-oracle harnesses' 'Parameterise scenarios'), keeping one canonical instance and cross-referencing it.

Compress the A/B methodology's ~30 heuristic bullets to a one-line trigger rule each, relocating the extended "Measured example" narratives to a methodology reference file loaded only when scoping A/B work.

DimensionReasoningScore

Conciseness

At ~2,200 lines the body is dense with genuinely non-obvious, measured lessons and does not explain basics Claude already knows, but it is well past lean: measured examples repeat across sections (e.g. the parked-Turn-2 cancel example appears in both Scope selection and Wire-oracle harnesses, kept byte-identical by the file's own admission), and the publish/guard/watch policy prose could be substantially tightened. Anchor 3 ("mostly efficient but… could be tightened") fits better than 4, where trimming needs would be minor.

3 / 5

Actionability

Guidance is fully executable end to end: copy-paste bash blocks for the container recipe and proxy, exact commands ("git worktree add tmp/base-tree <base>", "node scripts/verify-capture.mjs --out … -- <cmd>"), exact artifact contracts (verdict.txt "exactly one word", assertions.json field shapes with attribution enums), and concrete cell-table shapes to aim for ("5/9 flip from broken to fixed").

5 / 5

Workflow Clarity

The process is explicitly sequenced with validation checkpoints throughout: "Scope selection (do this before running anything)", the isolation gate with exit-code semantics ("treat exit 4 as 'this is not a boundary'"), the checker run before publishing, A/A controls for environmental failures, and "Fail loud" as a hard rule. Feedback loops (validate → fix → re-validate, re-measure never diff) are present at every risky stage.

5 / 5

Progressive Disclosure

The single bundle reference (references/android.md) exists and is clearly signaled at the point of need ("read references/android.md before scoping"), and section structure is strong — but the remaining ~2,200 lines, including the full Docker/model-proxy recipe, watch-mode setup, local publish rules, and ~30 methodology heuristics with extended narratives, are inlined in SKILL.md where reference files would serve. Anchor 3 ("content that should be separate is inline") applies; structure is too good for anchor 2.

3 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 a model example: third-person, dense with concrete capabilities and artifact names, and it embeds the exact natural-language and command triggers (English and Chinese) that should activate the skill, including follow-up re-verification phrasing. Both the "what" and "when" are explicit, and the niche is sharply distinct.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "run a sandboxed deep verification of a qwen-code PR", "A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates", "producing tmp/pr<n>-verify-<ts>/report.md plus a machine-readable verdict", and the publish variant that "posts the report comment" — with concrete artifact paths, comprehensive for what the skill does.

5 / 5

Completeness

Both questions are answered explicitly: what (sandboxed deep verification with A/B proof, harnesses, gates, and named artifacts) and when ("This skill should be used to…" followed by concrete trigger phrases). It also names the execution contexts ("Designed for the token-free CI verify job; also usable locally").

5 / 5

Trigger Term Quality

Trigger phrases are enumerated in two languages and across invocation styles — "/verify-pr <n>", "/verify-pr <n> --publish", "深度验证这个 PR", "验证这个 PR 并把报告发到评论", "有更新了,重新验证", "重新验证 PR <n>", "re-verify after update" — covering command forms, natural requests, and follow-up synonyms. This is comprehensive synonym coverage; no anchor-4 gap ("a few natural terms missing") is identifiable.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — deep verification of qwen-code PRs with a named artifact layout and repo-specific trigger phrases — so overlap with generic review/verification skills is minimal and the triggers would not fire for the wrong skill.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (2204 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 12 missing, 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

QwenLM/qwen-code

Path

.qwen/skills/verify-pr/SKILL.md

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.