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

59

Quality

67%

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

85%

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 strong, actionable, well-sequenced workflow with validation built in; the only inefficiency is the duplicated objective statement that mirrors the frontmatter.

Suggestions

Remove the redundant '## Objective' section (or the 'You are tasked with...' intro) since both repeat the frontmatter description verbatim.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no concept explanations), but the opening 'You are tasked with...' line and the '## Objective' section repeat the same sentence as the frontmatter, so not every token earns its place.

2 / 3

Actionability

Concrete executable commands ('./gradlew test', './gradlew verifyPlugin', './gradlew runIde'), specific search targets ('runInEdt', 'invokeLater', 'invokeAndWait'), and named APIs ('Task.Backgroundable', 'ReadAction.nonBlocking') make the guidance copy-paste ready.

3 / 3

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints (baseline tests, then testClasses/test/verifyPlugin plus a runIde sandbox check) provides the feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

At well under 50 lines with no need for external references, the well-organized numbered sections satisfy the simple-skill scoring note for a top score.

3 / 3

Total

11

/

12

Passed

Description

50%

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 a clear what but no explicit when, mixes natural and technical terms, and is only moderately distinctive. It sits squarely at the middle anchor across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user reports UI freezes, laggy dialogs, or asks about EDT/threading issues in an IntelliJ plugin.'

Soften jargon with natural variations users say ('UI hangs', 'frozen UI', 'UI thread', 'plugin freezes') alongside 'EDT' and 'blocking calls'.

Use third-person voice ('Prevents UI freezes...') instead of the imperative 'Prevent', and drop the abstract 'ensure a responsive user experience' padding in favor of another concrete action.

DimensionReasoningScore

Specificity

Names concrete actions ('validating threading rules', 'migrating blocking calls off the Event Dispatch Thread (EDT)') and a clear domain, but only two concrete actions plus an abstract goal ('ensure a responsive user experience'), and the imperative 'Prevent' is not the third-person voice the rubric prefers.

2 / 3

Completeness

It clearly states what the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 2.

2 / 3

Trigger Term Quality

'UI freezes' and 'responsive user experience' are natural user terms, but 'Event Dispatch Thread (EDT)' and 'blocking calls' are technical jargon, so common variations a user would say are missing.

2 / 3

Distinctiveness Conflict Risk

The EDT/threading niche is somewhat distinctive, but the opening 'Prevent UI freezes and ensure a responsive user experience' overlaps with general performance skills and there are no explicit triggers to disambiguate.

2 / 3

Total

8

/

12

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.