SKILLEMALL.ai
GitHub ↗ RU Sign in

BD harmonyos-dev

HarmonyOS 应用开发技能（覆盖 5.0~6.1 版本）。基于 ArkTS 语言，支持 Stage 模型应用开发、 ArkUI 声明式 UI、UIAbility 生命周期、资源管理、权限配置、媒体处理、AI 集成、 分布式流转等完整开发流程。当用户提到 HarmonyOS、鸿蒙应用开发、ArkTS、Stage模型、 HAP/HAR/HSP 包开发、ArkUI 组件、分布式能力时触发。

ClawHub Agent Skills author: yhongm v1.0.1 MIT-0 12 files body ≈ 4 615 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
D
42/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "trigger"
  • note frontmatter-key unknown frontmatter key "hermes"

Process rating: all ten parameters 42/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Execution cost. Instruction body is 4615 tokens
  • 100Steps. 44 steps
  • 100Consistency. Name and required fields are in place

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -251 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 196: enough signal without eating the budget
  • +4Structure: 54 headings
  • +3Step-by-step instructions: 44 items
  • +4Has examples (16 code blocks)
  • +4Reference files are cited in the instructions (9 of 9)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.

External checks

ClawHub: clean
This is a documentation-only HarmonyOS development skill, and the risky-looking examples are relevant developer references rather than actions the skill runs itself.
LLM: benign (high) · VirusTotal: · 29 May 2026