CtrlK
BlogDocsLog inGet started
Tessl Logo

m3u-epg-data-audit

Audit M3UAndroid M3U and EPG data flows for parser behavior, channel/programme matching, duplicate handling, fallback behavior, joins, and timezone/time-range correctness.

64

Quality

78%

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 ./.claude/skills/m3u-epg-data-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a tight, well-structured audit playbook with concrete steps and a validation recommendation, assuming Claude's intelligence throughout; its main gap is the absence of executable search/query examples and an explicit validate-fix-retry feedback loop.

Suggestions

Add one or two concrete example commands or grep patterns (e.g., a sample query to find channel/programme joins) to make the audit steps more directly executable.

Convert the Validation section from a recommendation into an explicit checkpoint with a fix-and-retry feedback loop (run tests -> if failures, locate and fix -> re-run).

Optionally link a fixture/test inventory or example malformed-playlist reference one level deep so the audit checks have concrete starting points.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept explanations or padding; every section (When To Use, Required Context, Audit Checks, Process, Validation, Output) earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides concrete actionable steps ("Map parser entry points", "Trace one normal playlist... and one empty/malformed guide path", "Cite file paths and line numbers") plus an executable validation command ("./gradlew :data:testDebugUnitTest"), but lacks example grep patterns or sample queries that would make guidance fully copy-paste ready.

4 / 5

Workflow Clarity

The Process section gives a clear 5-step sequence and a dedicated Validation section, but validation is framed as a recommendation rather than an enforced checkpoint with an explicit fix-and-retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with one-level-deep references to repo context files (AGENTS.md, docs/ai/playbooks/m3u-epg-data.md) and no nested references; for a sub-50-line skill this structure is appropriately navigable.

5 / 5

Total

18

/

20

Passed

Description

70%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 is specific and distinct, naming a clear niche and several concrete audit dimensions, but it omits any explicit "Use when..." trigger guidance, which caps completeness and leaves the activation conditions implicit.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., reviewing M3U/XMLTV/EPG parsing, channel-to-programme matching, or playlist-to-guide association).

Include common synonyms and file extensions users might say (playlist, guide, XMLTV, .m3u) to broaden trigger-term coverage.

Vary the action verbs beyond a single "Audit" to make the concrete capabilities (trace, verify, inspect joins, check timezones) more explicit.

DimensionReasoningScore

Specificity

Lists several concrete audit dimensions ("parser behavior, channel/programme matching, duplicate handling, fallback behavior, joins, and timezone/time-range correctness"), though all hang off a single verb "Audit" rather than multiple distinct action verbs, leaving minor coverage gaps.

4 / 5

Completeness

Has a clear "what" (audit M3U/EPG data flows for the listed behaviors) but no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good coverage of domain-natural terms ("M3U", "EPG", "parser", "channel/programme matching", "duplicate", "timezone"), but misses common synonyms a user might say such as "playlist", "guide", "XMLTV", or the .m3u extension.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (M3UAndroid M3U and EPG data flows) with distinct, domain-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
oxyroid/M3UAndroid
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.