[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75GSNQJV4XKYA0K2MHSZP3S":3,"skill-same:01M75GSNQJV4XKYA0K2MHSZP3S":57},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75GSNQJV4XKYA0K2MHSZP3S","codex-expo-run-actions",null,"Wire Expo projects into the Codex app with project-local run scripts and .codex\u002Fenvironments\u002Fenvironment.toml actions. Use when the user wants the Codex app Run button, build\u002Frun actions, action buttons, or a stable Expo start\u002Frun workflow from Codex.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fcodex-expo-run-actions\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: codex-expo-run-actions\ndescription: Wire Expo projects into the Codex app with project-local run scripts and .codex\u002Fenvironments\u002Fenvironment.toml actions. Use when the user wants the Codex app Run button, build\u002Frun actions, action buttons, or a stable Expo start\u002Frun workflow from Codex.\nversion: 1.0.0\nlicense: MIT\n---\n\n# Codex Run Actions for Expo\n\nUse this skill to connect an Expo project to the Codex app action bar.\n\nThe goal is one project-local script plus `.codex\u002Fenvironments\u002Fenvironment.toml`,\nso the user can press `Run` in the Codex app and see the Expo CLI \u002F Metro logs in\nan action terminal.\n\n## Workflow\n\n1. Confirm the current workspace is an Expo app.\n   - Look for `package.json`.\n   - Look for `app.json`, `app.config.js`, `app.config.ts`, or `expo` in `package.json`.\n   - Do not wire the Codex action at a monorepo root if the Expo app is in a child package.\n\n2. Discover the package runner.\n   - Prefer the package manager declared in `packageManager`.\n   - Otherwise infer from lockfiles.\n   - The generated run script should still have a safe fallback to `npx expo`.\n\n3. Create or update `script\u002Fbuild_and_run.sh`.\n   - Use the reference file for the script shape.\n   - Default no-argument mode starts the Expo dev server: `expo start`.\n   - Keep the dev server in the foreground so the Codex action terminal owns logs and Ctrl-C behavior.\n   - Support optional modes for direct buttons:\n     - `--ios` starts Expo and opens iOS simulator.\n     - `--android` starts Expo and opens Android.\n     - `--web` starts Expo for web.\n     - `--dev-client` starts in dev-client mode.\n     - `--tunnel` starts a tunnel.\n     - `--export-web` exports web.\n\n4. Write `.codex\u002Fenvironments\u002Fenvironment.toml`.\n   - Always add or update one primary action named `Run`.\n   - Wire `Run` to `.\u002Fscript\u002Fbuild_and_run.sh`.\n   - Add direct `Run iOS`, `Run Android`, `Run Web`, or `Run Dev Client`\n     actions only when the user asks for those buttons or the project clearly needs them.\n   - If the environment file already exists, update the existing matching action instead of duplicating it.\n\n5. Use the action script as the default local run path.\n   - After wiring, run `.\u002Fscript\u002Fbuild_and_run.sh --help` or a short non-server mode if you need to sanity-check syntax.\n   - Do not start a long-lived Metro server during a setup-only task unless the user asked you to run the app.\n\n## References\n\n- `references\u002Fexpo-run-button-bootstrap.md`: canonical Expo `script\u002Fbuild_and_run.sh` and Codex environment action examples.\n\n## Guardrails\n\n- Try Expo Go \u002F `expo start` first; do not default the Codex Run button to `expo run:ios`, `expo run:android`, prebuild, or EAS Build.\n- Do not wire cloud actions such as `eas build`, `eas submit`, or store deployment into Codex buttons unless the user explicitly asks and accepts the auth \u002F time \u002F cost tradeoff.\n- Do not create a nested git repo.\n- Do not put secrets in `.codex\u002Fenvironments\u002Fenvironment.toml` or in the run script.\n- Do not background Metro from the run script; the action terminal should show the active server logs.\n- Do not hard-code npm if the project uses pnpm, yarn, or bun.\n\n## Output Expectations\n\nWhen setup changes are made, summarize:\n\n- the Expo app root you wired\n- the run script path\n- the Codex environment file path\n- the actions added or updated\n- how to launch the same path from shell\n","# Codex Run Actions for Expo\n\nUse this skill to connect an Expo project to the Codex app action bar.\n\nThe goal is one project-local script plus `.codex\u002Fenvironments\u002Fenvironment.toml`,\nso the user can press `Run` in the Codex app and see the Expo CLI \u002F Metro logs in\nan action terminal.\n\n## Workflow\n\n1. Confirm the current workspace is an Expo app.\n   - Look for `package.json`.\n   - Look for `app.json`, `app.config.js`, `app.config.ts`, or `expo` in `package.json`.\n   - Do not wire the Codex action at a monorepo root if the Expo app is in a child package.\n\n2. Discover the package runner.\n   - Prefer the package manager declared in `packageManager`.\n   - Otherwise infer from lockfiles.\n   - The generated run script should still have a safe fallback to `npx expo`.\n\n3. Create or update `script\u002Fbuild_and_run.sh`.\n   - Use the reference file for the script shape.\n   - Default no-argument mode starts the Expo dev server: `expo start`.\n   - Keep the dev server in the foreground so the Codex action terminal owns logs and Ctrl-C behavior.\n   - Support optional modes for direct buttons:\n     - `--ios` starts Expo and opens iOS simulator.\n     - `--android` starts Expo and opens Android.\n     - `--web` starts Expo for web.\n     - `--dev-client` starts in dev-client mode.\n     - `--tunnel` starts a tunnel.\n     - `--export-web` exports web.\n\n4. Write `.codex\u002Fenvironments\u002Fenvironment.toml`.\n   - Always add or update one primary action named `Run`.\n   - Wire `Run` to `.\u002Fscript\u002Fbuild_and_run.sh`.\n   - Add direct `Run iOS`, `Run Android`, `Run Web`, or `Run Dev Client`\n     actions only when the user asks for those buttons or the project clearly needs them.\n   - If the environment file already exists, update the existing matching action instead of duplicating it.\n\n5. Use the action script as the default local run path.\n   - After wiring, run `.\u002Fscript\u002Fbuild_and_run.sh --help` or a short non-server mode if you need to sanity-check syntax.\n   - Do not start a long-lived Metro server during a setup-only task unless the user asked you to run the app.\n\n## References\n\n- `references\u002Fexpo-run-button-bootstrap.md`: canonical Expo `script\u002Fbuild_and_run.sh` and Codex environment action examples.\n\n## Guardrails\n\n- Try Expo Go \u002F `expo start` first; do not default the Codex Run button to `expo run:ios`, `expo run:android`, prebuild, or EAS Build.\n- Do not wire cloud actions such as `eas build`, `eas submit`, or store deployment into Codex buttons unless the user explicitly asks and accepts the auth \u002F time \u002F cost tradeoff.\n- Do not create a nested git repo.\n- Do not put secrets in `.codex\u002Fenvironments\u002Fenvironment.toml` or in the run script.\n- Do not background Metro from the run script; the action terminal should show the active server logs.\n- Do not hard-code npm if the project uses pnpm, yarn, or bun.\n\n## Output Expectations\n\nWhen setup changes are made, summarize:\n\n- the Expo app root you wired\n- the run script path\n- the Codex environment file path\n- the actions added or updated\n- how to launch the same path from shell\n",{"name":5,"license":15,"version":24,"description":7},"1.0.0","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fcodex-expo-run-actions",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add stanfish06\u002Fskillquarium --skill codex-expo-run-actions",{"tool":39,"command":40},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill codex-expo-run-actions",{"tool":42,"command":43},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill codex-expo-run-actions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fcodex-expo-run-actions\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",394,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fcodex-expo-run-actions\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fexpo-run-button-bootstrap.md",4972,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fcodex-expo-run-actions\u002Freferences\u002Fexpo-run-button-bootstrap.md",[58,65,74,81,88,95],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\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":69,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\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":69,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]