Harmonyos Build Deploy
CheckedHelps with building, deployment as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add fadinglight9291117/arkts_skills --skill harmonyos-build-deploy -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
fadinglight9291117
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned fadinglight9291117/arkts_skills at 2470cec124.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 2470cec124
- Manifest
- harmonyos-build-deploy/SKILL.md
- Scanned
- 3 files, 551 lines
About this skill
What it does
This skill enables AI agents to automate building, cleaning, packaging, and installing HarmonyOS applications as part of a workflow. It focuses on providing specific build and deployment commands for HarmonyOS projects using tools like hvigorw and hdc. Crucially, the skill requires confirmation from the user before executing any operation to ensure accuracy and prevent unintended actions.
When to use it
- Automating incremental builds of HarmonyOS applications.
- Performing a full clean build and deployment pipeline for HarmonyOS apps.
- Installing a HarmonyOS application onto a connected device.
- Managing project dependencies using
ohpm. - When needing precise control over the build and deployment process in an automated workflow.
Key capabilities
- Operation Confirmation: Requires user confirmation before executing any build or deploy operation (Clean, Install Dependencies, Build Project, Install to Device, Full Pipeline).
- Build Commands: Provides
hvigorwcommands for assembling HAP/APP packages. - Deployment Commands: Includes
hdccommands for installing applications onto a device and managing file transfers. - Dependency Management: Supports using
ohpmfor dependency installation. - Workflow Automation: Facilitates automated build, clean, and deployment workflows.
Example prompts
- "Can you please perform a full pipeline build of my HarmonyOS app?"
- "I need to install the latest version of my application onto my device. What steps should we take?"
- "Clean the build artifacts for my HarmonyOS project."
Tips & gotchas
- User Confirmation is Required: The agent must confirm which operation(s) the user wants to perform before proceeding.
- Git Bash Considerations: If using Git Bash on Windows, remember to disable MSYS path conversion (
export MSYS_NO_PATHCONV=1) when runninghdccommands. - Output Path: Build output is located in the
outputs/directory.