BF yunxiao-devops
与阿里云云效(Yunxiao)DevOps 平台交互,覆盖八大核心能力:项目协作 Projex、 代码管理 Codeup、流水线 Flow、应用交付 Appstack、制品仓库 Packages、 测试管理 Testhub、效能洞察 Insight、知识库 Thoughts。 当用户提到云效、Projex、Codeup、Flow、流水线、部署单、应用、版本、迭代、 工作项、需求、缺陷、任务、测试计划、制品仓库、Yunxiao、DevOps 时使用。 读 reference 选择:项目协作/工作项/迭代/版本/工时 → projex-guide.md; 流水线创建/YAML → pipeline-yaml-guide.md;工作流状态 → workflow-transitions.json。
As a process F 35/100 · Will not run — References files that are not bundled: scripts/config.mjs, scripts/daily-standup-card.mjs, scripts/my-workitems-card.mjs
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-background-processSKILL.md:203Starts a background / autostarted process# ⚠️ 必须用 nohup + disown,否则 exec session 回收时进程会被 SIGTERM 杀掉
-
low Dangerous commands
cmd-background-processSKILL.md:205Starts a background / autostarted process> /tmp/poll-pipeline-<runId>.log 2>&1 & disown $!
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/config.mjs - warning
missing-refreference to a missing file: scripts/daily-standup-card.mjs - warning
missing-refreference to a missing file: scripts/my-workitems-card.mjs - warning
missing-refreference to a missing file: scripts/create-workitem-flow.mjs - warning
missing-refreference to a missing file: scripts/effort-checkin-card.mjs - warning
missing-refreference to a missing file: scripts/commit-activity-card.mjs - warning
missing-refreference to a missing file: scripts/mr-review-card.mjs - warning
missing-refreference to a missing file: scripts/release-flow.mjs - warning
missing-refreference to a missing file: scripts/version-release-flow.mjs - warning
missing-refreference to a missing file: scripts/pipeline-log-card.mjs - warning
missing-refreference to a missing file: scripts/sprint-dashboard-card.mjs - warning
missing-refreference to a missing file: scripts/repo-init-flow.mjs - warning
missing-refreference to a missing file: scripts/testcase-card.mjs - warning
missing-refreference to a missing file: scripts/appstack-card.mjs - warning
missing-refreference to a missing file: references/workflow-transitions.json - warning
missing-refreference to a missing file: references/pipeline-yaml-guide.md - warning
missing-refreference to a missing file: references/projex-guide.md - warning
missing-refreference to a missing file: references/pipeline-yaml-syntax.md - warning
missing-refreference to a missing file: references/api-docs/INDEX.md - warning
missing-refreference to a missing file: references/user-mapping.json - warning
missing-refreference to a missing file: scripts/sync-feishu-task.mjs
Process rating: all ten parameters 35/100
- 0Tools and files. 21 referenced file(s) missing: scripts/config.mjs, scripts/daily-standup-card.mjs, scripts/my-workitems-card.mjs
- 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
- 30Running it twice. 9 mutating operations with no state check
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3509 tokens
- 100Progress reporting. Reports progress
- low 18 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 349: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (28 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.