CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-ui-thread-safety

Prevent UI freezes and ensure a responsive user experience by validating threading rules and migrating blocking calls off the Event Dispatch Thread (EDT).

56

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/audit-ui-thread-safety/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 is a well-structured, mostly actionable workflow with solid baseline and verification checkpoints and good organization for a single-purpose skill. Its main weakness is redundancy from restating the objective and commands, plus a missing error-recovery feedback loop and migration code example.

Suggestions

Remove the duplicate objective: drop the verbatim "You are tasked with..." opening line or the "## Objective" section, keeping the goal stated once.

Add an explicit feedback loop in step 6: "If `./gradlew test` or `verifyPlugin` fails, fix the issue and re-run before proceeding; only sandbox-test once green."

Include a short copy-paste snippet for the migration step showing Task.Backgroundable or ReadAction.nonBlocking wrapping a heavy operation.

DimensionReasoningScore

Conciseness

The objective ("Prevent UI freezes and ensure a responsive user experience by validating threading rules") is restated nearly verbatim in the opening line and the "## Objective" section, and step 6 repeats the baseline gradle commands, so the body could be noticeably tightened.

3 / 5

Actionability

Concrete gradle commands and named APIs (Task.Backgroundable, ReadAction.nonBlocking) give mostly executable guidance, but the core migration step lacks a copy-paste code snippet, leaving a minor gap.

4 / 5

Workflow Clarity

A clear 7-step sequence with a baseline checkpoint (step 1) and a verify checkpoint (step 6) is present, but there is no explicit "if verification fails, fix and re-run" feedback loop.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references, and is organized into clear numbered sections, meeting the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

16

/

20

Passed

Description

53%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 clearly conveys what the skill does within a distinct EDT niche, but lacks an explicit "Use when..." trigger clause and leans on technical jargon over natural user phrasing. Specificity and completeness are capped by the missing trigger guidance.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g., "Use when an IntelliJ plugin suffers UI freezes, hangs, or sluggishness, or when auditing EDT usage and moving blocking work to background threads."

Surface more natural keywords and synonyms users actually say (e.g., "UI freeze", "UI hang", "laggy plugin", " EDT blocking") alongside the technical EDT term.

Optionally enumerate a third concrete action (e.g., verifying modal dialogs don't block) to push specificity from 1-2 actions toward "several".

DimensionReasoningScore

Specificity

Names the UI-thread-safety domain and two concrete actions ("validating threading rules" and "migrating blocking calls off the Event Dispatch Thread (EDT)"), matching the 1-2 concrete actions anchor without being comprehensive.

3 / 5

Completeness

The "what" is clearly stated (prevent freezes via validation and migration), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"UI freezes" and "responsive user experience" are natural user terms, but "Event Dispatch Thread (EDT)" and "threading rules" lean technical and common synonyms/variations are absent.

3 / 5

Distinctiveness Conflict Risk

The EDT/UI-freeze niche is mostly distinct with minimal conflict risk, though "responsive user experience" could overlap with general performance skills, keeping it just below a 5.

4 / 5

Total

13

/

20

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
flutter/flutter-intellij
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.