triage

Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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 content is a well-organized, actionable gatekeeper spec with strong workflow sequencing and explicit validation checkpoints. Its main weakness is mild verbosity in the inlined policy/guardrail sections and some detail that could live in the referenced workflow files.

Suggestions

Tighten the 'No fabricated policies' and approval-guardrail paragraphs — the enumerated Stage 0/1-pre/1c sub-cases read as policy detail that already lives in references/pr-workflow.md and could be condensed to a pointer.

Move the detailed escalation/criteria enumeration out of SKILL.md into references/pr-workflow.md, keeping only the one-line rule plus a 'see references' pointer to reduce token cost.

Consider a short 'Stages at a glance' table (Stage → comment → decision) at the top of the Workflow section so the sequence is scannable before diving into pre-flight detail.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (terse command snippets, no concept explanation), but some rule sections are quite verbose and could be tightened, e.g. the long 'No fabricated policies' and approval-guardrail paragraphs.	4 / 5
Actionability	Provides concrete executable commands (`gh issue view ... --json ...`, `enter_worktree(name: "triage")`) and specific guardrails, though several key details (stage templates, escalation criteria) are deferred to references rather than being inline.	4 / 5
Workflow Clarity	The multi-stage workflow is clearly sequenced with explicit pre-flight checkpoints, a duplicate-guard, and validation/feedback guidance ('Validate immediately', 'not verified: <reason>'); destructive/batch operations (auto-approval, CHANGES_REQUESTED) carry explicit guardrails and error-recovery loops.	5 / 5
Progressive Disclosure	Structure is good: SKILL.md is an overview with clearly signaled one-level-deep references (`references/issue-workflow.md`, `references/pr-workflow.md`) that exist as real files. The body inlines a fair amount of detailed rule/policy content that arguably belongs in the referenced workflow files, which is a minor organization gap.	4 / 5
	Total	17 / 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 strong across all dimensions: it names concrete actions, includes natural trigger terms for both issues and PRs, and explicitly answers what and when. It is tightly scoped to a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Gatekeep and review GitHub issues and pull requests', 'GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments'), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' ('Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers') and 'when' ('Use for GitHub Action issue triage, PR admission checks...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases users would say are well covered ('GitHub issues and pull requests', 'GitHub Action issue triage', 'PR admission checks', 'PR review', 'bilingual GitHub comments'), including synonyms across both issues and PRs.	5 / 5
Distinctiveness Conflict Risk	The niche is clearly scoped to GitHub triage/gatekeeping for Qwen Code maintainers with distinct bilingual-comment triggers, making conflict with other skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: QwenLM/qwen-code
Path: .qwen/skills/triage/SKILL.md
Commit: a858dea

Reviewed: 5 hours ago

Table of Contents

Discovery Implementation Validation

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.