CtrlK
BlogDocsLog inGet started
Tessl Logo

playback-pipeline-audit

Audit M3UAndroid playback flows for UI/engine/persistence boundaries, lifecycle cleanup, Media3 integration, casting, overlays, resume/autoplay behavior, and TV control risks.

72

Quality

91%

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

100%

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

A tight, well-structured audit playbook that is concise, actionable, and clearly sequenced with validation guidance, fully appropriate for a single-purpose review skill with no bundle files.

DimensionReasoningScore

Conciseness

Lean ~65-line body with no concept explanations Claude already knows; every section earns its place (When To Use, Required Context, Audit Checks, Process, Validation, Output).

3 / 3

Actionability

Provides concrete executable validation commands ('./gradlew :app:smartphone:compileDebugKotlin', ':app:tv:compileDebugKotlin') and a specific 5-step process; for an instruction/audit skill the guidance is concrete and actionable rather than vague.

3 / 3

Workflow Clarity

Process is a clear numbered sequence (map → trace → inspect → check phone/TV → cite evidence) with an explicit Validation section and a fallback ('If manual playback checks cannot be run, state the remaining behavior risk').

3 / 3

Progressive Disclosure

Well-organized into clearly labeled sections with no monolithic wall of text; the only referenced files are repo context files (AGENTS.md, docs/ai/playbacks/playbook) which are clearly signaled, and no bundle files exist to mis-navigate.

3 / 3

Total

12

/

12

Passed

Description

82%

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 specific, distinctive description with strong natural trigger terms, weakened only by the absence of an explicit 'Use when…' clause that would tell Claude when to invoke it.

Suggestions

Append an explicit trigger clause, e.g. 'Use when reviewing or changing Media3/ExoPlayer setup, playback controls, casting, resume/autoplay, overlays, or TV remote behavior in M3UAndroid.'

Lead with the primary action verb and short purpose, then keep the target list — this makes the 'what' instantly scannable before the detail.

DimensionReasoningScore

Specificity

Lists multiple concrete audit targets — 'UI/engine/persistence boundaries, lifecycle cleanup, Media3 integration, casting, overlays, resume/autoplay behavior, and TV control risks' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states WHAT it audits but lacks an explicit 'Use when…' trigger clause; per guidelines a missing explicit trigger caps completeness at 2, so it is not at 3.

2 / 3

Trigger Term Quality

Uses natural developer terms a user would say — 'playback', 'Media3', 'casting', 'overlays', 'resume/autoplay', 'TV control' — giving good coverage rather than abstract jargon.

3 / 3

Distinctiveness Conflict Risk

The 'M3UAndroid playback' audit niche with Media3/TV/casting triggers is a clear, distinct scope unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.