SKILLEMALL.ai
GitHub ↗ RU Sign in

BC limrun-expo-development

Prepare and run Expo / React Native apps on Limrun with Expo dev-client iteration. Use when the user wants an Expo dev build, Metro tunnel, hot reload, JS/TS iteration without repeated native rebuilds, or to run/test an Expo app on a remote iOS simulator or Android emulator.

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

Prepare and run Expo / React Native apps on Limrun with Expo dev-client iteration.

As a process C 60/100 · Has gaps — References files that are not bundled: <signedStreamUrl>

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
60/100
Has gaps
References files that are not bundled: <signedStreamUrl>
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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

  • warning missing-ref reference to a missing file: <signedStreamUrl>
  • note frontmatter-key unknown frontmatter key "effort"
  • note edit-residue the text marks something as outdated (lines 252): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 60/100

Will not run. References files that are not bundled: <signedStreamUrl>
  • 0Tools and files. 1 referenced file(s) missing: <signedStreamUrl>
  • 0Result and completion. Does not say what the result is
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 100Steps. 19 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3481 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 11 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 275: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (24 code blocks)

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