openharmonyinsight/skills/appmgr-api-generator
skills/appmgr-api-generator/SKILL.md
--- name: appmgr-api-generator description: Generate complete API implementation chain from AppMgrClient to AppMgrServiceInner. Use when adding new interfaces to the app_manager service that require: (1) Client implementation, (2) IPC proxy/stub code, (3) AppMgrService service implementation, (4) AppMgrServiceInner business logic implementation, (5) Complete call chain: client.cpp → proxy.cpp → stub.cpp → service.cpp → service_inner.cpp --- # AppMgr API Generator Automatically generate complet
$ install --global
skillsauthnpx skillsauth add openharmonyinsight/openharmony-skills skills/appmgr-api-generatorInstall 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: May 22, 2026, 5:33 AM156.6s4 files scanned
SKILL.md
- name:
- appmgr-api-generator
- description:
- Generate complete API implementation chain from AppMgrClient to AppMgrServiceInner. Use when adding new interfaces to the app_manager service that require: (1) Client implementation, (2) IPC proxy/stub code, (3) AppMgrService service implementation, (4) AppMgrServiceInner business logic implementation, (5) Complete call chain: client.cpp → proxy.cpp → stub.cpp → service.cpp → service_inner.cpp
AppMgr API Generator
Automatically generate complete API call chain from client to service for new AppMgr APIs.
Quick Start
Ask: "Add a new API named [ApiName] with parameters [params] and return type [type]"
The skill will:
- Ask for interface details (name, parameters, return type, functionality)
- Generate all necessary code modifications
- Show diff preview for each file
Generated Files
For each new API, code is generated for the following files:
interfaces/inner_api/app_manager/include/appmgr/app_mgr_client.hinterfaces/inner_api/app_manager/src/appmgr/app_mgr_client.cppinterfaces/inner_api/app_manager/include/appmgr/app_mgr_ipc_interface_code.hinterfaces/inner_api/app_manager/include/appmgr/app_mgr_proxy.hinterfaces/inner_api/app_manager/src/appmgr/app_mgr_proxy.cppinterfaces/inner_api/app_manager/include/appmgr/app_mgr_interface.hservices/appmgr/include/app_mgr_service.h(NEW)services/appmgr/src/app_mgr_service.cpp(NEW)services/appmgr/src/app_mgr_service_inner.cppservices/appmgr/src/app_mgr_service_inner.hservices/appmgr/src/appmgrstub/app_mgr_stub.cpp
Workflow
- Interface Definition: Provide API name, parameters, return type
- Code Generation: Use
scripts/generate_appmgr_api.py - Review: Check generated code before applying changes
- Apply: Apply changes to all files in the call chain
Architecture Overview
Complete call chain path:
AppMgrClient → AppMgrProxy → IPC → AppMgrStub → AppMgrService → AppMgrServiceInner
- AppMgrClient: Client-side API wrapper
- AppMgrProxy: Client-side IPC proxy, marshals parameters
- AppMgrStub: Server-side IPC handler, unmarshals parameters
- AppMgrService: Service implementation, checks service status and delegates
- AppMgrServiceInner: Business logic implementation
Implementation Notes
- Follow existing code patterns in ability_runtime
- Generate appropriate IPC serialization/deserialization code
- Handle synchronous/asynchronous calls appropriately
- Include error handling and logging
- Important: Ensure to include AppMgrService layer implementation (was missing in previous versions)
See references/patterns.md for advanced patterns or special cases.
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