appmgr-api-generator

Name: appmgr-api-generator
Availability: InStock
Author: openharmonyinsight

Generate complete OpenHarmony AppMgr client-to-service IPC call chains.

31|6|Updated Jan 29, 2026

Search Tags:#code generation #service layer #generate #serialization #ipc #stubs #appmgr

Ready to run

npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill appmgr-api-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: appmgr-api-generator
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/appmgr-api-generator
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill appmgr-api-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires re, sys, pathlib, typing, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Adding a new AppMgr API in OpenHarmony often requires editing many interdependent files (client, proxy, stub, service, and service-inner), and missing one layer can break the call chain or leave functionality incomplete.

Core Features & Use Cases

End-to-end API call chain generation: Creates the full client → proxy → IPC → stub → service → service-inner flow for a newly added AppMgr interface.
Multi-file, pattern-aligned code modifications: Produces consistent edits across the required headers and source files following existing AppMgr service conventions.
Service-layer completeness: Ensures the AppMgrService layer implementation is included (not just stub and inner logic).

Quick Start

Provide the new AppMgr API name, parameters, return type, and behavior details, then ask the skill to generate the complete call chain and show a diff preview for each affected file.

Frequently Asked Questions about appmgr-api-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate the full IPC call chain for a new OpenHarmony AppMgr interface?▼

Adding a new AppMgr API requires synchronized edits across client, proxy, stub, service, and service-inner layers. Missing one layer breaks the call chain and leaves the IPC functionality incomplete or disconnected.

How does parameter marshaling and unmarshaling work for AppMgr IPC proxy and stub handlers?▼

Parameter marshaling and unmarshaling in AppMgr IPC requires writing interface code enum entries and handling parameter serialization across the proxy and stub to ensure synchronized client and service communication.

What is the best way to ensure AppMgrService layer implementation is included when adding new IPC APIs?▼

To ensure AppMgrService layer implementation is included, generate the complete client-to-service-inner call chain at once rather than editing files manually to prevent dropping required service orchestration logic.

Does this code generation approach work for OpenHarmony app_manager service interfaces requiring synchronized client and service updates?▼

Yes, this code generation approach works for OpenHarmony app_manager service interfaces by producing consistent multi-file edits spanning the full synchronized client implementation and AppMgrService business logic.

What are the limitations of manually editing AppMgr IPC files versus generating the complete call chain?▼

Manually editing AppMgr IPC files risks missing interdependent layers like the stub or service-inner, which breaks the call chain, whereas generating the complete chain ensures pattern-aligned edits and service-layer completeness across all required files.