SKILLEMALL.ai

AD appium-skill

Generates production-grade Appium mobile automation scripts for Android and iOS in Java, Python, or JavaScript. Supports real device and emulator testing locally and on TestMu AI cloud with 100+ real devices.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 2 688 tokens Open the sourcegithub.com analyzed 2 d ago

Generates production-grade Appium mobile automation scripts for Android and iOS in Java, Python, or JavaScript.

As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

    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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"
    • note edit-residue the text marks something as outdated (lines 257): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 49/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 9 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2688 tokens
    • low 10 top-level sections: this looks like several domains in one skill

    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
    • -2localhost URLs: will not work for another user
    • +2Single-language instructions
    • +3Description length 208: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 9 items
    • +4Has examples (11 code blocks)
    • +1License stated

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