CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/object-model-patterns

Use for any question or task about structuring UI test code, including quick ones such as Page Objects vs Screenplay or refactoring raw selector calls into an object model: Page Object, Screenplay, Component Object, App Actions, Service Object, Repository and Screen Object for desktop and mobile. Explains what each pattern is, when it fits and mixes to avoid, with citations and examples.

Quality

82%

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

Overview
Quality
Evals
Security
Files

Quality

Content

67%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 well-structured, authoritative reference catalog: the pattern selection matrix, quoted canonical sources, and cross-cutting anti-pattern table give a reviewer exactly the vocabulary to pick and enforce one pattern. Token efficiency is the main weakness, with the Screen Object section restating POM rules verbatim, repeating citations, and inlining example code that belongs in the reference file. The bundle split is real and clearly signaled, though Pattern 7's bulk breaks the otherwise consistent per-pattern footprint.

Suggestions

Replace the fully restated Screen Object rules with a pointer ('transfer unchanged from POM - see Pattern 1') to cut ~15 duplicated lines from Pattern 7.

Move the worked FlaUI/xUnit example and the WindowDriver provenance paragraph into references/pattern-catalog.md so Pattern 7 matches the other six patterns' overview footprint.

Drop or compress the References section - every URL is already cited inline at the rule it grounds, so the list doubles the same tokens.

DimensionReasoningScore

Conciseness

The body announces 'The three load-bearing rules transfer unchanged from POM' yet restates all three in full, the Fowler PageObject quote appears in both Pattern 1 and Pattern 7, and the References section re-lists every URL already cited inline; definitions of widely known patterns (POM, Repository, Service Object) also re-explain concepts Claude already knows. Mostly efficient and citation-dense, but the duplication is more than minor, which keeps it below anchor 4 and well above anchor 2 since the matrix, load-bearing rules, and anti-pattern tables all earn their tokens.

3 / 5

Actionability

Concrete, checkable rules ('No assertions in the POM body', 'Navigation methods return the next POM'), a decision matrix with explicit 'Best for' / 'Avoid for' columns, and one fully executable bad/good FlaUI example give mostly concrete guidance for an instruction-only reference skill. It falls short of anchor 5 because only one of the seven patterns carries a worked code example and the 'audit which pattern is in use' use case promises more than the checklist delivered.

4 / 5

Workflow Clarity

'When to use' lists four concrete scenarios plus explicit 'Do not use this skill to' boundaries, and the usage path is unambiguous: 'Use the pattern selection matrix to choose one; the detailed per-pattern when-to-use rules and anti-pattern tables live in references/pattern-catalog.md'. No validation loops are needed for a pure-reference skill with no execution steps, but the reviewing/auditing scenario lacks any sequenced steps, holding it below anchor 5.

4 / 5

Progressive Disclosure

A single one-level-deep bundle file ([references/pattern-catalog.md], verified to exist) is clearly signaled twice, with a sensible split: definitions, citations, and load-bearing rules in SKILL.md; when-to-use rules and anti-pattern tables in the reference. Anchor 5 is missed because Pattern 7 inlines ~40 lines of worked example and WindowDriver history that the other six patterns keep out of the overview, and the References section duplicates inline citations rather than adding navigation.

4 / 5

Total

15

/

20

Passed

Description

88%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 strong description: it answers both what and when explicitly, enumerates all seven pattern names as natural triggers, and even covers quick one-off questions ('including quick ones such as Page Objects vs Screenplay'). The only refinements available are synonym-level trigger coverage and boundary carving against sibling catalog skills. No dimension scored below 4.

DimensionReasoningScore

Specificity

'Explains what each pattern is, when it fits and mixes to avoid, with citations and examples' states multiple concrete capabilities, and the enumerated 'Page Object, Screenplay, Component Object, App Actions, Service Object, Repository and Screen Object' plus the concrete task 'refactoring raw selector calls into an object model' cover the domain comprehensively. This matches anchor 5 rather than 4 because there are no meaningful gaps in the capability list.

5 / 5

Completeness

The 'what' is explicit ('Explains what each pattern is, when it fits and mixes to avoid, with citations and examples') and the 'when' is explicit with concrete trigger phrases ('Use for any question or task about structuring UI test code, including quick ones such as Page Objects vs Screenplay or refactoring raw selector calls into an object model'). This clearly matches anchor 5: both questions answered with concrete trigger phrases, not merely implied as at anchor 4.

5 / 5

Trigger Term Quality

Natural triggers are present: 'structuring UI test code', 'Page Objects vs Screenplay', 'refactoring raw selector calls into an object model', all seven pattern names, and 'desktop and mobile'. A few natural terms users actually say are missing - the 'POM' abbreviation, framework names (Selenium, Playwright, Cypress), and 'test automation framework' - which fits anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear - UI test object-model architecture - and the pattern names are highly distinct triggers unlikely to fire the wrong skill. Minor overlap risk remains with closely related sibling skills (file-level test-code conventions, framework choice, test-data patterns) that the description does not explicitly carve out, which fits anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

18

/

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.

Reviewed

On this page