SKILLEMALL.ai

AD e2e-delivery

端到端需求/缺陷交付驱动器:给定一个 PingCode 工作项 URL/ID 或自然语言描述,自动串联"准备→开发→提交→验证→交付"五个阶段, 并沿路埋点,流程结束时产出 Markdown 报告并同步到 REDoc。 触发条件(满足任一即触发): (1) 用户说「帮我交付需求 xxx」「跑一遍端到端交付」「driver e2e」; (2) 用户给出 PingCode 工作项链接/ID 并表达"从头做到尾"的意图; (3) 用户自然语言描述一个新需求/缺陷、希望一站式完成。 不触发:仅查看工作项详情(由 pingcode-assistant-pro 处理)、仅创建 MR(由 yunxiao-assistant 处理)、 只想跑单一步骤(如只提测、只合并)。

ClawHub Agent Skills author: insistcp v1.0.0 MIT-0 8 files body ≈ 727 tokens Open the sourceclawhub.ai analyzed 5 d ago

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

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
D
43/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: 8. 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 43/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. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 27 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 727 tokens
  • low The response is described with custom markup (4 tags): a typed call is more reliable

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 332: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 27 items
  • +4Reference files are cited in the instructions (5 of 5)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This skill is a powerful end-to-end delivery automation tool, but it can change your local environment and external project records automatically without enough confirmation gates.
LLM: suspicious (high) · 9 Jul 2026