limrun-maestro-testing
Run Maestro Tests on Limrun iOS
Local iOS infrastructure limits Maestro testing across development and CI environments. This skill guides remote setup, execution, diagnosis, artifact capture, and cleanup through Limrun.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "limrun-maestro-testing" from https://skillstore.io/skills/limrun-inc-limrun-maestro-testing.md and its manifest at https://skillstore.io/api/skills/limrun-inc-limrun-maestro-testing/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "limrun-maestro-testing". Verify Maestro against the Settings app on a new Limrun iOS instance.
Expected outcome:
- The simulator was created with the Maestro runner available.
- The Settings flow completed and captured a screenshot.
- The remote driver connection is ready for application testing.
Using "limrun-maestro-testing". Explain why my text selector fails on the remote simulator.
Expected outcome:
The visible text differs from the accessibility label. Inspect the live element tree, then match the exact stable label.
Using "limrun-maestro-testing". Prepare my smoke suite for CI execution.
Expected outcome:
The suite uses an explicit instance, smoke tags, a dedicated artifact directory, optional recording, preserved exit codes, and final resource cleanup.
Security Audit
CriticalMost static alerts are Markdown formatting, protocol examples, instance identifiers, or defensive credential guidance. The curl-to-shell installer is a confirmed critical supply-chain risk. The workflow also transfers application builds and test activity to Limrun cloud infrastructure.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (3)
🔑 Env variables (1)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/limrun-inc-limrun-maestro-testing/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/limrun-inc-limrun-maestro-testing?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/limrun-inc-limrun-maestro-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/limrun-inc-limrun-maestro-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/limrun-inc-limrun-maestro-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
limrun-inc. (2026). limrun-maestro-testing security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/limrun-inc-limrun-maestro-testing/audits/1BibTeX citation
@techreport{limrun-inc-limrun-inc-limrun-maestro-testing-2026,
author = {limrun-inc},
title = {limrun-maestro-testing security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/limrun-inc-limrun-maestro-testing/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "limrun-maestro-testing security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "limrun-inc"
date-released: "2026-09-09"
url: "https://skillstore.io/skills/limrun-inc-limrun-maestro-testing/audits/1"
identifiers:
- type: other
value: "skillstore:limrun-inc-limrun-maestro-testing:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: LowWhat You Can Build
Validate mobile user journeys
Run repeatable Maestro flows on remote iOS simulators and inspect failures with screenshots and accessibility data.
Debug Expo interfaces
Open Expo projects on cloud simulators and refine selectors for stable iOS automation.
Move tests into CI
Target explicit simulator instances, preserve reports, record runs, and clean up resources after execution.
Try These Prompts
Verify my Limrun Maestro setup using the iOS Settings app, then explain each validation result.
Run the Maestro flow at [path] on iOS instance [id], preserve artifacts, and summarize failures.
Diagnose this failing Maestro selector using the live element tree and recommend a stable accessibility-based replacement: [failure].
Convert my Maestro suite at [path] for Limrun CI, including instance targeting, tagging, output directories, recording, and cleanup.
Best Practices
- Use explicit iOS instance identifiers in scripts and CI jobs.
- Anchor assertions on stable accessibility identifiers or exact labels.
- Use approved test builds, synthetic data, and scoped credentials on remote simulators.
Avoid
- Do not pipe remote installers directly into a shell without integrity verification.
- Do not pass driver or platform flags that Limrun manages automatically.
- Do not depend on fixed delays or unsupported local simulator file paths.
Frequently Asked Questions
Does this skill support Android testing?
Which Maestro versions are supported?
Can I use this in CI?
Does it support Expo applications?
Where are screenshots saved?
How should I handle secrets?
Developer Details
Author
limrun-incLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
367c7bb3962eb92a1b87fc08b2947aeda00cd51d
Maintenance freshness
9/9/2026
Usage
0 downloads · 0 views
File structure
📄 SKILL.md