CtrlK
BlogDocsLog inGet started
Tessl Logo

extension-system-audit

Audit M3UAndroid extension APIs and runtime for host/plugin boundaries, classloader compatibility, manifest metadata assumptions, IPC/protobuf compatibility, and dependency leakage.

62

Quality

74%

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/extension-system-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 concise, well-structured audit playbook with concrete file references, an executable validation command, and a clear sequenced process; its main limitation is that audit checks read as goals rather than fully executable sub-steps, and no explicit fix-retry loop is given.

DimensionReasoningScore

Conciseness

The body is lean bullet-driven prose with no padding or explanation of concepts Claude already knows; every section (When To Use, Required Context, Audit Checks, Process, Validation, Output) earns its place, matching the lean-and-efficient anchor 5.

5 / 5

Actionability

Provides concrete file paths to read, a copy-paste gradle validation command, and specific audit checks, but the checks are framed as verification goals rather than fully executable step-by-step instructions, leaving minor gaps versus the fully-executable anchor 5.

4 / 5

Workflow Clarity

The Process section gives a clear 5-step sequence with an explicit Validation checkpoint and a fallback ('If unavailable, state compatibility risk'), but lacks an explicit validate-fix-retry feedback loop, so it sits at anchor 4 rather than 5; the destructive/batch cap does not apply since this is read-only inspection.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files needed and is organized into clearly signaled sections (When To Use, Required Context, Audit Checks, Process, Validation, Output), so per the simple-skill guidance it qualifies for the well-organized anchor 5.

5 / 5

Total

18

/

20

Passed

Description

62%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 distinctive and names a clear, concrete audit domain with several specific subjects, but it omits any 'Use when...' trigger guidance and relies on technical jargon without synonyms, which caps completeness and limits trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when changing extension APIs, plugin discovery, AIDL/protobuf contracts, or host/plugin dependency boundaries').

Include common synonyms or file-type cues users might say (e.g., 'plugin', '.aidl', '.proto') to broaden natural trigger coverage.

Vary the action verbs beyond the single 'Audit' to surface multiple distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain ('M3UAndroid extension APIs and runtime') and five concrete audit subjects (host/plugin boundaries, classloader compatibility, manifest metadata, IPC/protobuf, dependency leakage), but relies on a single action verb 'Audit' rather than multiple distinct actions, placing it just below the comprehensive multi-action anchor 5.

4 / 5

Completeness

Provides a clear 'what' (audit extension APIs and runtime for listed boundaries) but includes no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('extension', 'classloader', 'manifest', 'protobuf', 'IPC') but they lean technical and lack common synonyms or file extensions a user might naturally say, matching the anchor for some relevant keywords missing variations.

3 / 5

Distinctiveness Conflict Risk

Targets a highly specific niche (M3UAndroid extension system audit) with distinct triggers and minimal overlap risk with other skills, matching the clear-niche anchor.

5 / 5

Total

15

/

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.