CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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).

Quality

75%

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

78%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 tight, well-sequenced audit-and-refactor workflow with concrete commands, specific API names, and validation checkpoints before and after changes. The main residual weaknesses are the duplicated objective statement, the missing migration code example, and the absence of an error-recovery loop in the verify step.

Suggestions

Remove the duplicated objective — the intro paragraph and the "## Objective" section restate the frontmatter description verbatim; keep one.

In step 4, add a short migration snippet showing a blocking call wrapped in Task.Backgroundable (or ReadAction.nonBlocking) so the refactor is copy-paste ready.

Add a feedback loop to step 6: if freezes persist in the runIde sandbox, re-audit the flagged EDT call sites and re-verify.

DimensionReasoningScore

Conciseness

The body is lean and command-driven ("Run `./gradlew test` and `./gradlew verifyPlugin`", "Search for usages of `runInEdt`, `invokeLater`, and `invokeAndWait`") with no concept explanations Claude already knows; the only over-explanation is the objective sentence duplicated verbatim in the intro paragraph and the Objective section — minor trimmable padding, not the "some unnecessary explanation" of the 3 anchor.

4 / 5

Actionability

Guidance is mostly executable: exact gradle commands, exact search terms, and exact migration targets ("`Task.Backgroundable` or `ReadAction.nonBlocking`"). As an instruction-only skill the absence of code is acceptable, but there is no example of the actual migration pattern (e.g., wrapping a call in Task.Backgroundable), which keeps it short of fully copy-paste-ready.

4 / 5

Workflow Clarity

A clear 7-step sequence with validation checkpoints at both ends (baseline "ensure the project is in a good state before refactoring", then "ensure no regressions", sandbox run, manual test steps) and an explicit "Do not commit or push" guardrail. It falls short of the 5 anchor because there is no error-recovery feedback loop (what to do when verifyPlugin or runIde reveals a freeze).

4 / 5

Progressive Disclosure

No bundle files exist and the body is under 50 lines with clean, well-labeled sections (Baseline, Audit, Identify, Migrate, Check Modality, Verify, Report), so per the scoring guideline for short single-purpose skills needing no external references, well-organized sections alone earn the top score.

5 / 5

Total

17

/

20

Passed

Description

58%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 states concrete, domain-specific capabilities in proper third-person voice, but it entirely lacks a "Use when..." trigger clause and natural trigger synonyms, which caps both completeness and trigger-term quality. Adding explicit usage triggers and common user phrasings would lift it substantially.

Suggestions

Append a trigger clause such as "Use when the user reports a frozen, hanging, or unresponsive UI, or when refactoring Swing/IntelliJ plugin code that performs I/O or heavy computation on the EDT."

Include natural synonyms users would actually say — "hang", "unresponsive", "laggy", "Swing", "IntelliJ plugin" — alongside "UI freezes".

Clarify the platform context (IntelliJ plugin / Swing) in the description itself to reduce overlap with generic UI-performance skills.

DimensionReasoningScore

Specificity

Phrases like "validating threading rules and migrating blocking calls off the Event Dispatch Thread (EDT)" name concrete, domain-specific actions rather than vague capabilities, though "Prevent UI freezes" is a goal statement rather than an action, leaving minor gaps in coverage — between the 1-2-action (3) and comprehensive (5) anchors, noticeably above the midpoint.

4 / 5

Completeness

The "what" is clear (validate threading rules, migrate blocking calls off the EDT), but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3, and it is not below 3 since the what-half is concrete.

3 / 5

Trigger Term Quality

"UI freezes" and "responsive user experience" are natural phrases users would say, but common variations like "hang", "unresponsive", "laggy", "Swing", or "IntelliJ plugin" are absent, and "Event Dispatch Thread (EDT)" leans technical — matching the anchor for some relevant keywords but missing common synonyms.

3 / 5

Distinctiveness Conflict Risk

The EDT threading niche is fairly distinct from most skills, but "UI freezes" and "responsive user experience" are broad enough to overlap with general performance, frontend, or Android UI skills — mostly distinct with minor overlap risk, short of the clear-niche anchor (5).

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

flutter/flutter-intellij

Path

.agents/skills/audit-ui-thread-safety/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.