Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Unified integration skill for React Native Update / Pushy(统一入口)across OpenClaw and Claude Code workflows. Use for 安装配置, appKey/update.json 接线, iOS/Android 原生...
Unified integration skill for React Native Update / Pushy(统一入口)across OpenClaw and Claude Code workflows. Use for 安装配置, appKey/update.json 接线, iOS/Android 原生...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill to get a project from “not integrated” to “hot update works in release builds”. Prioritize copy-paste-safe steps, smallest viable changes, and explicit verification checkpoints.
Detect app type (React Native CLI vs Expo) and target platforms. Apply dependency/install steps from references/integration-playbook.md. Apply required native config (Bundle URL / MainApplication integration points). Add Pushy client + UpdateProvider minimal bootstrapping. Run scripts/integration_doctor.sh <app-root> to detect common misses. Return a short action list: done / missing / next verification.
If user context is OpenClaw: provide OpenClaw-first instructions and file/workspace conventions. If user context is Claude Code: provide Claude Code-first command style and workflow wording. If context is unknown: provide neutral steps first, then append OpenClaw/Claude Code notes. Keep technical steps identical; only adapt command conventions and delivery style.
Keep user code changes minimal and localized. Do not promise hot update works in debug mode; emphasize release verification. Warn about expo-updates conflict in Expo projects. Preserve existing app architecture; adapt snippets to current project style. If native files differ heavily (monorepo/mixed native), provide targeted patch guidance instead of broad rewrites.
Minimal integration diff (exact files and snippets). Verification checklist (build, check update, download, switch version). Troubleshooting hints for common failures. Scenario examples when requested (including class component integration and custom whitelist rollout).
Read references/integration-playbook.md before giving steps. Use scripts/integration_doctor.sh for quick project diagnosis.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.