SKILLEMALL.ai

AD omc-omx-orchestrator

异步派发编码任务到 OMC (claude -p) 或 OMX (omx exec)。触发词:"用omc" "用omx" "派任务" "后台编码" "异步任务" "omc跑" "omx跑" "claude跑" "codex跑" "派发OMC" "派发OMX"。

ClawHub Agent Skills author: qiuscut v4.3.0 MIT-0 6 files body ≈ 4 048 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

ProcedureAI and agentsSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
99
Quality 40%
81
Run on models
none yet
Process rating
D
46/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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-background-process SKILL.md:44
    Starts a background / autostarted process (quoted — discussed, not commanded)
    3. **进程独立存活**:`os.setsid` 创建独立进程组,主 Agent 死亡不影响子进程
    quoted

Files scanned: 6. 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 "source"
  • note frontmatter-key unknown frontmatter key "created_at"
  • note frontmatter-key unknown frontmatter key "updated_at"

Process rating: all ten parameters 46/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
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
  • 70Execution cost. Instruction body is 4048 tokens
  • 100Steps. 68 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low 19 top-level sections: this looks like several domains in one skill

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 2 example trigger phrases
  • +3Description length 130: enough signal without eating the budget
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 68 items
  • +4Has examples (10 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This is a disclosed background coding-task orchestrator, but it gives downstream agents broad local authority by default and uses activation and cleanup rules that need careful review.
LLM: suspicious (high) · VirusTotal: · 29 May 2026