CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/at-spi-linux

Authors Linux desktop UI tests via AT-SPI - the DBus-based Assistive Technology Service Provider Interface implemented by `at-spi2-core` (registry daemon + `libatspi` C library + ATK GTK bridge). Covers enabling toolkit accessibility (`gsettings set org.gnome.desktop.interface toolkit-accessibility true`), driving GTK + Qt apps through Python `dogtail` (object-oriented + procedural APIs), inspecting the tree with Accerciser, scripting via `pyatspi`, and CI integration on headless Linux runners with `Xvfb` + `dbus-launch`. Use for Linux-side desktop tests of GTK applications, Qt apps with QAccessible enabled, and Electron apps on Linux.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thoroughly actionable, well-sequenced skill with executable code at every step and strong error-recovery/limitations coverage. The main weakness is mild verbosity in the Overview and quoted documentation that could be trimmed or delegated to the linked references.

Suggestions

Trim the Overview architecture prose and the inline README/libatspi blockquotes; replace with a one-line pointer to the already-linked at-spi2-core README to raise conciseness.

Consider moving the full Step 9 CI workflow yaml into a references/ file referenced from the main body, keeping SKILL.md as a leaner overview.

Add an explicit validate->fix->retry note in Step 7/8 (e.g. 'on assert failure, check ~/.dogtail/logs and the captured screenshot, then re-run') to make the feedback loop explicit.

DimensionReasoningScore

Conciseness

Mostly efficient with abundant executable code, but the Overview explains AT-SPI architecture and embeds several README/libatspi blockquotes (e.g. 'init() ... connects to the accessibility registry') that restate documentation Claude could be pointed to rather than quoted inline.

2 / 3

Actionability

Provides copy-paste-ready bash ('gsettings set ...', 'xvfb-run ... dbus-launch ... pytest'), complete runnable Python for both dogtail APIs and pyatspi, and a full CI workflow yaml - all concrete and executable.

3 / 3

Workflow Clarity

Steps 1-9 are clearly sequenced (enable accessibility -> install -> inspect -> author -> run -> parse -> CI), with assertion-based validation in the test code and an Anti-patterns table giving 'why it fails / fix' error-recovery guidance.

3 / 3

Progressive Disclosure

Well-organized into Overview, When to use, numbered Steps, Anti-patterns, Limitations, and References, with one-level-deep signaled references to authoritative external docs (at-spi2-core README, libatspi docs, dogtail README) and related skills - no deep reference nesting.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong, third-person description that concretely lists capabilities and provides an explicit 'Use for' trigger scoped to Linux GTK/Qt/Electron desktop testing. It is dense with technical detail but every term earns its place and the niche is clearly distinguished.

DimensionReasoningScore

Specificity

Names multiple concrete actions - 'enabling toolkit accessibility', 'driving GTK + Qt apps through Python dogtail', 'inspecting the tree with Accerciser', 'scripting via pyatspi', and 'CI integration ... with Xvfb + dbus-launch' - matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does (authors tests via AT-SPI, covers the listed capabilities) and when to use it via an explicit 'Use for Linux-side desktop tests of GTK applications, Qt apps ... and Electron apps on Linux' clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say ('Linux desktop UI tests', 'GTK applications', 'Qt apps', 'Electron apps on Linux') alongside the tool names, giving good coverage rather than pure jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Linux-only AT-SPI niche distinct from Windows UIA / macOS XCTest backends, with tool-specific triggers (dogtail, pyatspi, Accerciser) unlikely to fire for other skills.

3 / 3

Total

12

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents