CtrlK
BlogDocsLog inGet started
Tessl Logo

apk-size-audit

Audit M3UAndroid APK/AAB size and packaging changes for dependency growth, native libraries, resources, R8/minification, generated assets, baseline profiles, and artifact comparison evidence.

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/apk-size-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 concise, well-structured audit skill body with concrete process steps and a real validation command, hindered only slightly by descriptive rather than executable audit checks and external-only references.

Suggestions

Tighten audit checks into more executable form (e.g., specific grep/gradle commands to verify version-catalog usage or R8 config) to push actionability higher.

Add an explicit validate->fix->retry feedback loop for the assembleRelease step so workflow_clarity can reach the top anchor.

If the referenced docs exist in the repo, consider bundling the playbook into a reference file so progressive disclosure is self-contained.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude's competence with no padding or explanation of basic concepts, e.g. 'Audit packaging and size-sensitive changes with measurable artifact and configuration evidence.'

5 / 5

Actionability

Provides an executable validation command ('./gradlew :app:smartphone:assembleRelease') and a concrete numbered process, though several audit checks are descriptive verification cues rather than directly executable steps.

4 / 5

Workflow Clarity

A clear 5-step Process is sequenced with a Validation section and explicit command, plus a stated fallback ('If artifact comparison cannot be run, state the remaining size risk'); minor validation gaps keep it just below 5.

4 / 5

Progressive Disclosure

Well-organized sections with one-level-deep references signaled in Required Context (AGENTS.md, docs/ai/playbooks/apk-size.md, docs/native-load-yaml.md); no bundle files are provided, so references are external rather than bundled.

4 / 5

Total

17

/

20

Passed

Description

75%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 specific, well-scoped description that clearly states what the skill does and is highly distinct, but it lacks an explicit 'Use when...' trigger clause, capping its completeness.

Suggestions

Append an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when a change affects APK/AAB size, packaging, dependencies, native libraries, or release artifacts').

Add a few lay-friendly synonyms ('app size', 'install size', 'release build size') alongside the technical terms to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete audit areas ('dependency growth, native libraries, resources, R8/minification, generated assets, baseline profiles, and artifact comparison evidence'), giving comprehensive coverage of the skill's scope.

5 / 5

Completeness

The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Strong technical keyword coverage ('APK/AAB size', 'packaging changes', 'R8/minification', 'baseline profiles') that users would naturally say, though it leans technical and omits some lay synonyms.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ('M3UAndroid APK/AAB size and packaging changes') with distinct, specific triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

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.