openharmonyinsight/ohos-dev-arkruntime-interop-development
skills/ohos-dev-arkruntime-interop-development/SKILL.md
Expert assistant for ArkTS-JS Interoperability in ArkCompiler (ArkTS runtime). 触发场景：修改/调试 ArkCompiler 互操作层代码（static_core/plugins/ets/runtime/interop_js/）、实现 ArkTS 与 JS 跨语言调用、处理 ETS 和 JS 之间的值转换（js_convert/JSRefConvert）、分析 Interop 内存泄漏与 GC 安全点、以及进行相关代码规范审查。
$ install --global
skillsauthnpx skillsauth add openharmonyinsight/openharmony-skills ohos-dev-arkruntime-interop-developmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 26, 2026, 6:52 AM37.2s7 files scanned
SKILL.md
- name:
- ohos-dev-arkruntime-interop-development
- description:
- >
- author:
- openharmony
- scope:
- domain
- stage:
- development
- domain:
- arkruntime
- capability:
- interop-development
- version:
- 1.0.0
- status:
- production
ArkRuntime Interop Development
Overview
This skill specializes in the ArkTS <-> JavaScript Interoperability layer located in runtime_core/static_core/plugins/ets/runtime/interop_js/. It bridges the ArkTS runtime (ETS) with the JavaScript engine via NAPI.
Core Capabilities
1. Navigating the Interop Layer
The directory structure is segmented by function:
ets_proxy/: ETS objects in JS.js_proxy/: JS objects in ETS.intrinsics/: Direct interop access from ArkTS.napi_impl/: Implementation of NAPI interfaces.- Reference: architecture.md
2. Underlying Runtimes
Interop depends on both the JS runtime and the NAPI framework:
- JS Runtime: Core VM, interpreter, and compiler context. See ets-runtime.md.
- NAPI Framework: The abstraction layer for JS engines. See napi-framework.md.
3. Value Conversion
Handled by js_convert and JSRefConvert classes.
- Key Files:
js_convert.h,js_refconvert_*.h.
Common Workflows
Debugging Interop Issues
- Crashes: Check
napi_envusage and scope mismatches. - Leaks: Monitor
GlobalObjectStorageand proxy reference counting. - Exceptions: Use
InteropCtx::ThrowJSErrororThrowETSError.
Performance & Memory
- Use
napi_create_async_workfor heavy tasks. - Respect GC safepoints and handle allocation through
EcmaVM. - Use
napi_handle_scopeto prevent memory leaks.
Coding Standards
- Formatting: Always run
bash code-format.sh format-changedbefore committing. - Validation: Ensure
check <path>passes andtidyreports no new warnings.
Key Headers
interop_context.h: Main context.js_convert.h: Value conversion.ets_proxy/ets_class_wrapper.h: ETS classes in JS.js_proxy/js_proxy.h: JS objects in ETS.
Related Skills
openharmonyinsight/skills/ohos-req-value-decision
testing
VerifiedTrustedCommunity
--- name: ohos-req-value-decision description: Use after review meeting to record decision and route to next step. Triggers: 评审决策纪要, 评审结论回流, value decision, 评审接纳, 评审不接纳, 评审退回, 下次重新上会. Do NOT use for feature baseline (ohos-req-feature-baseline), review gate checks (ohos-req-review-gate), or IR generation (ohos-req-feature-to-ir). metadata: author: openharmony scope: common stage: requirements capability: value-decision version: 0.3.0 status: draft tags: - sdd - requirements
30SKILL.mdUpdated Jul 22, 2026
openharmonyinsight/ohos-req-review-ppt-gen
development
VerifiedTrustedCommunity
Use when converting an OpenHarmony requirement document, spec, or design proposal into an OpenHarmony review slide deck (需求评审 / 需求变更评审 / 设计评审 PPTX) — produces the fixed OpenHarmony-branded review-deck structure (OH logo on every page) with architecture/flow diagrams and field tables. Triggers on "需求评审PPT", "需求变更评审", "把需求文档转成评审PPT", "spec转评审PPT", "requirement/spec to review deck". NOT for arbitrary or generic slide decks unrelated to OpenHarmony requirement/design review.
30SKILL.mdUpdated Jul 22, 2026
openharmonyinsight/ohos-req-review-gate
testing
VerifiedTrustedCommunity
Use when performing the Phase 0 Step 0.5 Review Ready Gate on a 04-feature.md, especially when the user says "evaluate gate", "review readiness", "feature ready?", "should we generate IR", or when the ohos-req-intake-orchestration main session needs a structured Ready / Conditional Ready / Not Ready judgment instead of doing the check inline. Reads 01-04, runs seven fixed checks plus a conditional-items check, and returns a machine-readable JSON summary plus a human-readable table that the main session can route on. Do NOT use for feature baseline generation (ohos-req-feature-baseline), value decision recording (ohos-req-value-decision), or IR generation (ohos-req-feature-to-ir).
30SKILL.mdUpdated Jul 22, 2026
openharmonyinsight/skills/ohos-req-requirement-intake
testing
VerifiedTrustedCommunity
--- name: ohos-req-requirement-intake description: Use when importing an OHOS requirement into Phase 0.1, especially for 01-requirement.md, requirement intake, background, user value, scenarios, scope, FR/NFR, affected modules, or priority. Triggers: 需求导入, 01-requirement, 需求基线, RR单号. Do NOT use for feasibility analysis (ohos-req-feasibility-analysis), architecture decision (ohos-req-arch-decision), or feature baseline (ohos-req-feature-baseline). metadata: author: openharmony scope: common
30SKILL.mdUpdated Jul 22, 2026