optics-context

Use the Optics design framework for styling applications. Apply Optics classes for layout, spacing, typography, colors, and components. Use when working on CSS, styling views, or implementing design system guidelines.

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/optics-context/SKILL.md

Quality

Content

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

The content provides concrete, token-based styling guidance with good file structure and progressive disclosure, but is weakened by a broken CSS example, absent validation checkpoints, and some workflow duplication in the Quick Reference.

Suggestions

Fix the button CSS example: nest the &.btn--primary, &.btn--secondary, and &.btn--outline modifiers inside the .btn {} block so the code is executable as written.

Add validation checkpoints to the workflows (e.g., verify a token exists in assets/tokens.json before use, confirm a new component renders before importing it in application.scss).

Remove or condense the "Quick Reference" section since it duplicates the discovery, token, and component workflows already detailed above.

Dimension	Reasoning	Score
Conciseness	The body largely assumes Claude knows CSS/BEM and avoids concept over-explanation, but the "Quick Reference" section re-lists the discovery/token/component workflows already covered and the two inlined component examples are lengthy, matching anchor 3.	3 / 5
Actionability	Concrete token var() names, exact file paths, and BEM structure are actionable, but the button example is broken CSS: the &.btn--primary/secondary/outline modifiers appear outside the already-closed .btn {} block, so the example is incomplete/non-executable as written.	3 / 5
Workflow Clarity	Discovery, token, and component workflows are clearly numbered and sequenced, but no validation or verification checkpoints exist and there are no feedback loops, matching anchor 3 (steps listed but validation gaps).	3 / 5
Progressive Disclosure	Sections are well-organized and reference assets/components.json and assets/tokens.json (both real, one-level-deep, clearly signaled), with bulk reference data properly split into bundle files; minor gaps keep it below 5.	4 / 5
	Total	13 / 20 Passed

Description

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

The description clearly communicates what the skill does and when to use it, with concrete styling categories and natural trigger terms. It is solid but not maximally comprehensive in its triggers or distinctiveness.

Dimension	Reasoning	Score
Specificity	"Apply Optics classes for layout, spacing, typography, colors, and components" lists several concrete styling actions, matching anchor 4; it falls short of 5 because the opening "Use the Optics design framework for styling applications" is overarching rather than a discrete action.	4 / 5
Completeness	It states both a clear "what" (apply Optics classes for the listed categories) and an explicit "when" ("Use when working on CSS, styling views, or implementing design system guidelines"); the when clause could enumerate more concrete user-mentionable triggers to reach 5.	4 / 5
Trigger Term Quality	"CSS", "styling views", and "design system guidelines" are natural terms users would say, giving good keyword coverage; missing common synonyms like "stylesheets" or "Rails" keeps it below 5.	4 / 5
Distinctiveness Conflict Risk	The named "Optics" framework niche with distinct triggers is mostly distinguishable, but the broad "CSS, styling views" phrasing has minor overlap risk with general frontend styling skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: RoleModel/rolemodel-skills
Path: skills/optics-context/SKILL.md
Commit: 6d600e9

Reviewed: 5 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.