CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/object-model-patterns

Pure reference catalog of the canonical object-model architecture patterns for test automation frameworks - Page Object Model (Fowler), Screenplay (Marcano/Palmer/Hill), Component Object, App Actions (Cypress idiom), Service Object, Repository, and Screen Object (the desktop/mobile sibling of Page Object covering Windows UIA, macOS XCTest, Linux AT-SPI, Appium / Espresso) - each with its canonical citation, when-to-use rules, refuse-to-mix anti-patterns, and a worked example. This is the architecture-tier reference - what each pattern *is* - not file-level style rules and not tool-specific configuration. Use when designing, reviewing, or migrating a test framework's object-model architecture.

66

Quality

83%

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

57%

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

A well-organized reference catalog with strong progressive disclosure (overview in SKILL.md, detail in references/pattern-catalog.md) and concrete selection guidance. It loses points on conciseness for re-explaining well-known concepts and on actionability/workflow because a catalog is inherently descriptive rather than procedural.

Suggestions

Trim the verbatim Fowler/Selenium definition quotes in Pattern 1 to just the load-bearing rules they ground — Claude already knows what a Page Object is.

In Pattern 7 (Screen Object), since the three rules are stated to 'transfer unchanged from POM', reference them rather than re-deriving each one inline.

Lead each pattern with the actionable rule/matrix row first, then the citation, so the catalog reads as decision guidance rather than description.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but it re-explains concepts Claude already knows (e.g. quoting Fowler's and Selenium HQ's full POM definitions) and the Screen Object section re-lists the three POM rules it itself calls 'transfer unchanged' then re-explains each — could be tightened without losing the canonical-citation value.

2 / 3

Actionability

Concrete guidance is present — the pattern-selection matrix, the load-bearing rules, the cross-cutting anti-pattern table, and a copy-paste-ready C# worked example — but the bulk is descriptive catalog ('what each pattern *is*') rather than executable how-to instruction, so it sits at 'some concrete guidance but largely describes' rather than fully copy-paste ready.

2 / 3

Workflow Clarity

The decision flow is sequenced (When to use → Do not use → selection matrix → Hand-off targets), but this is a reference catalog with no multi-step procedure or validation checkpoints; the organization is clear yet there is no explicit workflow with feedback loops to elevate it to a 3.

2 / 3

Progressive Disclosure

SKILL.md is an overview that signals a single one-level-deep reference — 'the detailed per-pattern when-to-use rules and anti-pattern tables live in [references/pattern-catalog.md]' — and that file exists and holds exactly the deferred detail, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

9

/

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.

The description is specific, trigger-rich, and self-scoping: it names all seven patterns, states the explicit 'Use when' trigger, and explicitly distinguishes itself from file-level and tool-config skills. Voice is third person throughout. No weak dimensions; no changes needed.

DimensionReasoningScore

Specificity

Enumerates multiple concrete catalog items — 'Page Object Model (Fowler), Screenplay (Marcano/Palmer/Hill), Component Object, App Actions (Cypress idiom), Service Object, Repository, and Screen Object' — and what each carries ('canonical citation, when-to-use rules, refuse-to-mix anti-patterns, and a worked example'), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Pure reference catalog of the canonical object-model architecture patterns...') and when ('Use when designing, reviewing, or migrating a test framework's object-model architecture'), matching the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Uses the natural domain vocabulary engineers actually say — 'Page Object Model', 'Screenplay', 'App Actions', 'Service Object', 'Repository', 'Screen Object' — plus the trigger phrase 'Use when designing, reviewing, or migrating a test framework's object-model architecture', giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche ('the architecture-tier reference - what each pattern *is* - not file-level style rules and not tool-specific configuration') and names sibling skills it is not, making triggering for the wrong skill unlikely.

3 / 3

Total

12

/

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.

Reviewed

Table of Contents