dcli-tools-reference

Documents parameters and usage examples for 41 HarmonyOS dcli development tools.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/YrracOwl/dsh-hmos-sidebar --skill dcli-tools-reference-yrracowl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcli-tools-reference
Source: https://github.com/YrracOwl/dsh-hmos-sidebar/tree/main/packages/dsh-hmos-sidebar/presets/native-harmonyos/skills/dcli-tools-reference
Command: npx skills add https://github.com/YrracOwl/dsh-hmos-sidebar --skill dcli-tools-reference-yrracowl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building, deploying, or debugging HarmonyOS apps through dcli__* tools, agents often guess wrong parameter names, miss required fields, or misuse signing configurations. This Skill provides the authoritative parameter reference for all 41 native tools so calls are correct on the first attempt. ## Core Features & Use Cases - Complete Parameter Tables: Required fields, types, enums, and defaults for every dcli__* tool covering build, device control, emulator, UI automation, logs, docs, and signing. - High-Frequency Examples: Ready-to-use JSON payloads for common tasks like building a debug product, installing a signed HAP, or querying API signatures. - Operational Rules: Guidance on multi-project projectPath usage, debug-only HAP installation (avoiding error 9568322), dual signing configuration, and devEcoHome resolution. - Use Case: Before running a release build on a real device, consult this Skill to confirm dcli__build_project needs product, modules, and buildMode, then use dcli__install_hap with the debug-signed HAP path. ## Quick Start Ask the agent to check this Skill for the exact parameters of dcli__build_project before building your HarmonyOS project.

Frequently Asked Questions about dcli-tools-reference

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

FAQPage Schema
How do I build a HarmonyOS project with dcli tools?

Use dcli__build_project with optional projectPath, product, modules, and buildMode parameters. For a debug build of a dual-product project, pass product "debug", modules ["entry@debug"], and buildMode "debug".

How to install a HAP on a real HarmonyOS device?

Use dcli__install_hap with the absolute hapPath to a debug-signed package such as entry-debug-signed.hap. Installing default or release signed packages on a real device fails with error 9568322.

Which tool should I use to look up HarmonyOS API signatures?

Use dcli__api_lookup as the single entry point. It queries SDK .d.ts signatures across component, api, kits, arkts, and hms scopes plus local documentation hits, so one call covers ArkTS and ArkUI API checks.

Does dcli__lsp_check work across multiple projects?

Yes, dcli__lsp_check keeps a persistent diagnostic instance per project and accepts a projectPath parameter to target a specific project. If the instance hangs, restart it with dcli__lsp_restart.

Why does installing a release HAP fail on a real device?

Real-device debugging only accepts debug-signed packages. Installing a default or release signed HAP triggers error 9568322, so always install the entry-debug-signed.hap artifact instead.

What parameters are required for dcli__configure_dual_signing?

It requires release and debug keystore files, passwords, key aliases, profiles, and certificate paths. By default it only previews changes; set apply to true to back up and write the build-profile.json5 configuration.