CtrlK
BlogDocsLog inGet started
Tessl Logo

iptvnator-ui-design

Repository-specific UI design guidance for IPTVnator channel rows, EPG views, settings surfaces, shared selection styles, and light/dark theme consistency.

57

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/iptvnator-ui-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is concise and well-organized with concrete library/token references and a sensible checklist, but its validation and workflow steps are stated abstractly without explicit commands or error-recovery feedback loops, capping actionability and workflow clarity at 2. Adding exact Nx/Playwright commands and a retry-on-failure loop would lift both.

Suggestions

Replace abstract validation with concrete commands, e.g. the actual `nx test <project>` and Playwright target invocations rather than 'run the affected Nx project test target'.

Add an explicit error-recovery feedback loop in Validation (run → on failure inspect output → fix → re-run until green) for the destructive/batch UI changes the checklist covers.

Make the checklist steps more imperative and copy-paste ready where possible (e.g. exact grep/inspect commands for finding the nearest shared component).

DimensionReasoningScore

Conciseness

The body is lean (~22 lines), assumes Claude's competence, and never over-explains Angular/Material concepts, matching 'Lean and efficient; every token earns its place'.

3 / 3

Actionability

It gives concrete guidance (named libraries "@iptvnator/ui/components", "@iptvnator/portal/shared/ui", "@iptvnator/ui/epg" and "--app-selection-*" tokens) but validation targets are named abstractly rather than as copy-paste commands, fitting 'Some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

A numbered checklist gives a clear sequence and a Validation section exists, but checkpoints are implicit and there is no fix→retry feedback loop, matching 'Steps listed but validation gaps; checkpoints missing or implicit'.

2 / 3

Progressive Disclosure

Under 50 lines with no bundle files and well-organized named sections (Principles, Checklist, Validation) plus a single legitimate pointer to AGENTS.md, which per the guidelines lets progressive disclosure score 3 on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

57%

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 and well-scoped to the IPTVnator repository with strong distinctiveness, but it lacks an explicit "Use when…" trigger and frames surfaces rather than concrete actions, capping completeness and trigger quality at 2. Adding a natural-language trigger clause would raise the weaker dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when changing user-visible Angular UI in IPTVnator — channel lists, EPG panels, settings, or shared components.'

Reframe surfaces as concrete actions (e.g. 'style', 'audit', 'align selection states') rather than naming only the areas touched.

Include common natural phrasings users would say, such as 'channel list styling', 'EPG panel layout', or 'settings page UI'.

DimensionReasoningScore

Specificity

Names the IPTVnator domain and several surfaces ("channel rows, EPG views, settings surfaces, shared selection styles, and light/dark theme consistency") but lists areas rather than concrete actions, matching the 'Names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

The description clearly states what the skill provides ("UI design guidance for IPTVnator…") but never gives an explicit "Use when…" trigger, so per the guidelines completeness is capped at 2 ('Has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Surface names like "channel rows", "EPG views", and "light/dark theme" are real domain terms a developer would say, but coverage of natural user phrasings is incomplete and there is no "Use when…" trigger, fitting 'Some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

It is tightly scoped to a single repository and specific UI surfaces ("Repository-specific UI design guidance for IPTVnator…"), making it a clear niche unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

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.

Repository
4gray/iptvnator
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.