[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETFGB5WDBTZBHDTYBVFDHT":3,"skill-same:01M7ETFGB5WDBTZBHDTYBVFDHT":52},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ETFGB5WDBTZBHDTYBVFDHT","test-t3-mobile",null,"Launch and test T3 Code Mobile on an iOS Simulator or Android Emulator against disposable local T3 environments, including Metro and dev-client reuse, native rebuild decisions, per-client pairing, seeded projects, semantic UI control, screenshots, and iOS serve-sim streaming. Use after mobile UI or native changes, when reproducing phone or tablet behavior, pairing an emulator to isolated state, or verifying mobile behavior on macOS, Linux, or Windows.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Ftest-t3-mobile\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-t3-mobile\ndescription: Launch and test T3 Code Mobile on an iOS Simulator or Android Emulator against disposable local T3 environments, including Metro and dev-client reuse, native rebuild decisions, per-client pairing, seeded projects, semantic UI control, screenshots, and iOS serve-sim streaming. Use after mobile UI or native changes, when reproducing phone or tablet behavior, pairing an emulator to isolated state, or verifying mobile behavior on macOS, Linux, or Windows.\n---\n\n# Test T3 Mobile\n\nRun one focused, end-to-end mobile verification pass against disposable T3 state. Use the sibling [`test-t3-app`](..\u002Ftest-t3-app\u002FSKILL.md) skill as the detailed reference for pairing-token semantics and SQLite fixtures.\n\nCommand examples use POSIX shell syntax. On Windows, use PowerShell equivalents: set variables with `$env:NAME = \"value\"`, use an explicit temporary directory from `[System.IO.Path]::GetTempPath()`, and run multiline examples on one line or with PowerShell backticks. Use `$env:ANDROID_HOME\\platform-tools\\adb.exe` when `adb` is not already on `PATH`.\n\n## Select a viable platform\n\nInspect the host and the affected code before launching processes:\n\n- On macOS with Xcode, prefer one representative iOS Simulator when the change is cross-platform so the user can watch through serve-sim. Load and follow [`ios-debugger-agent`](..\u002Fios-debugger-agent\u002FSKILL.md), and load [`ios-simulator-browser`](..\u002Fios-simulator-browser\u002FSKILL.md) when live streaming is available.\n- On macOS, Linux, or Windows with the Android SDK, use one Android Emulator when Android is the affected surface or iOS tooling is unavailable.\n- When the change is platform-specific, test that platform. When neither platform is viable, report the missing SDK, emulator, or dev-client prerequisite rather than claiming verification.\n\nDo not treat unavailable iOS tooling as a blocker when Android is a valid representative target.\n\n## Choose the lightest valid launch path\n\n- For JavaScript, TypeScript, or asset-only changes, reuse a compatible installed development client and start Metro. Do not rebuild native code merely to load a new bundle.\n- For native source, native dependencies, entitlements, config plugins, or generated project changes, rebuild the affected platform.\n- Use `vp run ios:dev` or `vp run android:dev` only when an Expo clean prebuild is actually required; both commands regenerate the native project.\n- If the user requested no native rebuild and no compatible app is installed, reuse an existing compatible `.app` or `.apk` artifact when available. Otherwise report the missing dev client instead of silently rebuilding.\n\nThe development identity on both platforms is:\n\n- App: `T3 Code Dev`\n- Bundle\u002Fpackage identifier: `com.t3tools.t3code.dev`\n- URL scheme: `t3code-dev`\n\nBundle or package presence proves the correct variant, not native compatibility. Reuse it only when the current changes did not alter its Expo SDK, native dependencies, config plugins, entitlements, generated project, or native source.\n\n## Start one disposable T3 environment\n\nRun backend commands from the repository root. Use the ignored, worktree-local `.t3` directory or create a fresh directory with the host OS's temporary-directory mechanism. An explicit base directory stores state in `\u003Cbase-dir>\u002Fuserdata`; never point testing at shared `~\u002F.t3` state.\n\nSeed a small number of meaningful Git projects before starting the backend:\n\n```bash\nnode apps\u002Fserver\u002Fsrc\u002Fbin.ts project add \u003Cgit-workspace> \\\n  --base-dir \u003Cbase-dir> \\\n  --title \u003Cproject-title>\n```\n\nRunning `project add` before the backend starts gives it exclusive offline database access. If a backend is already running, wait until it is ready so the CLI dispatches through the live server; never run offline mutations concurrently with the server.\n\nUse direct SQLite mutation only for disposable projection fixtures. Follow `test-t3-app` and stop the backend before writing.\n\nStart a headless backend after seeding:\n\n```bash\nnode apps\u002Fserver\u002Fsrc\u002Fbin.ts serve \\\n  --host 127.0.0.1 \\\n  --port \u003Cserver-port> \\\n  --base-dir \u003Cbase-dir> \\\n  --no-browser\n```\n\nUse these client origins:\n\n- iOS Simulator: `http:\u002F\u002F127.0.0.1:\u003Cserver-port>`\n- Android Emulator: `http:\u002F\u002F10.0.2.2:\u003Cserver-port>`\n- Physical device: bind the backend to `0.0.0.0` and use the host's reachable LAN origin\n\nEnter the complete `http:\u002F\u002F` origin to make the test transport explicit. Bare IP addresses default to HTTP, while bare hostnames default to HTTPS. When testing web and mobile together, run `vp run dev --home-dir \u003Cbase-dir> --host 127.0.0.1` instead and do not launch a second backend over the same base directory.\n\n## Start or reuse Metro safely\n\nRun Metro from `apps\u002Fmobile`.\n\n1. Inspect any process on the intended Metro port and its `\u002Fstatus` response. Reuse it only when it is healthy, belongs to this worktree, and matches `APP_VARIANT=development`, `--dev-client`, and scheme `t3code-dev`.\n2. Never kill another worktree's Metro. Use a free explicit port when necessary.\n3. Run `vp run dev:client` on the standard port. For another port, retain the complete development identity:\n\n   ```bash\n   APP_VARIANT=development vp exec expo start \\\n     --dev-client \\\n     --scheme t3code-dev \\\n     --lan \\\n     --port \u003Cmetro-port>\n   ```\n\n   In PowerShell, set `$env:APP_VARIANT = \"development\"` first and then run the `vp exec expo start ...` command without the leading assignment.\n\n4. Open the exact development-client URL for the selected device and confirm the loaded bundle belongs to this worktree and Metro port.\n\n### iOS launch\n\nUse `ios-debugger-agent` to select one UDID and set these XcodeBuildMCP session defaults:\n\n- Workspace: `\u003Crepo>\u002Fapps\u002Fmobile\u002Fios\u002FT3CodeDev.xcworkspace`\n- Scheme: `T3CodeDev`\n- Configuration: `Debug`\n- Simulator ID: the selected UDID\n- Bundle ID: `com.t3tools.t3code.dev`\n\nCheck the installed client with:\n\n```bash\nxcrun simctl get_app_container \u003Csimulator-udid> com.t3tools.t3code.dev app\nxcrun simctl openurl \u003Csimulator-udid> \u003Cprinted-dev-client-url>\n```\n\nAccept the iOS confirmation prompt and dismiss the developer menu when it obscures the app.\n\n### Android launch\n\nSelect one running emulator serial from `adb devices` and check the installed client:\n\n```bash\nadb -s \u003Cemulator-serial> shell pm path com.t3tools.t3code.dev\nadb -s \u003Cemulator-serial> reverse tcp:\u003Cmetro-port> tcp:\u003Cmetro-port>\nadb -s \u003Cemulator-serial> shell am start -W \\\n  -a android.intent.action.VIEW \\\n  -d '\u003Cprinted-dev-client-url>' \\\n  com.t3tools.t3code.dev\n```\n\nDo not start, stop, erase, or reconfigure an emulator owned by another task. Track and later stop only processes owned by this test.\n\n## Pair each client once\n\nUse the bundled helper from the repository root. It issues a fresh credential against the running backend's exact base directory, opens the existing Add Environment route with the credential in an encoded query parameter, and asks that route to connect once:\n\n```bash\n.agents\u002Fskills\u002Ftest-t3-mobile\u002Fscripts\u002Fpair-client.sh \\\n  ios \u003Csimulator-udid> \u003Cserver-port> \u003Cbase-dir>\n\n.agents\u002Fskills\u002Ftest-t3-mobile\u002Fscripts\u002Fpair-client.sh \\\n  android \u003Cemulator-serial> \u003Cserver-port> \u003Cbase-dir>\n```\n\nRun only the command for the selected platform. The helper uses `http:\u002F\u002F127.0.0.1:\u003Cserver-port>` for iOS and `http:\u002F\u002F10.0.2.2:\u003Cserver-port>` for Android. Pass a fifth argument only when testing a non-development URL scheme.\n\nThe helper opens this registered route:\n\n```text\nt3code-dev:\u002F\u002Fconnections\u002Fnew?pairingUrl=\u003Cencoded-pairing-url>&autoConnect=1\n```\n\nThe Add Environment route owns the behavior: `pairingUrl` prefills its normal host and token inputs, while `autoConnect=1` submits once in development builds and returns to Home after success. Without `autoConnect`, the same route only prefills the form for manual inspection.\n\nDo not enter pairing hosts or tokens through simulator keyboard automation. Xcode's semantic typer sends HID-style key events through the simulator's active keyboard state, which can corrupt uppercase tokens and punctuation even when the host Mac uses a U.S. input source. The one-shot route is the deterministic pairing path. Use the visible form only as a fallback, and paste credentials rather than typing them character by character.\n\nVerify the expected seeded projects appear before exercising the affected flow.\n\nPairing credentials are secret, short-lived, and single-use. Create a different credential for every simulator, emulator, physical device, or browser. If an attempt fails, issue a new credential rather than retrying the old one. Do not expose tokens in screenshots, commits, or final responses.\n\n## Drive and observe the affected flow\n\n### iOS\n\nUse `snapshot_ui` and current element references from XcodeBuildMCP for taps and typing. Stream the same UDID through `ios-simulator-browser` so the user can watch in T3 Code when the host supports it. Use the stream as a visual feed rather than a reason to switch to fragile browser coordinates.\n\n### Android\n\nPrefer semantic Android automation exposed by the current agent host. Otherwise inspect the current hierarchy with `adb shell uiautomator dump`, target stable resource IDs, content descriptions, text, or bounds, and use scoped `adb shell input` actions. Refresh the hierarchy after navigation. Capture the final state with `adb exec-out screencap -p`.\n\nAndroid does not use serve-sim. Use a browser-compatible Android mirror when the host already provides one; otherwise return focused emulator screenshots as evidence rather than installing unrelated streaming infrastructure during verification.\n\n## Verify and clean up\n\nExercise only the affected flow on one representative device unless the change specifically concerns platform, OS version, or screen size. Before finishing:\n\n1. Confirm the app connected to the intended disposable environment instead of merely rendering an empty disconnected state.\n2. Capture the relevant final state.\n3. Remove the disposable environment from T3 Code Dev.\n4. Remove any `adb reverse` rule created for this test with `adb -s \u003Cemulator-serial> reverse --remove tcp:\u003Cmetro-port>`.\n5. Stop only the serve-sim, Metro, backend, emulator, and log processes started by this test.\n6. Remove only base directories and temporary Git repositories deliberately created for this test. Preserve them when they contain useful reproduction evidence.\n\nKeep local verification focused. Do not turn this workflow into a full repository test run.\n\n## Troubleshoot predictable failures\n\n- **Old UI or an old error appears:** verify Metro's worktree, variant, URL, and port before diagnosing the app.\n- **Metro serves stale or invalid transforms after those checks:** stop the owned Metro process and run `vp run dev:client:reset` once on the standard port. For a custom port, add `--clear` to the complete explicit `expo start` command above.\n- **The environment remains empty:** verify the platform-specific HTTP origin, use a fresh token, and confirm project seeding used the identical base directory.\n- **A second client cannot pair:** pairing tokens are single-use; issue another token.\n- **The pairing form opens but does not connect:** confirm the deep link uses the existing `connections\u002Fnew` route, includes `autoConnect=1`, and carries a freshly minted encoded `pairingUrl`.\n- **Pairing text changes case or punctuation:** do not retry semantic typing. Use `scripts\u002Fpair-client.sh`; the simulator keyboard layout and HID input path are not reliable for credentials.\n- **iOS semantic actions fail:** set explicit XcodeBuildMCP defaults and refresh with `snapshot_ui`.\n- **Android cannot reach Metro:** verify `adb reverse` for the exact Metro port and relaunch the development-client URL.\n- **Android cannot reach the backend:** use `10.0.2.2`, not `127.0.0.1`, for the Android Emulator.\n","# Test T3 Mobile\n\nRun one focused, end-to-end mobile verification pass against disposable T3 state. Use the sibling [`test-t3-app`](..\u002Ftest-t3-app\u002FSKILL.md) skill as the detailed reference for pairing-token semantics and SQLite fixtures.\n\nCommand examples use POSIX shell syntax. On Windows, use PowerShell equivalents: set variables with `$env:NAME = \"value\"`, use an explicit temporary directory from `[System.IO.Path]::GetTempPath()`, and run multiline examples on one line or with PowerShell backticks. Use `$env:ANDROID_HOME\\platform-tools\\adb.exe` when `adb` is not already on `PATH`.\n\n## Select a viable platform\n\nInspect the host and the affected code before launching processes:\n\n- On macOS with Xcode, prefer one representative iOS Simulator when the change is cross-platform so the user can watch through serve-sim. Load and follow [`ios-debugger-agent`](..\u002Fios-debugger-agent\u002FSKILL.md), and load [`ios-simulator-browser`](..\u002Fios-simulator-browser\u002FSKILL.md) when live streaming is available.\n- On macOS, Linux, or Windows with the Android SDK, use one Android Emulator when Android is the affected surface or iOS tooling is unavailable.\n- When the change is platform-specific, test that platform. When neither platform is viable, report the missing SDK, emulator, or dev-client prerequisite rather than claiming verification.\n\nDo not treat unavailable iOS tooling as a blocker when Android is a valid representative target.\n\n## Choose the lightest valid launch path\n\n- For JavaScript, TypeScript, or asset-only changes, reuse a compatible installed development client and start Metro. Do not rebuild native code merely to load a new bundle.\n- For native source, native dependencies, entitlements, config plugins, or generated project changes, rebuild the affected platform.\n- Use `vp run ios:dev` or `vp run android:dev` only when an Expo clean prebuild is actually required; both commands regenerate the native project.\n- If the user requested no native rebuild and no compatible app is installed, reuse an existing compatible `.app` or `.apk` artifact when available. Otherwise report the missing dev client instead of silently rebuilding.\n\nThe development identity on both platforms is:\n\n- App: `T3 Code Dev`\n- Bundle\u002Fpackage identifier: `com.t3tools.t3code.dev`\n- URL scheme: `t3code-dev`\n\nBundle or package presence proves the correct variant, not native compatibility. Reuse it only when the current changes did not alter its Expo SDK, native dependencies, config plugins, entitlements, generated project, or native source.\n\n## Start one disposable T3 environment\n\nRun backend commands from the repository root. Use the ignored, worktree-local `.t3` directory or create a fresh directory with the host OS's temporary-directory mechanism. An explicit base directory stores state in `\u003Cbase-dir>\u002Fuserdata`; never point testing at shared `~\u002F.t3` state.\n\nSeed a small number of meaningful Git projects before starting the backend:\n\n```bash\nnode apps\u002Fserver\u002Fsrc\u002Fbin.ts project add \u003Cgit-workspace> \\\n  --base-dir \u003Cbase-dir> \\\n  --title \u003Cproject-title>\n```\n\nRunning `project add` before the backend starts gives it exclusive offline database access. If a backend is already running, wait until it is ready so the CLI dispatches through the live server; never run offline mutations concurrently with the server.\n\nUse direct SQLite mutation only for disposable projection fixtures. Follow `test-t3-app` and stop the backend before writing.\n\nStart a headless backend after seeding:\n\n```bash\nnode apps\u002Fserver\u002Fsrc\u002Fbin.ts serve \\\n  --host 127.0.0.1 \\\n  --port \u003Cserver-port> \\\n  --base-dir \u003Cbase-dir> \\\n  --no-browser\n```\n\nUse these client origins:\n\n- iOS Simulator: `http:\u002F\u002F127.0.0.1:\u003Cserver-port>`\n- Android Emulator: `http:\u002F\u002F10.0.2.2:\u003Cserver-port>`\n- Physical device: bind the backend to `0.0.0.0` and use the host's reachable LAN origin\n\nEnter the complete `http:\u002F\u002F` origin to make the test transport explicit. Bare IP addresses default to HTTP, while bare hostnames default to HTTPS. When testing web and mobile together, run `vp run dev --home-dir \u003Cbase-dir> --host 127.0.0.1` instead and do not launch a second backend over the same base directory.\n\n## Start or reuse Metro safely\n\nRun Metro from `apps\u002Fmobile`.\n\n1. Inspect any process on the intended Metro port and its `\u002Fstatus` response. Reuse it only when it is healthy, belongs to this worktree, and matches `APP_VARIANT=development`, `--dev-client`, and scheme `t3code-dev`.\n2. Never kill another worktree's Metro. Use a free explicit port when necessary.\n3. Run `vp run dev:client` on the standard port. For another port, retain the complete development identity:\n\n   ```bash\n   APP_VARIANT=development vp exec expo start \\\n     --dev-client \\\n     --scheme t3code-dev \\\n     --lan \\\n     --port \u003Cmetro-port>\n   ```\n\n   In PowerShell, set `$env:APP_VARIANT = \"development\"` first and then run the `vp exec expo start ...` command without the leading assignment.\n\n4. Open the exact development-client URL for the selected device and confirm the loaded bundle belongs to this worktree and Metro port.\n\n### iOS launch\n\nUse `ios-debugger-agent` to select one UDID and set these XcodeBuildMCP session defaults:\n\n- Workspace: `\u003Crepo>\u002Fapps\u002Fmobile\u002Fios\u002FT3CodeDev.xcworkspace`\n- Scheme: `T3CodeDev`\n- Configuration: `Debug`\n- Simulator ID: the selected UDID\n- Bundle ID: `com.t3tools.t3code.dev`\n\nCheck the installed client with:\n\n```bash\nxcrun simctl get_app_container \u003Csimulator-udid> com.t3tools.t3code.dev app\nxcrun simctl openurl \u003Csimulator-udid> \u003Cprinted-dev-client-url>\n```\n\nAccept the iOS confirmation prompt and dismiss the developer menu when it obscures the app.\n\n### Android launch\n\nSelect one running emulator serial from `adb devices` and check the installed client:\n\n```bash\nadb -s \u003Cemulator-serial> shell pm path com.t3tools.t3code.dev\nadb -s \u003Cemulator-serial> reverse tcp:\u003Cmetro-port> tcp:\u003Cmetro-port>\nadb -s \u003Cemulator-serial> shell am start -W \\\n  -a android.intent.action.VIEW \\\n  -d '\u003Cprinted-dev-client-url>' \\\n  com.t3tools.t3code.dev\n```\n\nDo not start, stop, erase, or reconfigure an emulator owned by another task. Track and later stop only processes owned by this test.\n\n## Pair each client once\n\nUse the bundled helper from the repository root. It issues a fresh credential against the running backend's exact base directory, opens the existing Add Environment route with the credential in an encoded query parameter, and asks that route to connect once:\n\n```bash\n.agents\u002Fskills\u002Ftest-t3-mobile\u002Fscripts\u002Fpair-client.sh \\\n  ios \u003Csimulator-udid> \u003Cserver-port> \u003Cbase-dir>\n\n.agents\u002Fskills\u002Ftest-t3-mobile\u002Fscripts\u002Fpair-client.sh \\\n  android \u003Cemulator-serial> \u003Cserver-port> \u003Cbase-dir>\n```\n\nRun only the command for the selected platform. The helper uses `http:\u002F\u002F127.0.0.1:\u003Cserver-port>` for iOS and `http:\u002F\u002F10.0.2.2:\u003Cserver-port>` for Android. Pass a fifth argument only when testing a non-development URL scheme.\n\nThe helper opens this registered route:\n\n```text\nt3code-dev:\u002F\u002Fconnections\u002Fnew?pairingUrl=\u003Cencoded-pairing-url>&autoConnect=1\n```\n\nThe Add Environment route owns the behavior: `pairingUrl` prefills its normal host and token inputs, while `autoConnect=1` submits once in development builds and returns to Home after success. Without `autoConnect`, the same route only prefills the form for manual inspection.\n\nDo not enter pairing hosts or tokens through simulator keyboard automation. Xcode's semantic typer sends HID-style key events through the simulator's active keyboard state, which can corrupt uppercase tokens and punctuation even when the host Mac uses a U.S. input source. The one-shot route is the deterministic pairing path. Use the visible form only as a fallback, and paste credentials rather than typing them character by character.\n\nVerify the expected seeded projects appear before exercising the affected flow.\n\nPairing credentials are secret, short-lived, and single-use. Create a different credential for every simulator, emulator, physical device, or browser. If an attempt fails, issue a new credential rather than retrying the old one. Do not expose tokens in screenshots, commits, or final responses.\n\n## Drive and observe the affected flow\n\n### iOS\n\nUse `snapshot_ui` and current element references from XcodeBuildMCP for taps and typing. Stream the same UDID through `ios-simulator-browser` so the user can watch in T3 Code when the host supports it. Use the stream as a visual feed rather than a reason to switch to fragile browser coordinates.\n\n### Android\n\nPrefer semantic Android automation exposed by the current agent host. Otherwise inspect the current hierarchy with `adb shell uiautomator dump`, target stable resource IDs, content descriptions, text, or bounds, and use scoped `adb shell input` actions. Refresh the hierarchy after navigation. Capture the final state with `adb exec-out screencap -p`.\n\nAndroid does not use serve-sim. Use a browser-compatible Android mirror when the host already provides one; otherwise return focused emulator screenshots as evidence rather than installing unrelated streaming infrastructure during verification.\n\n## Verify and clean up\n\nExercise only the affected flow on one representative device unless the change specifically concerns platform, OS version, or screen size. Before finishing:\n\n1. Confirm the app connected to the intended disposable environment instead of merely rendering an empty disconnected state.\n2. Capture the relevant final state.\n3. Remove the disposable environment from T3 Code Dev.\n4. Remove any `adb reverse` rule created for this test with `adb -s \u003Cemulator-serial> reverse --remove tcp:\u003Cmetro-port>`.\n5. Stop only the serve-sim, Metro, backend, emulator, and log processes started by this test.\n6. Remove only base directories and temporary Git repositories deliberately created for this test. Preserve them when they contain useful reproduction evidence.\n\nKeep local verification focused. Do not turn this workflow into a full repository test run.\n\n## Troubleshoot predictable failures\n\n- **Old UI or an old error appears:** verify Metro's worktree, variant, URL, and port before diagnosing the app.\n- **Metro serves stale or invalid transforms after those checks:** stop the owned Metro process and run `vp run dev:client:reset` once on the standard port. For a custom port, add `--clear` to the complete explicit `expo start` command above.\n- **The environment remains empty:** verify the platform-specific HTTP origin, use a fresh token, and confirm project seeding used the identical base directory.\n- **A second client cannot pair:** pairing tokens are single-use; issue another token.\n- **The pairing form opens but does not connect:** confirm the deep link uses the existing `connections\u002Fnew` route, includes `autoConnect=1`, and carries a freshly minted encoded `pairingUrl`.\n- **Pairing text changes case or punctuation:** do not retry semantic typing. Use `scripts\u002Fpair-client.sh`; the simulator keyboard layout and HID input path are not reliable for credentials.\n- **iOS semantic actions fail:** set explicit XcodeBuildMCP defaults and refresh with `snapshot_ui`.\n- **Android cannot reach Metro:** verify `adb reverse` for the exact Metro port and relaunch the development-client URL.\n- **Android cannot reach the backend:** use `10.0.2.2`, not `127.0.0.1`, for the Android Emulator.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Ftest-t3-mobile",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill test-t3-mobile",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill test-t3-mobile",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill test-t3-mobile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Ftest-t3-mobile\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",252,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Ftest-t3-mobile\u002Fagents\u002Fopenai.yaml",[53,60,67,74,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]