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.

Quality

77%

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 ./.codex/skills/xtream-electron/SKILL.md

Quality

Content

76%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 lean, high-signal contracts reference that assumes Claude's competence and points outward to architecture docs for detail. Its weakness is workflow clarity: it reads as a reference rather than a sequenced procedure, with an explicit validation step but no fix-retry loop.

Suggestions

Add a short sequenced procedure (e.g. 1. Read the relevant docs/architecture file, 2. Apply the ownership/identity/runtime contracts, 3. Validate) so the implicit workflow becomes an explicit one.

Spell out a validate -> fix -> re-run feedback loop in the Validation section, since the skill covers database import/search/delete and batch operations where retry guidance matters.

Include one or two worked code snippets (e.g. the correct capability-gated ElectronXtreamDataSource selection, or a canonical Xtream identity key construction) to lift actionability from concrete rules to copy-paste-ready examples.

Dimension	Reasoning	Score
Conciseness	Lean and dense with no padding: it assumes Claude knows what Electron, SQLite, and Signal Store are, and every line carries project-specific contract value (e.g. 'A generic window.electron check is not the capability contract').	5 / 5
Actionability	Concrete, named guidance ('Select ElectronXtreamDataSource only through RuntimeCapabilitiesService.supportsXtreamSqliteDataSource', the operationId/requestId/sessionId distinction, and runnable e2e commands) is actionable, but as an instruction-only skill it lacks worked copy-paste examples that would reach 5.	4 / 5
Workflow Clarity	Organized as sectional contracts rather than a clearly sequenced multi-step workflow; a concrete validation checkpoint is present (run the listed specs/tests, which avoids the destructive/batch cap), but the process sequence is implicit and no fix-retry feedback loop is articulated.	3 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled one-level-deep 'Read First' pointer list to docs/architecture/*.md; the gap from 5 is that those references are external repo paths (not verifiable bundle files) and the in-skill contracts are inline rather than split across a bundle.	4 / 5
	Total	16 / 20 Passed

Description

78%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 tight, domain-specific description that pairs an explicit 'Use when' trigger with a concrete enumeration of the subsystems it covers. It is highly distinctive and broadly complete, held back only by a single generic action verb and some internal jargon.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete named subsystems ('Xtream routes, Signal Store or data sources, content identity, SQLite-backed import, search or delete, sparse VOD playback, Electron and PWA behavior') rather than vague abstractions, though the single action verb 'changing' keeps it just below a 5.	4 / 5
Completeness	An explicit 'Use when ...' clause gives strong trigger guidance (so it is not capped at 3) and the enumerated scope answers 'what', but the merged single-clause form conveys 'what' as change-scope rather than a crisp capability statement, leaving it just below a 5.	4 / 5
Trigger Term Quality	Good coverage of domain-natural terms a developer would actually say ('Xtream routes', 'VOD playback', 'Electron and PWA'), but it lacks synonyms/file extensions and leans on internal jargon like 'content identity' and 'sparse VOD', so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche built on highly specific triggers ('Xtream', 'Signal Store', 'sparse VOD playback') with minimal overlap risk against any other skill.	5 / 5
	Total	17 / 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: 4gray/iptvnator
Path: .codex/skills/xtream-electron/SKILL.md
Commit: 069b8b3

Reviewed: ~17 hours 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.