SKILLEMALL.ai
GitHub ↗ RU Sign in

BC app-dev-workflow

通用应用软件开发完整工作流（HarmonyOS版）。支持从需求到部署的全流程开发管理。 包含：产品功能设计、代码生成、TDD开发、调试诊断、编译验证、版本管理。 适用于各类HarmonyOS应用的快速开发。 当用户需要开发HarmonyOS应用、生成代码、管理开发进度、进行TDD开发时触发。 关键词：开发应用、生成代码、TDD、调试、编译检查、版本管理

ClawHub Agent Skills author: ShiXiangYu2 v1.0.0 MIT-0 33 files · 21 scripts body ≈ 1 516 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureWriting and documentsSoftware developmentData and analyticstype 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
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
69
Run on models
none yet
Process rating
C
53/100
Has gaps
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-background-process scripts/mock-server.sh:392
    Starts a background / autostarted process (test fixture / example file)
    MOCK_PORT=$PORT MOCK_DELAY=${DELAY:-0} nohup node server.js > ../mock-server.log 2>&1 &
    fixture

Files scanned: 33. 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")

Process rating: all ten parameters 53/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
  • 100Tools and files. No external tools needed
  • 100Steps. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1516 tokens
  • 100Running it twice. No mutating operations

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
  • -32 of 21 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 177: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (15 code blocks)

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

External checks

ClawHub: suspicious
Most of this is a normal HarmonyOS development workflow, but a bundled demo script appears copied from a coffee-app project and can modify a user's project with unrelated demo-mode code.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026