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.

63

Quality

76%

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

85%

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

The body is concise, well-organized, and clearly sequenced with an explicit validation checkpoint and well-signaled context references, but several audit checks remain abstract rather than fully executable.

Suggestions

Make audit checks actionable by specifying what to look for and how, e.g. give example grep/glob patterns for forbidden imports or a concrete classloader rule to verify, rather than 'Inspect dependency declarations for forbidden direction or leakage'.

Optionally add a short expected-evidence template (e.g. the pass/fail table columns) so the Output guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and structured as terse bullet lists across focused sections (When To Use, Required Context, Audit Checks, Process, Validation, Output) with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides one concrete executable command ('./gradlew :core:extension:compileDebugKotlin :app:extension:compileDebugKotlin') and a fallback instruction, but most audit checks are abstract directives ('Inspect dependency declarations for forbidden direction or leakage') without defining what is forbidden or giving executable inspection steps, fitting 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

The Process section gives a clearly numbered 1–5 sequence and a dedicated Validation section with a concrete command plus a fallback ('If unavailable, state compatibility risk'), providing an explicit validation checkpoint above the 'sequence present but checkpoints missing' level 2; this is a read-only audit so a full fix-retry loop is not essential.

3 / 3

Progressive Disclosure

The skill is a concise, well-organized overview with clearly signaled one-level-deep references in 'Read first' (AGENTS.md, core/AGENTS.md, docs/ai/playbooks/extension-system.md) and no nested references; with no bundle files present, the well-structured sections satisfy the 'clear overview with well-signaled references' anchor.

3 / 3

Total

11

/

12

Passed

Description

67%

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 distinctive, naming concrete audit dimensions in third person, but it omits an explicit 'Use when...' trigger clause and leans on technical jargon over natural conversational terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing or changing M3UAndroid extension APIs, plugin loading, manifests, AIDL/protobuf contracts, or host/plugin dependencies.'

Broaden trigger terms with natural variations users might say (e.g. 'extension', 'plugin', 'manifest validation', 'compatibility check') to lift trigger-term quality to a 3.

DimensionReasoningScore

Specificity

The description lists multiple concrete audit targets — 'host/plugin boundaries', 'classloader compatibility', 'manifest metadata assumptions', 'IPC/protobuf compatibility, and dependency leakage' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly states what the skill does ('Audit M3UAndroid extension APIs and runtime for...') but has no 'Use when...' clause or equivalent trigger guidance, so per the rubric guideline a missing trigger clause caps completeness at 2 ('has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Relevant domain keywords (extension, plugin, manifest, classloader, protobuf, dependency) are present, but they are specialized jargon without common conversational variations and lack an explicit trigger phrase, fitting 'some relevant keywords but missing common variations' rather than the broad natural-term coverage of a 3.

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific (M3UAndroid extension system audit with named boundaries) making it unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor; it is well above the 'somewhat specific but could overlap' level 2.

3 / 3

Total

10

/

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.