[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWV56WRFE3CDKJFDFA6F9V":3,"skill-same:01M7AWV56WRFE3CDKJFDFA6F9V":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M7AWV56WRFE3CDKJFDFA6F9V","maestro-mobile-e2e",null,"Use when generating or running Maestro Mobile\u002FHybrid E2E flows, deriving Maestro YAML from BDD `.feature` scenarios, configuring Maestro report paths, or debugging Maestro iOS real-device runs.","KunoLu\u002Fsbtd-plugins","KunoLu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60886434?v=4","01M7AWBJNA6JJ6KBD84KR936JH","640","01M7AWBJP0V2KGW7VRBH4HY22M",195,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-agent-plugin\u002Fskills\u002Fmaestro-mobile-e2e\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-agent-plugin\u002Fskills\u002Fmaestro-mobile-e2e\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maestro-mobile-e2e\ndescription: Use when generating or running Maestro Mobile\u002FHybrid E2E flows,\n  deriving Maestro YAML from BDD `.feature` scenarios, configuring Maestro\n  report paths, or debugging Maestro iOS real-device runs.\nlicense: Apache-2.0\nallowed-tools: read grep glob bash\nmetadata:\n  sbtd.category: testing\n  sbtd.portable: \"true\"\n  sbtd.source-revision: 1d82494d74f6df9bca7dccef2da409f87091883e\ncompatibility: Requires Java 17+, Maestro CLI, a device, an app artifact, and\n  the scenario environment including account and backend prerequisites.\n---\n\n# Maestro Mobile E2E\n\nUse this Skill for Mobile \u002F Hybrid E2E work that uses Maestro.\n\nThis Skill does not replace `gherkin-bdd`, `project-validation`, task workflows, project tests, or human review. BDD `.feature` files are the behavior source of truth; Maestro flow YAML files are executable Mobile \u002F Hybrid E2E assets derived from selected BDD scenarios.\n\n## Workflow\n\n1. Confirm the task involves Android, iOS, React Native, Flutter, Hybrid App, mobile smoke, or cross-device user journeys.\n2. Read the relevant BDD `.feature` scenarios first. If no BDD scenario exists for user-visible behavior, return to `gherkin-bdd` before generating flow assets.\n3. Run the mobile context gate before generating or running flows.\n4. Decide whether the BDD scenario should become a Maestro flow. Use Maestro for device-level journeys, native permissions, deep links, system UI, mobile navigation, or Hybrid flows that cannot be covered reliably by Web E2E alone.\n5. Classify the run mode: `full-stack`, `contract-backed`, `app-mocked`, `smoke-only`, or `blocked`.\n6. Generate or update flow assets under `maestro\u002Fflow\u002F`.\n7. Before running Maestro, confirm Java 17+, Maestro CLI, target device \u002F simulator, app binary or installed app, bundle id \u002F app id, test account, and environment.\n8. Before any Maestro command that must generate a report, decide whether to use `rtk`. Formal report-producing runs default to native `maestro test` unless the project proves `rtk` is no-cache \u002F report-safe for that command.\n9. Run the smallest relevant flow first. Expand to platform smoke or full regression only after the targeted flow is stable.\n10. If an iOS real-device failure matches the known issue index, load the matching reference and apply only the relevant fix before rerunning the smallest failing flow.\n11. After failures are fixed and targeted reruns pass, run the planned final full validation and generate one final passing report plus one Markdown run summary.\n12. Report flow asset paths, commands, `rtk` decision, report files, artifacts location, blocked items, and remaining risk.\n13. For Cloud runs, wait for `get_cloud_run_status` to reach a terminal state before retrieving a specific per-flow run's diagnostic status or artifacts.\n\n## Mobile Context Gate\n\nBefore writing or running a flow, confirm:\n\n- Platform scope: `ios`, `android`, `both`, or `hybrid`.\n- App artifact: `.app`, `.ipa`, `.apk`, installed app, simulator \u002F emulator build, or cloud build.\n- App identity: iOS bundle id and \u002F or Android application id.\n- Target: iOS Simulator, iOS real device, Android Emulator, Android real device, or cloud device.\n- Backend dependency: live environment, mock environment, contract-only backend, or missing backend.\n- App launch control: base URL override, launch arguments, deep link, feature flags, clear-state strategy, and deterministic starting screen.\n- Data and accounts: test account, role, seed data, cleanup strategy, and environment isolation.\n- Selectors: stable accessibility identifiers, stable labels, platform differences, and WebView boundary strategy when applicable.\n- System capabilities: permissions, camera, photos, location, notifications, file picker, external app hops, OS dialogs, and native login.\n\nIf required context is missing, do not generate a fragile flow. Report `Maestro Flow Assets: blocked` and list the missing facts. Mock-backed or app-mocked flows are allowed only when behavior comes from a contract, real sample, existing fixture, launch argument, or explicit user confirmation; they must not be reported as full-stack E2E.\n\n## Flow Asset Contract\n\n- Store repo-resident Maestro flows in `maestro\u002Fflow\u002F`.\n- Use `.yml` extension.\n- Use English names for both file names and Maestro `name` fields.\n- Use lower-kebab-case file names for business scenarios, for example `maestro\u002Fflow\u002Flogin-success.yml`.\n- Use `maestro\u002Fflow\u002Fsmoke.yml` for the full regression \u002F smoke flow only.\n- When iOS and Android need materially different flows, use platform subdirectories such as `maestro\u002Fflow\u002Fios\u002Flogin-success.yml` and `maestro\u002Fflow\u002Fandroid\u002Flogin-success.yml`; platform smoke flows may use `maestro\u002Fflow\u002Fios\u002Fsmoke.yml` and `maestro\u002Fflow\u002Fandroid\u002Fsmoke.yml`.\n- Keep one maintainable flow per business scenario unless the project already has a stronger Maestro architecture.\n- Add a short trace comment near the top of generated flows that points back to the source BDD feature path, scenario name, platform scope, and run mode.\n- Do not generate fragile flows when stable selectors, deterministic data, app launch state, permissions, or test accounts are unavailable. Report `Maestro Flow Assets: blocked` with the missing prerequisite.\n\nExample flow header:\n\n```yaml\nappId: com.example.app\nname: Login Success\ntags:\n  - mobile\n  - smoke\n---\n# BDD: features\u002Fauthentication\u002Flogin.feature :: Scenario: 已注册用户使用正确密码登录\n# Platform: ios\n# Mode: full-stack\n- launchApp\n- tapOn: \"Email\"\n- inputText: \"${MAESTRO_TEST_EMAIL}\"\n- tapOn: \"Password\"\n- inputText: \"${MAESTRO_TEST_PASSWORD}\"\n- tapOn: \"Login\"\n- assertVisible: \"Home\"\n```\n\n## BDD To Flow Mapping\n\n- Map `Given` to deterministic app state, fixtures, launch arguments, deep links, or setup steps.\n- Map `When` to user actions such as `tapOn`, `inputText`, `scrollUntilVisible`, `back`, `swipe`, or nested subflows.\n- Map `Then` to visible, accessible, persisted, or emitted outcomes such as `assertVisible`, `assertNotVisible`, or stable post-action screen state.\n- Prefer accessibility identifiers and stable user-visible labels. If the app lacks stable selectors for critical controls, propose the minimal selector addition and stop unless the user has approved product code changes.\n- Keep secrets out of flow files. Use environment variables or project-approved test secret injection.\n- Use nested flows only when they remove real duplication and remain readable.\n\n## Report Contract\n\nWhen a planned Maestro validation run executes, it must request a native report with `--format` \u002F `--output` or the project's equivalent reporter unless prerequisites are blocked before the runner can start. Write a named native report under `.maestro\u002Freports\u002F` in the project root, plus one Markdown run summary with the same stem, branch slug, and timestamp. Do this even when the flow fails or the final full rerun is blocked by environment.\n\nBecause Maestro report generation depends on file side effects, formal Mobile \u002F Hybrid E2E runs must not blindly use `rtk`. Prefer native `maestro test` for any run that writes `.xml`, `.html`, trace, artifact, or Markdown evidence. If `rtk` was used for a Maestro command, verify that the expected report file exists, its mtime \u002F size changed during this run, and the contents match the flow that just executed. If the file is missing, stale, empty, mismatched, or `rtk` output suggests cache hit \u002F replay \u002F skipped write, rerun the same scope with native `maestro test` and treat the native result as authoritative.\n\nDebugging and targeted reruns may use stdout only, but stdout-only runs never satisfy the final formal report gate. If a debugging or targeted rerun does produce a native report, preserve it as a timestamped report snapshot before running another Maestro command that might overwrite or clean the same output. Multiple local report snapshots are allowed across rounds; the final result is still the last planned full rerun status. If the last useful run was stdout-only and Mobile \u002F Hybrid E2E remains in formal validation scope, rerun the planned scope with a native reporter or mark `Final Test Report` and `Run Summary MD` as blocked.\n\nUse this timestamp shape in local time:\n\n```text\nYYYY_mm_dd-HH_MM_SS\n```\n\nUse `branch_slug` for the current branch segment in report file names. Prefer the current git branch or the project \u002F CI branch ref; use `detached-{short_sha}` for detached HEAD and `unknown-branch` when no git context exists. Preserve only letters, digits, `.`, `_`, and `-`; replace `\u002F`, spaces, and other special characters with `_`. Record the raw branch and `branch_slug` in the Markdown summary.\n\nReport file names:\n\n```text\n.maestro\u002Freports\u002Fmaestro-report-{flow_name}-{branch_slug}-{YYYY_mm_dd}-{HH_MM_SS}.xml\n.maestro\u002Freports\u002Fmaestro-report-{flow_name}-{branch_slug}-{YYYY_mm_dd}-{HH_MM_SS}.html\n.maestro\u002Freports\u002Fmaestro-report-{flow_name}-{branch_slug}-{YYYY_mm_dd}-{HH_MM_SS}.md\n```\n\n`flow_name` is the flow file stem, such as `login-success` or `smoke`. Keep `flow_name` in the report file name even when the flow is derived from a BDD `.feature`; the Markdown summary records the source `.feature` path and scenario name.\n\nExample commands:\n\n```bash\nmkdir -p .maestro\u002Freports\nflow=maestro\u002Fflow\u002Flogin-success.yml\nflow_name=$(basename \"$flow\" .yml)\nraw_branch=${GITHUB_HEAD_REF:-${GITHUB_REF_NAME:-}}\nif [ -z \"$raw_branch\" ]; then\n  raw_branch=$(git branch --show-current 2>\u002Fdev\u002Fnull || true)\nfi\nif [ -z \"$raw_branch\" ]; then\n  short_sha=$(git rev-parse --short HEAD 2>\u002Fdev\u002Fnull || true)\n  if [ -n \"$short_sha\" ]; then\n    raw_branch=\"detached-${short_sha}\"\n  else\n    raw_branch=\"unknown-branch\"\n  fi\nfi\nbranch_slug=$(printf \"%s\" \"$raw_branch\" | LC_ALL=C tr -cs 'A-Za-z0-9._-' '_' | sed 's\u002F^_*\u002F\u002F; s\u002F_*$\u002F\u002F')\nbranch_slug=${branch_slug:-unknown-branch}\nstamp=$(date +%Y_%m_%d-%H_%M_%S)\nmaestro test --format junit --output \".maestro\u002Freports\u002Fmaestro-report-${flow_name}-${branch_slug}-${stamp}.xml\" \"$flow\"\n```\n\nUse the project-required native reporter. Default to JUnit when CI needs machine-readable output; use HTML only when the project or user asks for human-readable local reports. Prefer writing directly to the branch-and-timestamped report file. If a project wrapper can only emit into a fixed or runner-managed output directory, use `.maestro\u002Freports\u002F.maestro-current\u002F` as the temporary output and copy or rename the result to `maestro-report-{flow_name}-{branch_slug}-{timestamp}` before the next Maestro run. Do not treat `~\u002F.maestro\u002Ftests`, `.maestro-current\u002F`, or a fixed `report.xml` \u002F `report.html` path as the formal preserved report.\n\nIf project configuration forces multiple reporters, treat them as one report set from the same run, and still generate only one Markdown summary for that report set. If Maestro CLI never produces a native report because prerequisites are blocked, the runner crashes before reporting, or the only executed command was stdout-only, mark the report and summary as blocked instead of claiming generation.\n\nThe Markdown summary must be written in Chinese. Status enum values, commands, file paths, case \u002F flow names, raw error messages, and technical identifiers may remain in English. The summary must include platform scope, run mode, mock strategy, raw branch, `branch_slug`, executed case \u002F flow list, source `.feature` path and scenario name for each flow, final report path, total rounds, each round command, failed case \u002F flow, failure classification, fix summary, changed files, targeted rerun result, affected subset rerun result, final full rerun result, skipped items, and remaining risk. When the report is intended as PR or knowledge-base evidence, also include evidence source, repository key, raw source ref, full commit SHA, worktree state, source revision, trigger, environment alignment, publication status, and the evidence sidecar \u002F envelope path defined by `project-validation\u002Freferences\u002Fvalidation-evidence-contract.md`. `branch_slug` is not revision identity. Do not include real accounts, secrets, PII, production data, full tokens, sensitive headers, or production screenshots.\n\nLoad the installed `project-validation\u002Freferences\u002Frun-summary.zh-CN.md.template` before writing the summary. Keep its fixed section order, populate results from the native artifact, and apply its generated-summary checks; use a device\u002Fplatform appendix when needed. A retained historical run may only be reformatted as a separate labeled preview, never silently rewritten or presented as a fresh run.\n\nFor PR or knowledge-base evidence, generate a same-report-stem `.evidence.json` or reference a cross-tool evidence envelope. Generic report evidence may use the project-validation v1 schema. Scenario-backed execution evidence is valid only as v2: the Maestro JUnit testcase must carry an extractable `sbtd.sourceLocatorDigest` property that equals the recomputed source locator, and the envelope must pass `scripts\u002Fvalidate_validation_evidence.py` from the installed `project-validation` Skill root, not this Maestro Skill directory. If the current Maestro reporter or adapter cannot emit that property, keep the human-readable report and mark v2 scenario execution evidence `blocked`. Do not fabricate a link. A dirty developer worktree remains `local-only`; knowledge-server runs require an exact revision set. Ordinary local Maestro diagnostics do not require an evidence sidecar.\n\n## Cloud Run Diagnostics\n\nFor a Cloud upload, retain the `upload_id` and `project_id` returned by `run_on_cloud`, and poll `get_cloud_run_status` until the upload is terminal. When a failing or warned flow provides its per-flow `run_id`, use `describe_cloud_run` to inspect that run's status and diagnostic artifacts.\n\nRead the default individual artifacts first. Request the complete artifact archive only when screenshots or failed-step view hierarchies are necessary, because archive URLs are short-lived. Record artifact links or paths as diagnostic evidence only; the Cloud result and its artifacts do not replace the planned native report, same-stem Chinese run summary, or final rerun status.\n\n## Failure Rerun Loop\n\nOn failure:\n\n1. Classify the failure as app code, test code, BDD \u002F spec, mock \u002F contract drift, environment \u002F account \u002F data \u002F device, flaky \u002F timing, or out-of-scope.\n2. If the issue is in scope and fixable, apply the smallest fix.\n3. Rerun the failed flow first.\n4. After the failed flow passes, rerun the affected platform subset, such as the same platform smoke flow or related business flow.\n5. Run the planned final full validation attempt, then generate the named native report and Chinese Markdown summary from that final attempted run whenever Maestro produced a native report, even if the flow failed.\n6. If fail-fast stopped on the first failure, do not assume later flows passed; continue with unrun flows or rerun the planned final validation.\n\nMaestro runtime artifacts still default outside the repository under `~\u002F.maestro\u002Ftests` on macOS \u002F Linux unless the command or project config overrides the output directory. Do not treat `~\u002F.maestro\u002Ftests` as a repo asset.\n\n## Known Issue Index\n\nKnown issue references are lazily loaded. Do not read reference files preemptively.\n\nRead `references\u002Flessons-index.md` only when a Maestro run, setup, or device inspection fails. Then load the referenced file only if tags, keywords, error messages, platform, or version match the current failure.\n\nCurrent reference topics include:\n\n- iOS real-device setup and Maestro 2.6.1 driver issues.\n\n## Output\n\nReport:\n\n- `Maestro Flow Assets`: `generated` \u002F `reused` \u002F `blocked` \u002F `skipped`.\n- `Mobile Platform Scope`: `ios` \u002F `android` \u002F `both` \u002F `hybrid` \u002F `not-needed`.\n- `Mobile E2E Mode`: `full-stack` \u002F `contract-backed` \u002F `app-mocked` \u002F `smoke-only` \u002F `blocked`.\n- `Mock Strategy`: `none` \u002F `contract-backed` \u002F `user-approved` \u002F `blocked`.\n- Flow files created or updated under `maestro\u002Fflow\u002F`.\n- Source `.feature` paths and scenario names traced by each flow.\n- Maestro CLI \u002F MCP \u002F Java \u002F device status.\n- Commands run and whether reports were generated.\n- `rtk`: `used` \u002F `skipped-for-report` \u002F `fallback-native` \u002F `not-available` \u002F `not-needed`, with reason.\n- Report paths under `.maestro\u002Freports\u002F`.\n- `Run Summary MD`: Chinese Markdown run summary path under `.maestro\u002Freports\u002F`.\n- `Evidence Source`: `developer-local` \u002F `ci` \u002F `knowledge-server` \u002F `not-needed`.\n- `Source Revision`: `exact` \u002F `dirty` \u002F `unknown` \u002F `not-needed`.\n- `Environment Alignment`: `verified` \u002F `unverified` \u002F `mismatch` \u002F `not-needed`.\n- `Evidence Publication`: `local-only` \u002F `published` \u002F `blocked` \u002F `not-configured` \u002F `not-needed`.\n- Evidence sidecar \u002F envelope path when the report is used by a PR or knowledge base.\n- Targeted rerun, affected subset rerun, and final full rerun results.\n- Runtime artifact location, usually `~\u002F.maestro\u002Ftests`.\n- Known issue reference loaded, fix applied, restore command if a tool patch was made, and rerun result.\n- Remaining manual setup, account, environment, selector, device, signing, or toolchain risks.\n","# Maestro Mobile E2E\n\nUse this Skill for Mobile \u002F Hybrid E2E work that uses Maestro.\n\nThis Skill does not replace `gherkin-bdd`, `project-validation`, task workflows, project tests, or human review. BDD `.feature` files are the behavior source of truth; Maestro flow YAML files are executable Mobile \u002F Hybrid E2E assets derived from selected BDD scenarios.\n\n## Workflow\n\n1. Confirm the task involves Android, iOS, React Native, Flutter, Hybrid App, mobile smoke, or cross-device user journeys.\n2. Read the relevant BDD `.feature` scenarios first. If no BDD scenario exists for user-visible behavior, return to `gherkin-bdd` before generating flow assets.\n3. Run the mobile context gate before generating or running flows.\n4. Decide whether the BDD scenario should become a Maestro flow. Use Maestro for device-level journeys, native permissions, deep links, system UI, mobile navigation, or Hybrid flows that cannot be covered reliably by Web E2E alone.\n5. Classify the run mode: `full-stack`, `contract-backed`, `app-mocked`, `smoke-only`, or `blocked`.\n6. Generate or update flow assets under `maestro\u002Fflow\u002F`.\n7. Before running Maestro, confirm Java 17+, Maestro CLI, target device \u002F simulator, app binary or installed app, bundle id \u002F app id, test account, and environment.\n8. Before any Maestro command that must generate a report, decide whether to use `rtk`. Formal report-producing runs default to native `maestro test` unless the project proves `rtk` is no-cache \u002F report-safe for that command.\n9. Run the smallest relevant flow first. Expand to platform smoke or full regression only after the targeted flow is stable.\n10. If an iOS real-device failure matches the known issue index, load the matching reference and apply only the relevant fix before rerunning the smallest failing flow.\n11. After failures are fixed and targeted reruns pass, run the planned final full validation and generate one final passing report plus one Markdown run summary.\n12. Report flow asset paths, commands, `rtk` decision, report files, artifacts location, blocked items, and remaining risk.\n13. For Cloud runs, wait for `get_cloud_run_status` to reach a terminal state before retrieving a specific per-flow run's diagnostic status or artifacts.\n\n## Mobile Context Gate\n\nBefore writing or running a flow, confirm:\n\n- Platform scope: `ios`, `android`, `both`, or `hybrid`.\n- App artifact: `.app`, `.ipa`, `.apk`, installed app, simulator \u002F emulator build, or cloud build.\n- App identity: iOS bundle id and \u002F or Android application id.\n- Target: iOS Simulator, iOS real device, Android Emulator, Android real device, or cloud device.\n- Backend dependency: live environment, mock environment, contract-only backend, or missing backend.\n- App launch control: base URL override, launch arguments, deep link, feature flags, clear-state strategy, and deterministic starting screen.\n- Data and accounts: test account, role, seed data, cleanup strategy, and environment isolation.\n- Selectors: stable accessibility identifiers, stable labels, platform differences, and WebView boundary strategy when applicable.\n- System capabilities: permissions, camera, photos, location, notifications, file picker, external app hops, OS dialogs, and native login.\n\nIf required context is missing, do not generate a fragile flow. Report `Maestro Flow Assets: blocked` and list the missing facts. Mock-backed or app-mocked flows are allowed only when behavior comes from a contract, real sample, existing fixture, launch argument, or explicit user confirmation; they must not be reported as full-stack E2E.\n\n## Flow Asset Contract\n\n- Store repo-resident Maestro flows in `maestro\u002Fflow\u002F`.\n- Use `.yml` extension.\n- Use English names for both file names and Maestro `name` fields.\n- Use lower-kebab-case file names for business scenarios, for example `maestro\u002Fflow\u002Flogin-success.yml`.\n- Use `maestro\u002Fflow\u002Fsmoke.yml` for the full regression \u002F smoke flow only.\n- When iOS and Android need materially different flows, use platform subdirectories such as `maestro\u002Fflow\u002Fios\u002Flogin-success.yml` and `maestro\u002Fflow\u002Fandroid\u002Flogin-success.yml`; platform smoke flows may use `maestro\u002Fflow\u002Fios\u002Fsmoke.yml` and `maestro\u002Fflow\u002Fandroid\u002Fsmoke.yml`.\n- Keep one maintainable flow per business scenario unless the project already has a stronger Maestro architecture.\n- Add a short trace comment near the top of generated flows that points back to the source BDD feature path, scenario name, platform scope, and run mode.\n- Do not generate fragile flows when stable selectors, deterministic data, app launch state, permissions, or test accounts are unavailable. Report `Maestro Flow Assets: blocked` with the missing prerequisite.\n\nExample flow header:\n\n```yaml\nappId: com.example.app\nname: Login Success\ntags:\n  - mobile\n  - smoke\n---\n# BDD: features\u002Fauthentication\u002Flogin.feature :: Scenario: 已注册用户使用正确密码登录\n# Platform: ios\n# Mode: full-stack\n- launchApp\n- tapOn: \"Email\"\n- inputText: \"${MAESTRO_TEST_EMAIL}\"\n- tapOn: \"Password\"\n- inputText: \"${MAESTRO_TEST_PASSWORD}\"\n- tapOn: \"Login\"\n- assertVisible: \"Home\"\n```\n\n## BDD To Flow Mapping\n\n- Map `Given` to deterministic app state, fixtures, launch arguments, deep links, or setup steps.\n- Map `When` to user actions such as `tapOn`, `inputText`, `scrollUntilVisible`, `back`, `swipe`, or nested subflows.\n- Map `Then` to visible, accessible, persisted, or emitted outcomes such as `assertVisible`, `assertNotVisible`, or stable post-action screen state.\n- Prefer accessibility identifiers and stable user-visible labels. If the app lacks stable selectors for critical controls, propose the minimal selector addition and stop unless the user has approved product code changes.\n- Keep secrets out of flow files. Use environment variables or project-approved test secret injection.\n- Use nested flows only when they remove real duplication and remain readable.\n\n## Report Contract\n\nWhen a planned Maestro validation run executes, it must request a native report with `--format` \u002F `--output` or the project's equivalent reporter unless prerequisites are blocked before the runner can start. Write a named native report under `.maestro\u002Freports\u002F` in the project root, plus one Markdown run summary with the same stem, branch slug, and timestamp. Do this even when the flow fails or the final full rerun is blocked by environment.\n\nBecause Maestro report generation depends on file side effects, formal Mobile \u002F Hybrid E2E runs must not blindly use `rtk`. Prefer native `maestro test` for any run that writes `.xml`, `.html`, trace, artifact, or Markdown evidence. If `rtk` was used for a Maestro command, verify that the expected report file exists, its mtime \u002F size changed during this run, and the contents match the flow that just executed. If the file is missing, stale, empty, mismatched, or `rtk` output suggests cache hit \u002F replay \u002F skipped write, rerun the same scope with native `maestro test` and treat the native result as authoritative.\n\nDebugging and targeted reruns may use stdout only, but stdout-only runs never satisfy the final formal report gate. If a debugging or targeted rerun does produce a native report, preserve it as a timestamped report snapshot before running another Maestro command that might overwrite or clean the same output. Multiple local report snapshots are allowed across rounds; the final result is still the last planned full rerun status. If the last useful run was stdout-only and Mobile \u002F Hybrid E2E remains in formal validation scope, rerun the planned scope with a native reporter or mark `Final Test Report` and `Run Summary MD` as blocked.\n\nUse this timestamp shape in local time:\n\n```text\nYYYY_mm_dd-HH_MM_SS\n```\n\nUse `branch_slug` for the current branch segment in report file names. Prefer the current git branch or the project \u002F CI branch ref; use `detached-{short_sha}` for detached HEAD and `unknown-branch` when no git context exists. Preserve only letters, digits, `.`, `_`, and `-`; replace `\u002F`, spaces, and other special characters with `_`. Record the raw branch and `branch_slug` in the Markdown summary.\n\nReport file names:\n\n```text\n.maestro\u002Freports\u002Fmaestro-report-{flow_name}-{branch_slug}-{YYYY_mm_dd}-{HH_MM_SS}.xml\n.maestro\u002Freports\u002Fmaestro-report-{flow_name}-{branch_slug}-{YYYY_mm_dd}-{HH_MM_SS}.html\n.maestro\u002Freports\u002Fmaestro-report-{flow_name}-{branch_slug}-{YYYY_mm_dd}-{HH_MM_SS}.md\n```\n\n`flow_name` is the flow file stem, such as `login-success` or `smoke`. Keep `flow_name` in the report file name even when the flow is derived from a BDD `.feature`; the Markdown summary records the source `.feature` path and scenario name.\n\nExample commands:\n\n```bash\nmkdir -p .maestro\u002Freports\nflow=maestro\u002Fflow\u002Flogin-success.yml\nflow_name=$(basename \"$flow\" .yml)\nraw_branch=${GITHUB_HEAD_REF:-${GITHUB_REF_NAME:-}}\nif [ -z \"$raw_branch\" ]; then\n  raw_branch=$(git branch --show-current 2>\u002Fdev\u002Fnull || true)\nfi\nif [ -z \"$raw_branch\" ]; then\n  short_sha=$(git rev-parse --short HEAD 2>\u002Fdev\u002Fnull || true)\n  if [ -n \"$short_sha\" ]; then\n    raw_branch=\"detached-${short_sha}\"\n  else\n    raw_branch=\"unknown-branch\"\n  fi\nfi\nbranch_slug=$(printf \"%s\" \"$raw_branch\" | LC_ALL=C tr -cs 'A-Za-z0-9._-' '_' | sed 's\u002F^_*\u002F\u002F; s\u002F_*$\u002F\u002F')\nbranch_slug=${branch_slug:-unknown-branch}\nstamp=$(date +%Y_%m_%d-%H_%M_%S)\nmaestro test --format junit --output \".maestro\u002Freports\u002Fmaestro-report-${flow_name}-${branch_slug}-${stamp}.xml\" \"$flow\"\n```\n\nUse the project-required native reporter. Default to JUnit when CI needs machine-readable output; use HTML only when the project or user asks for human-readable local reports. Prefer writing directly to the branch-and-timestamped report file. If a project wrapper can only emit into a fixed or runner-managed output directory, use `.maestro\u002Freports\u002F.maestro-current\u002F` as the temporary output and copy or rename the result to `maestro-report-{flow_name}-{branch_slug}-{timestamp}` before the next Maestro run. Do not treat `~\u002F.maestro\u002Ftests`, `.maestro-current\u002F`, or a fixed `report.xml` \u002F `report.html` path as the formal preserved report.\n\nIf project configuration forces multiple reporters, treat them as one report set from the same run, and still generate only one Markdown summary for that report set. If Maestro CLI never produces a native report because prerequisites are blocked, the runner crashes before reporting, or the only executed command was stdout-only, mark the report and summary as blocked instead of claiming generation.\n\nThe Markdown summary must be written in Chinese. Status enum values, commands, file paths, case \u002F flow names, raw error messages, and technical identifiers may remain in English. The summary must include platform scope, run mode, mock strategy, raw branch, `branch_slug`, executed case \u002F flow list, source `.feature` path and scenario name for each flow, final report path, total rounds, each round command, failed case \u002F flow, failure classification, fix summary, changed files, targeted rerun result, affected subset rerun result, final full rerun result, skipped items, and remaining risk. When the report is intended as PR or knowledge-base evidence, also include evidence source, repository key, raw source ref, full commit SHA, worktree state, source revision, trigger, environment alignment, publication status, and the evidence sidecar \u002F envelope path defined by `project-validation\u002Freferences\u002Fvalidation-evidence-contract.md`. `branch_slug` is not revision identity. Do not include real accounts, secrets, PII, production data, full tokens, sensitive headers, or production screenshots.\n\nLoad the installed `project-validation\u002Freferences\u002Frun-summary.zh-CN.md.template` before writing the summary. Keep its fixed section order, populate results from the native artifact, and apply its generated-summary checks; use a device\u002Fplatform appendix when needed. A retained historical run may only be reformatted as a separate labeled preview, never silently rewritten or presented as a fresh run.\n\nFor PR or knowledge-base evidence, generate a same-report-stem `.evidence.json` or reference a cross-tool evidence envelope. Generic report evidence may use the project-validation v1 schema. Scenario-backed execution evidence is valid only as v2: the Maestro JUnit testcase must carry an extractable `sbtd.sourceLocatorDigest` property that equals the recomputed source locator, and the envelope must pass `scripts\u002Fvalidate_validation_evidence.py` from the installed `project-validation` Skill root, not this Maestro Skill directory. If the current Maestro reporter or adapter cannot emit that property, keep the human-readable report and mark v2 scenario execution evidence `blocked`. Do not fabricate a link. A dirty developer worktree remains `local-only`; knowledge-server runs require an exact revision set. Ordinary local Maestro diagnostics do not require an evidence sidecar.\n\n## Cloud Run Diagnostics\n\nFor a Cloud upload, retain the `upload_id` and `project_id` returned by `run_on_cloud`, and poll `get_cloud_run_status` until the upload is terminal. When a failing or warned flow provides its per-flow `run_id`, use `describe_cloud_run` to inspect that run's status and diagnostic artifacts.\n\nRead the default individual artifacts first. Request the complete artifact archive only when screenshots or failed-step view hierarchies are necessary, because archive URLs are short-lived. Record artifact links or paths as diagnostic evidence only; the Cloud result and its artifacts do not replace the planned native report, same-stem Chinese run summary, or final rerun status.\n\n## Failure Rerun Loop\n\nOn failure:\n\n1. Classify the failure as app code, test code, BDD \u002F spec, mock \u002F contract drift, environment \u002F account \u002F data \u002F device, flaky \u002F timing, or out-of-scope.\n2. If the issue is in scope and fixable, apply the smallest fix.\n3. Rerun the failed flow first.\n4. After the failed flow passes, rerun the affected platform subset, such as the same platform smoke flow or related business flow.\n5. Run the planned final full validation attempt, then generate the named native report and Chinese Markdown summary from that final attempted run whenever Maestro produced a native report, even if the flow failed.\n6. If fail-fast stopped on the first failure, do not assume later flows passed; continue with unrun flows or rerun the planned final validation.\n\nMaestro runtime artifacts still default outside the repository under `~\u002F.maestro\u002Ftests` on macOS \u002F Linux unless the command or project config overrides the output directory. Do not treat `~\u002F.maestro\u002Ftests` as a repo asset.\n\n## Known Issue Index\n\nKnown issue references are lazily loaded. Do not read reference files preemptively.\n\nRead `references\u002Flessons-index.md` only when a Maestro run, setup, or device inspection fails. Then load the referenced file only if tags, keywords, error messages, platform, or version match the current failure.\n\nCurrent reference topics include:\n\n- iOS real-device setup and Maestro 2.6.1 driver issues.\n\n## Output\n\nReport:\n\n- `Maestro Flow Assets`: `generated` \u002F `reused` \u002F `blocked` \u002F `skipped`.\n- `Mobile Platform Scope`: `ios` \u002F `android` \u002F `both` \u002F `hybrid` \u002F `not-needed`.\n- `Mobile E2E Mode`: `full-stack` \u002F `contract-backed` \u002F `app-mocked` \u002F `smoke-only` \u002F `blocked`.\n- `Mock Strategy`: `none` \u002F `contract-backed` \u002F `user-approved` \u002F `blocked`.\n- Flow files created or updated under `maestro\u002Fflow\u002F`.\n- Source `.feature` paths and scenario names traced by each flow.\n- Maestro CLI \u002F MCP \u002F Java \u002F device status.\n- Commands run and whether reports were generated.\n- `rtk`: `used` \u002F `skipped-for-report` \u002F `fallback-native` \u002F `not-available` \u002F `not-needed`, with reason.\n- Report paths under `.maestro\u002Freports\u002F`.\n- `Run Summary MD`: Chinese Markdown run summary path under `.maestro\u002Freports\u002F`.\n- `Evidence Source`: `developer-local` \u002F `ci` \u002F `knowledge-server` \u002F `not-needed`.\n- `Source Revision`: `exact` \u002F `dirty` \u002F `unknown` \u002F `not-needed`.\n- `Environment Alignment`: `verified` \u002F `unverified` \u002F `mismatch` \u002F `not-needed`.\n- `Evidence Publication`: `local-only` \u002F `published` \u002F `blocked` \u002F `not-configured` \u002F `not-needed`.\n- Evidence sidecar \u002F envelope path when the report is used by a PR or knowledge base.\n- Targeted rerun, affected subset rerun, and final full rerun results.\n- Runtime artifact location, usually `~\u002F.maestro\u002Ftests`.\n- Known issue reference loaded, fix applied, restore command if a tool patch was made, and rerun result.\n- Remaining manual setup, account, environment, selector, device, signing, or toolchain risks.\n",{"name":5,"license":15,"metadata":25,"description":7,"allowed-tools":29,"compatibility":30},{"sbtd.category":26,"sbtd.portable":27,"sbtd.source-revision":28},"testing","true","1d82494d74f6df9bca7dccef2da409f87091883e","read grep glob bash","Requires Java 17+, Maestro CLI, a device, an app artifact, and the scenario environment including account and backend prerequisites.","main","0d9331bd7d64c28dea368fd4385fd009809d58da","packages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-agent-plugin\u002Fskills\u002Fmaestro-mobile-e2e",1,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins","https:\u002F\u002Fgithub.com\u002FKunoLu","2026-11-05 11:57:54",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add KunoLu\u002Fsbtd-plugins --skill maestro-mobile-e2e",{"tool":44,"command":45},"bunx","bunx skills add KunoLu\u002Fsbtd-plugins --skill maestro-mobile-e2e",{"tool":47,"command":48},"pnpm","pnpm dlx skills add KunoLu\u002Fsbtd-plugins --skill maestro-mobile-e2e","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-agent-plugin\u002Fskills\u002Fmaestro-mobile-e2e\u002FSKILL.md",true,[52,56,62,68],{"path":53,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"NOTICE","OTHER","其他",720,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-agent-plugin\u002Fskills\u002Fmaestro-mobile-e2e\u002FNOTICE",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fios-real-device-setup.md","REFERENCE","参考文档",4864,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-agent-plugin\u002Fskills\u002Fmaestro-mobile-e2e\u002Freferences\u002Fios-real-device-setup.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Flessons-index.md",794,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-agent-plugin\u002Fskills\u002Fmaestro-mobile-e2e\u002Freferences\u002Flessons-index.md",[73,80,87,95,103,111],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":20},"01M7AX886G1MY416H73C125QZY","gherkin-bdd","Use when adding, changing, reviewing, testing, synchronizing, or read-only ingesting user-visible behavior with BDD, Gherkin, Given\u002FWhen\u002FThen scenarios, .feature files, acceptance criteria, knowledge catalogs, or bug-fix behavior specs.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fomp-overlays\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fgherkin-bdd\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":20},"01M7AX84YZXTS7PR2WSMYJACTZ","sbtd-workflow-onboard","Checks, installs, or resets SBTD workflow tools, global Skills, managed AGENTS templates, and per-project configuration for local project roots in Oh My Pi.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fomp-overlays\u002Fonboard\u002Fruntime\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":20},"01M7AX80VRAYPPHAN1XN3X7G3V","web-ui-autotest-generator","从前端和后端源码中生成可维护的 Web UI 自动化测试。适用于分析页面、路由、组件、接口、用户流程，生成 Playwright UI 测试，运行测试，生成中文报告，并自检页面功能和跨页面逻辑是否被独立测试资产覆盖。 Generate maintainable Web UI automated tests from frontend and backend source code. Use for analyzing pages, routes, components, APIs, and user flows; generating and running Playwright UI tests; producing Chinese test reports; and checking whether page features and cross-page logic are covered by independent test assets.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fweb-ui-autotest-generator\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fweb-ui-autotest-generator\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M7AX7THTKH5DJPGH67M3SQ0Q","seo-geo","SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fseo-geo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fseo-geo\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":20},"01M7AX7P70M14ZRN5BRHC8BHP3","sbtd-task","Use for SBTD task execution and continuation, explicit default\u002Flite\u002Fstrict mode selection, task records and status changes, cross-session recovery, and task handoffs. Load strict gates only for strict tasks; ordinary questions and read-only work do not create task files.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fsbtd-task\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fsbtd-task\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M7AX7GX3NPZ19J2T9EMFC63H","project-validation","Use after code changes to choose and run validation commands for Node, JavaScript, TypeScript, Python, Go, Dart, Java, Kotlin, C++, Swift, or Objective-C projects. Prefer project-defined commands and report skipped checks and risks.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fproject-validation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fproject-validation\u002FSKILL.md",[],[]]