SKILLEMALL.ai

BC zentao

ZenTao Project Management API Integration | 禅道-ZenTao 项目管理 API 集成。Query products, projects, executions, stories, tasks, bugs / 查询产品、项目、执行、需求、任务、缺陷等。Triggers: 禅道,zentao, project management

ClawHub Agent Skills author: yoyoalphax v1.0.6 MIT-0 7 files body ≈ 2 049 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 60/100 · Has gaps — weak spots: when it triggers, consistency, running it twice

IntegrationOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
C
60/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: ZenTao Project Management API Integration | 禅道-ZenTao 项目管理 API 集成。… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "config"

Process rating: all ten parameters 60/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 32 mutating operations with no state check
  • 40Consistency. Frontmatter name (zentao) differs from the folder (yoyoalphax-zentao)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 196 steps
  • 100Execution cost. Instruction body is 2049 tokens

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)
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 187: enough signal without eating the budget
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 196 items
  • +3Output format is stated explicitly
  • +4Has examples (22 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This ZenTao integration is mostly purpose-aligned, but it exposes broad write and delete abilities without consistently enforcing the confirmations its documentation promises.
LLM: suspicious (high) · VirusTotal: · 29 May 2026