CtrlK
BlogDocsLog inGet started
Tessl Logo

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck <PID> to focus on a specific process.

69

Quality

85%

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

88%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.

A highly actionable, well-sequenced diagnostic skill with executable commands, explicit validation checkpoints, and thoughtful fallback handling. Minor conciseness and progressive-disclosure improvements are possible but the core guidance is strong.

Suggestions

State the credential-redaction rule once near the top and reference it, instead of repeating it at each command-quoting point.

Consider hoisting the longer shell command blocks into a references/ file to slim the SKILL.md overview and improve progressive disclosure.

Tighten the regex-matching rationale in 'What to look for' — the anchored-path explanation can be compressed without losing the false-positive warning.

DimensionReasoningScore

Conciseness

Dense with non-obvious cross-platform gotchas (grep -E/\b, ss -p permissions, lsof -nP) that earn their tokens, but the credential-redaction note is repeated across sections and the regex rationale is somewhat verbose.

4 / 5

Actionability

Fully executable, copy-paste-ready shell commands throughout (ps, grep, node -e, lsof, ss, sample, /proc/pid/stack) with macOS/Linux variants covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sequence with explicit validation (kill -0 PID liveness, qwen-path guard, sustained-CPU re-sample) and feedback/fallback loops (sidecar→ps, lsof→timeout, ss→lsof); diagnostic-only so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Well-organized into clear sections (What to look for, Argument validation, Investigation steps, Report, Notes) and self-contained with no external refs, but at ~115 lines it is not the lean overview-with-one-level-references ideal.

4 / 5

Total

18

/

20

Passed

Description

82%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.

A specific, well-triggered, distinctive diagnostic description that lists concrete actions and natural synonyms. Its main weakness is the absence of an explicit 'Use when...' trigger clause, capping completeness at 3.

Suggestions

Add an explicit trigger clause such as 'Use when the user reports a Qwen Code session that is frozen, stuck, hanging, or unusually slow.' to lift completeness.

Clarify the 'when' alongside the existing invocation hint ('Use /stuck or /stuck <PID>') so the trigger condition is stated, not just the command syntax.

DimensionReasoningScore

Specificity

Lists multiple concrete scan actions — 'problematic processes, high CPU/memory usage, hung subprocesses, and debug logs' — giving comprehensive coverage of the diagnostic domain.

5 / 5

Completeness

The 'what' is clear (diagnose stuck sessions via specific scans) but there is no explicit 'Use when...' trigger clause — only an invocation hint ('Use /stuck or /stuck <PID>'), so the cap at 3 applies.

3 / 5

Trigger Term Quality

Uses natural user synonyms 'frozen, stuck, or slow' alongside 'Qwen Code sessions', matching the phrasing a user would actually say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (frozen/stuck/slow Qwen Code sessions on this machine) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

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.