component-fixtures

Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Highly actionable content with strong executable examples and well-structured sections, weakened by notable duplication between the adapting and writing-friendly sections and the absence of verification checkpoints in the run workflow.

Suggestions

Consolidate 'Adapting Existing Components for Fixtures' and 'Writing Fixture-Friendly Components' — they repeat CSS decoupling, DI, auto-focus, and DOM-node exposure; merge into one section with sub-points distinguishing retrofit vs. greenfield.

Add a verification step to 'Running Fixtures Locally' (e.g., confirm the fixture appears in `mcp_component-exp_list_fixtures` and the screenshot matches expectations before iterating).

Consider moving the long utility table and full pre-registered service list into a `references/` file so the SKILL.md body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Language is lean and code-forward with no padding about concepts Claude already knows, but 'Adapting Existing Components for Fixtures' and 'Writing Fixture-Friendly Components' substantially duplicate each other (CSS decoupling, DI, auto-focus disabling, exposing the DOM node all appear in both), which could be consolidated.	3 / 5
Actionability	Provides copy-paste-ready TypeScript/CSS examples, a utility export table, named service lists, and bad-vs-better pitfall patterns covering the common fixture authoring cases — fully executable guidance.	5 / 5
Workflow Clarity	'Running Fixtures Locally' gives a clear 3-step sequence but lacks any validation/verification checkpoint (e.g., how to confirm a fixture rendered correctly or a screenshot is stable), and the bulk of the skill is reference patterns rather than a sequenced workflow.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and a navigation-friendly structure; no bundle files exist so everything is inlined, and the ~340-line body could plausibly split the large 'Adapting'/'Writing Fixture-Friendly' reference into a separate file, but placement is otherwise reasonable.	4 / 5
	Total	15 / 20 Passed

Description

92%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, specific description that clearly states both capability and trigger conditions with concrete domain terms. Minor room to add synonyms or the `.fixture.ts` file extension to broaden natural trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete coverage areas — 'creating or updating component fixtures for screenshot testing', 'designing UI components to be fixture-friendly', plus 'fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls' — giving comprehensive, specific action coverage.	5 / 5
Completeness	Explicitly answers both what ('creating or updating component fixtures... Covers fixture file structure, theming...') and when ('Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keywords ('component fixtures', 'screenshot testing', 'designing UI components', 'fixture-friendly') with a clear 'Use when' clause, but lacks synonyms or file-extension variants a user might naturally say (e.g. '.fixture.ts', 'visual testing').	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (component fixtures for screenshot testing via the component explorer) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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.

Repository: posit-dev/positron
Path: .github/skills/component-fixtures/SKILL.md
Commit: 10323ef

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.