SKILLEMALL.ai

BD mobile-limrun-dev

Launch and iterate on apps/mobile from a cloud sandbox (no local Xcode or simulator) using Limrun's remote iOS simulators. Use when asked to run, start, open, or show the mobile app from a cloud workspace, or to verify a mobile change there. On a machine with real Xcode, use mobile-sim-verification instead.

superset-sh/superset Agent Skills author: superset-sh NOASSERTION 1 file body ≈ 501 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Launch and iterate on apps/mobile from a cloud sandbox (no local Xcode or simulator) using Limrun's remote iOS simulators.

As a process D 42/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
D
42/100
Unfinished process
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 42/100

    • 0Steps. Prose only: no discrete steps
    • 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
    • 50When it triggers. No condition that starts the skill
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 501 tokens
    • 100Running it twice. Mutating operations check current state

    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)
    • +4Structure: 1 headings, hard to scan
    • +3No numbered steps or checklist
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 308: enough signal without eating the budget
    • +4Has examples (1 code blocks)

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