CtrlK
BlogDocsLog inGet started
Tessl Logo

xtream-electron

Use when changing Xtream routes, Signal Store or data sources, content identity, SQLite-backed import, search or delete, sparse VOD playback, or Electron and PWA behavior.

65

Quality

82%

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

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

An exemplary lean, project-specific contracts skill: dense with actionable rules, exact names, and concrete validation commands, with zero filler. The only gap is a missing validate-and-retry feedback loop for the SQLite worker operations it references.

DimensionReasoningScore

Conciseness

Every line carries non-obvious project-specific rules (ownership boundaries, ID conflations, capability gating); there is no padding and no explanation of concepts Claude already knows. This fits the 'lean and efficient; every token earns its place' anchor exactly.

5 / 5

Actionability

Fully concrete guidance: exact class/method names ('ElectronXtreamDataSource', 'RuntimeCapabilitiesService.supportsXtreamSqliteDataSource', 'XtreamStore'), exact library paths, and copy-paste validation commands like 'web-e2e:e2e-ci--src/xtream.e2e.ts'. As an instruction-only skill, the absence of code is not penalized because the guidance is specific and executable.

5 / 5

Workflow Clarity

A clear section sequence (Read First docs -> ownership -> contracts -> validation) with an explicit, concrete validation section, but there is no feedback loop (validate -> fix -> re-run) for the SQLite import/search/delete work the skill governs, so it falls short of anchor 5's 'explicit validation steps with error-recovery loops'.

4 / 5

Progressive Disclosure

A compact single-file skill with no bundle files to disclose; sections are well-organized and the 'Read First' list is a clearly signaled, one-level-deep set of pointers, matching the anchor for a clear overview with well-signaled references and easy navigation.

5 / 5

Total

19

/

20

Passed

Description

61%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 highly distinctive, specific trigger clause that would fire reliably for the right tasks, but it completely lacks a 'what' statement — the skill's actual capability is never described. Adding one sentence of what the skill provides (project structure, contracts, and validation guidance for Xtream changes) would lift it substantially.

Suggestions

Add an explicit 'what' statement before the 'Use when' clause, e.g. 'Guide for Xtream Electron app changes: ownership boundaries, data/navigation contracts, and validation flows.'

Include trigger terms for the other topics the body covers (favorites/recent, EPG, player, DB worker) so those changes also surface this skill.

Consider naming the primary artifacts (e.g. 'Xtream feature/data-access libraries') in the 'what' portion to make the capability concrete.

DimensionReasoningScore

Specificity

Names several concrete change-areas ('Signal Store or data sources', 'SQLite-backed import, search or delete', 'sparse VOD playback', 'Electron and PWA behavior'), which is well above anchor 3's 1-2 concrete actions, but the single generic verb 'changing' keeps it short of anchor 5's multiple distinct concrete actions.

4 / 5

Completeness

The description is solely a 'when' clause ('Use when changing...') with no statement of what the skill does, matching the anchor for 'only when present without what'; the 'when' is specific, but the 'what' is absent rather than merely implied, so anchor 3 does not fit.

2 / 5

Trigger Term Quality

Terms like 'Xtream routes', 'SQLite-backed import', 'VOD playback', and 'Electron and PWA' are exactly what a developer in this codebase would say, but no synonyms or variations appear and body-covered topics (favorites, EPG, player) lack trigger terms.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive terms ('Xtream', 'Signal Store', 'sparse VOD playback', 'Electron and PWA') carve out a clear niche with essentially no overlap risk against other skills.

5 / 5

Total

15

/

20

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.

Validation — 16 / 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.