CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stand-ui-test

Write, fix, or review the browser journeys in tests/stand/ui/ — Playwright (Python, sync API) against a deployed Insight stand with a real Keycloak sign-in. Covers the governing UI-vs-API rule and how to justify a browser test in writing, accessibility-first locators, the page-object/flows split, manifest-derived expectations, URL/deep-link validation, and real browser downloads. Use for any request to write, add, fix or review a committed browser test in this repository — 'add a Playwright test for X', 'the UI test is failing', 'turn this scenario into a browser journey', 'add a deep-link or download regression' — and for anything under tests/stand/ui/. For HTTP contract tests use stand-api-test; playwright-cli is for driving a browser interactively at a prompt and for Playwright's own CLI — reach for it only when nothing will be committed under tests/stand/ui/; drive-ui is for looking at a stand by hand.

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, high-fidelity skill body: it adds only repository-specific knowledge Claude could not already have, provides executable code and commands for the common cases, and closes with a validated 10-step procedure including a deliberate-failure check. The only real weaknesses are mild redundancy in restating the governing rule and the absence of any progressive-disclosure split — all material lives inline in one long file.

DimensionReasoningScore

Conciseness

Assumes Claude's competence throughout — no explanation of what Playwright, pytest, or OIDC are — and nearly every sentence carries non-obvious repo knowledge (the __Host- cookie origin rule, aria-rowcount on virtualized grids, the pytest path-union gotcha). Falls short of level 5 because the governing rule is restated several times and the two long block-quote exemplars could be trimmed — 'minor instances of over-explanation that could be trimmed' (level 4) rather than every token earning its place; not level 3, since there are no explanations of concepts Claude already knows, only emphasis redundancy.

4 / 5

Actionability

Fully executable guidance covering the common cases: copy-paste run commands with the --instance/--image caveats, an executable sign_in snippet, concrete locator code (get_by_role with accessible names), a manifest-derivation snippet with an assert guard, and named files to read (flows.py, downloads.py, src/ingestion/tools/seed/PROFILE.md, tests/pyproject.toml), with named worked examples (test_git_output_timeseries etc.). Matches level 5's copy-paste-ready coverage; level 4 would imply executable gaps that are not present.

5 / 5

Workflow Clarity

The 10-step Procedure is clearly sequenced with explicit validation checkpoints and feedback loops: step 1 is a decision gate ('Try to make it an API test first'), step 7 guards against an empty derivation, step 9 requires auditing fidelity and running headed with a deliberately broken expectation to confirm it fails for the right reason, and 'Run stand-test-auditor over a new journey before considering it done'. Level 5's 'explicit validation steps; feedback loops' is met; level 4's 'minor validation gaps' is not.

5 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, and its cross-references to sibling skills and repo files are clearly named one hop away. However, no reference files exist: everything — including the justification exemplars, the download-parsing walkthrough, and run-mode details — is inline in a ~270-line file, so it sits at level 4 ('good structure; most content appropriately placed; minor organization gaps') rather than level 5's multi-file split, and above level 3 since sections are well organized and references are clearly signaled, not buried.

4 / 5

Total

18

/

20

Passed

Description

100%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.

An exemplary description: concrete capability list, quoted natural trigger phrases, explicit what/when, and explicit boundary guidance against three adjacent skills. The only nitpick is length (~1050 characters), but every clause is load-bearing disambiguation rather than padding, so it does not warrant a lower score under the verbosity guideline.

DimensionReasoningScore

Specificity

Quotes multiple concrete actions — 'Write, fix, or review the browser journeys in tests/stand/ui/' plus a comprehensive capability list ('accessibility-first locators, the page-object/flows split, manifest-derived expectations, URL/deep-link validation, and real browser downloads'). Coverage is comprehensive rather than having minor gaps, so it matches the level-5 anchor, not level 4.

5 / 5

Completeness

Explicitly answers both questions: what ('Write, fix, or review the browser journeys... Playwright (Python, sync API) against a deployed Insight stand with a real Keycloak sign-in') and when ('Use for any request to write, add, fix or review a committed browser test in this repository' with concrete quoted triggers). Level 4 requires a 'when' that 'could be more explicit'; here the when-clause is fully explicit with trigger phrases.

5 / 5

Trigger Term Quality

Includes quoted natural phrasings users would actually say — 'add a Playwright test for X', 'the UI test is failing', 'turn this scenario into a browser journey', 'add a deep-link or download regression' — plus synonyms (browser test / UI test / Playwright test / browser journey) and the repo path. This goes beyond 'a few natural terms missing' (level 4) to comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Actively disambiguates three sibling skills — 'For HTTP contract tests use stand-api-test; playwright-cli is for driving a browser interactively at a prompt... drive-ui is for looking at a stand by hand' — and pins its niche to committed tests under tests/stand/ui/. Clear niche with distinct triggers and minimal conflict risk, exceeding level 4's 'minor overlap risk'.

5 / 5

Total

20

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

constructorfabric/insight

Path

.claude/skills/stand-ui-test/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.