CtrlK
BlogDocsLog inGet started
Tessl Logo

android-legacy-security

Harden Intent handling, WebView configuration, and FileProvider access in Android apps. Use when securing Intent extras, configuring WebViews, or exposing files via FileProvider; defer manifest export flags and generic Bundle typing to focused Android security guidance.

69

Quality

86%

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

72%Weight 40%Scale 1-3

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

A well-organized, concise hardening checklist with good progressive disclosure via a real one-level reference. Its weaknesses are the absence of inline executable code and any validation/verification workflow for applying the standards.

Suggestions

Add a short inline Kotlin/XML snippet or a concrete manifest fragment for at least one high-impact item (e.g. the FileProvider block) so the body is copy-paste ready without opening the reference.

Add an explicit verification step — e.g. 'Run a manifest audit to confirm no exported components remain' or a lint/checklist checkpoint — to turn the standards list into a sequenced, validated workflow.

De-duplicate WebView settings between the body and references/implementation.md (which repeats both 'WebView Hardening' and 'WebView Lockdown (Extended)') to avoid drift between the two locations.

DimensionReasoningScore

Conciseness

The body is lean — direct imperatives, no concept explanations Claude already knows (no 'what a WebView is' padding) — and stays under ~35 lines while offloading code to the reference, so every token earns its place.

3 / 3

Actionability

Names concrete flags and APIs ('android:exported="false"', 'javaScriptEnabled = false', 'allowFileAccessFromFileURLs', 'resolveActivity') but the fully executable code is deferred to references/implementation.md rather than presented inline, so guidance is concrete yet not copy-paste ready in the body.

2 / 3

Workflow Clarity

Standards are organized by P0 priority and numbered sections, but there is no sequenced multi-step workflow and no validation/verification checkpoints for the hardening changes, which leaves the sequence implicit.

2 / 3

Progressive Disclosure

The body is an overview pointing to a single one-level-deep reference (references/implementation.md, verified to exist) with clearly signaled links ('See [hardening examples](references/implementation.md)'), and content is appropriately split between summary and detail.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and complete with an explicit 'Use when' clause plus a defer boundary that sharpens its niche. It is concise without padding and unlikely to conflict with sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across three distinct domains — 'Harden Intent handling, WebView configuration, and FileProvider access' and 'securing Intent extras, configuring WebViews, or exposing files via FileProvider' — matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what ('Harden Intent handling, WebView configuration, and FileProvider access') and when via an explicit 'Use when securing Intent extras, configuring WebViews, or exposing files via FileProvider' clause.

3 / 3

Trigger Term Quality

Includes natural terms a developer would actually say — 'Intent extras', 'WebViews', 'FileProvider', 'exposing files via FileProvider' — with good coverage of the relevant vocabulary.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Android legacy security niche with distinct triggers, and the defer clause ('defer manifest export flags and generic Bundle typing to focused Android security guidance') further reduces overlap with adjacent skills.

3 / 3

Total

12

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.