SKILLEMALL.ai

BC android-native-dev

Android native application development and UI design guide. Covers Material Design 3, Kotlin/Compose development, project configuration, accessibility, and build troubleshooting. Read this before Android native application development.

ClawHub Agent Skills author: smasherlxd v1.0.0 MIT-0 11 files body ≈ 7 175 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

GeneratorInfrastructureDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
67
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 3 more places: ClawHub, ClawHub, ClawHub

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token references/testing.md:543
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    ./gradlew pixe…est
    fixture

Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 7175 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Execution cost. Instruction body is 7175 tokens
  • 85Steps. 37 steps, 2 vague phrases
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 235: enough signal without eating the budget
  • +4Structure: 49 headings
  • +3Step-by-step instructions: 37 items
  • +4Has examples (29 code blocks)
  • +4Reference files are cited in the instructions (9 of 9)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.

External checks

ClawHub: clean
This is a documentation-only Android development guide with standard, disclosed build and testing advice.
LLM: benign (high) · VirusTotal: · 29 May 2026