ワンクリックでManusで任意のスキルを実行

hm-sa-skill

HarmonyOS/OpenHarmony System Ability Manager (SAMgr) daemon domain expertise. Covers SA architecture, lifecycle management, IPC/RPC communication patterns, service registration/discovery, source code structure, and API reference. Use when: (1) Working with OpenHarmony SAMgr / systemabilitymgr_samgr code, (2) Questions about SA lifecycle, daemon startup, or boot sequence, (3) Implementing or debugging IPC/RPC Proxy/Stub patterns for system services, (4) Understanding SA registration (AddSystemAbility, GetSystemAbility, LoadSystemAbility), (5) Analyzing SAMgr crash recovery, on-demand loading, or distributed SA routing, (6) Navigating the systemabilitymgr subsystem source tree.

Manusで実行

概要

インストールコマンド

npx skills add https://github.com/aresbit/claude-skills --skill hm-sa-skill

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール

ソース

aresbit/claude-skills

スター0

フォーク0

更新日2026年5月21日 03:41

ファイルエクスプローラー

5 ファイル

SKILL.md

readonly

name

hm-sa-skill

description

HarmonyOS System Ability Manager (SAMgr) Skill

Overview

SAMgr is the daemon-level service registry and lifecycle manager for all system services in HarmonyOS/OpenHarmony. It plays a role analogous to Android's servicemanager + init daemon, with stronger lifecycle governance and native cross-device distributed support.

Knowledge Domains

This skill covers four domains. Load the relevant reference file based on the task:

Domain	Reference	When to Load
Architecture & Concepts	references/hm-sa-architecture.md	Understanding SAMgr's role, boot sequence, SA lifecycle, data structures, registration modes
API Reference	references/hm-sa-api-reference.md	Writing SA code, Proxy/Stub patterns, registration macros, death notifications
Source Code Structure	references/hm-sa-source-structure.md	Navigating the repo, finding files, understanding build config, SA .cfg format

Quick Reference

SAMgr's Four Roles

Service Registry — Central table mapping SA ID → proxy object
Lifecycle Manager — OnStart/OnStop, crash detection, auto-restart
IPC Router — Local via Binder, cross-device via DSoftBus
Capability Scheduler — Boot ordering, priority, on-demand loading

SA Lifecycle

Register → Publish → Discovery → IPC Invocation → Reclamation

Core API (C++)

// Get SAMgr client
sptr<ISystemAbilityManager> samgr =
    SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();

// Register SA
samgr->AddSystemAbility(saId, new MyAbility());

// Get SA proxy
sptr<IRemoteObject> obj = samgr->GetSystemAbility(saId);

Boot Sequence

init → parse .cfg → SAMgr daemon → foundation (safwk + samgr) → appspawn → apps

Source Repo

GitHub: https://gitcode.com/openharmony/systemabilitymgr_samgr
Path: foundation/systemabilitymgr/samgr/

Fetching Official Docs

To refresh the fetched Huawei developer docs, run:

# Fetch IPC Kit docs (preset)
python3 scripts/fetch_sa_docs.py --preset ipc --out-dir references/fetched-docs

# Fetch a single doc by slug
python3 scripts/fetch_sa_docs.py --slug ipc-rpc-overview --out /tmp/doc.md

# List all known working slugs
python3 scripts/fetch_sa_docs.py --list-slugs

Known working slugs:

ipc-rpc-overview — IPC Kit V13 overview (current)
ipc-rpc-overview-0000001427584740-V2 — IPC RPC V2 overview (archived)

Key Comparison: Android vs HarmonyOS

Dimension	Android	HarmonyOS SAMgr
Service Management	Dispersed (app-driven)	Unified (system-driven)
Lifecycle	App-controlled	System-controlled
Cross-device	None built-in	Natively supported
Crash Recovery	Limited	Auto-restart + client notification

Recognized SA IDs

SA ID	Service
3001	PowerManager
3002	LocationService
3400	BundleMgrService

このリポジトリの他の Skills

同じリポジトリ

fanqie-publish

aresbit/claude-skills

Automates publishing novel chapters to 番茄小说 (fanqienovel.com) via Playwright browser automation. Use when the user wants to publish, batch-upload, or retry uploading novel chapters from a local directory to 番茄小说. Handles login state, ProseMirror editor injection, popup dismissal (错别字检测/仅基础检测/AI声明/确认发布), and auto-archives successfully published files. Triggers on requests like "发布章节到番茄", "上传小说", "batch publish chapters", or retrying failed chapters.

2026-05-240

harmonyos-code-review

aresbit/claude-skills

Use when reviewing HarmonyOS (ArkTS/ArkUI) code, when file extensions are .ets/.ts in HarmonyOS context, or when checking ArkUI component implementations, async/await patterns, or @State/@Prop/@Provide usage

2026-05-220

pack-skill

aresbit/claude-skills

Solve any problem in the philosophical family of the knapsack problem (背包问题) using the unified state-design framework from 崔添翼《背包问题九讲》. Use whenever a problem reduces to "choose a subset/multiset of items under a capacity-like cost to optimize a value-like objective" — including 0/1 pack, unbounded/complete pack, bounded/multiple pack, mixed pack, 2-D cost pack, grouped pack, dependency pack (主件/附件, tree-shaped), generalized items (泛化物品), subset-sum / can-it-fill-exactly, counting feasible or optimal schemes, recovering the chosen subset, lexicographically smallest plan, and Kth-best value. Trigger words — 背包/knapsack, subset sum, "choose items with weight/cost ≤ W to maximize value", "ways to make change", "partition into K groups", "limited copies", "items depend on each other", "fill exactly", coin change counting, NOIP-style 金明的预算方案 / 采药 / 装箱问题.

2026-05-220

zig

aresbit/claude-skills

Up-to-date Zig programming language patterns for version 0.16.0. Use when writing, reviewing, or debugging Zig code, working with build.zig and build.zig.zon files, or using comptime metaprogramming. Critical for avoiding outdated patterns from training data - especially build system APIs (root_module instead of root_source_file), I/O APIs (buffered writer pattern), container initialization (.empty/.init), allocator selection (DebugAllocator), and removed language features (@Type, @cImport, async/await, usingnamespace).

2026-05-220

hm-napi-skill

aresbit/claude-skills

HarmonyOS/OpenHarmony Node-API (NAPI) domain expertise for developing native C/C++ modules that bridge ArkTS/JS with native code. Use when: (1) Creating or modifying NAPI native modules in OpenHarmony projects, (2) Implementing high-performance native-codec/image-processing/thumbnail NAPI interfaces, (3) Designing NAPI module registration, async work, thread-safe callbacks, or Promise-based native APIs, (4) Debugging NAPI lifecycle, memory, or cross-thread issues, (5) Applying NAPI performance patterns (ArrayBuffer zero-copy, Sendable types, QoS scheduling), (6) Working with multimedia_media_library or any OHOS service-layer NAPI code.

2026-05-210

distributed-systems

aresbit/claude-skills

AI-assisted distributed systems verification with TLA+ formal specification. Use when verifying distributed system correctness, discovering race conditions, writing TLA+ specifications from codebases, performing model checking on consensus/replication protocols, or setting up Lamport Agent workflows. Triggers on: "verify distributed system", "formal verification", "TLA+ spec", "model checking", "find race condition", "prove correctness", "CRAQ", "Paxos verification", "Raft verification", "chain replication verification", "distributed consensus verification".

2026-05-200

ソース

aresbit

aresbit/claude-skills

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

name

hm-sa-skill

description

HarmonyOS System Ability Manager (SAMgr) Skill

Overview

Knowledge Domains

This skill covers four domains. Load the relevant reference file based on the task:

Domain	Reference	When to Load
Architecture & Concepts	references/hm-sa-architecture.md	Understanding SAMgr's role, boot sequence, SA lifecycle, data structures, registration modes
API Reference	references/hm-sa-api-reference.md	Writing SA code, Proxy/Stub patterns, registration macros, death notifications
Source Code Structure	references/hm-sa-source-structure.md	Navigating the repo, finding files, understanding build config, SA .cfg format

Quick Reference

SAMgr's Four Roles

Service Registry — Central table mapping SA ID → proxy object
Lifecycle Manager — OnStart/OnStop, crash detection, auto-restart
IPC Router — Local via Binder, cross-device via DSoftBus
Capability Scheduler — Boot ordering, priority, on-demand loading

SA Lifecycle

Register → Publish → Discovery → IPC Invocation → Reclamation

Core API (C++)

// Get SAMgr client
sptr<ISystemAbilityManager> samgr =
    SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();

// Register SA
samgr->AddSystemAbility(saId, new MyAbility());

// Get SA proxy
sptr<IRemoteObject> obj = samgr->GetSystemAbility(saId);

Boot Sequence

init → parse .cfg → SAMgr daemon → foundation (safwk + samgr) → appspawn → apps

Source Repo

GitHub: https://gitcode.com/openharmony/systemabilitymgr_samgr
Path: foundation/systemabilitymgr/samgr/

Fetching Official Docs

To refresh the fetched Huawei developer docs, run:

# Fetch IPC Kit docs (preset)
python3 scripts/fetch_sa_docs.py --preset ipc --out-dir references/fetched-docs

# Fetch a single doc by slug
python3 scripts/fetch_sa_docs.py --slug ipc-rpc-overview --out /tmp/doc.md

# List all known working slugs
python3 scripts/fetch_sa_docs.py --list-slugs

Known working slugs:

ipc-rpc-overview — IPC Kit V13 overview (current)
ipc-rpc-overview-0000001427584740-V2 — IPC RPC V2 overview (archived)

Key Comparison: Android vs HarmonyOS

Dimension	Android	HarmonyOS SAMgr
Service Management	Dispersed (app-driven)	Unified (system-driven)
Lifecycle	App-controlled	System-controlled
Cross-device	None built-in	Natively supported
Crash Recovery	Limited	Auto-restart + client notification

Recognized SA IDs

SA ID	Service
3001	PowerManager
3002	LocationService
3400	BundleMgrService