BD jielong-cli
接龙活动管理工具（CLI版）。通过 jielong 命令行工具管理接龙活动。 支持创建、查看、修改、删除接龙活动、收费报名活动、打卡接龙活动， 以及查看报名列表、查看活动详情、管理填表项、控制活动状态（开始/结束/重启）、 删除报名记录、清空报名等操作。 触发场景： - 用户提到"创建接龙/报名/打卡"、"帮我发一个活动"、"查看报名"、"看看我的活动" - "帮我报名"、"代报名"、"我要参加"、"报名一下" - "删除活动"、"修改活动时间/名称/描述"、"添加填表项"、"删除报名" - "清空报名"、"结束活动"、"开始活动"、"重启活动"等 NOT for: 与接龙活动无关的请求。
接龙活动管理工具（CLI版）。通过 jielong 命令行工具管理接龙活动。 支持创建、查看、修改、删除接龙活动、收费报名活动、打卡接龙活动， 以及查看报名列表、查看活动详情、管理填表项、控制活动状态（开始/结束/重启）、 删除报名记录、清空报名等操作。 触发场景： -…
As a process D 48/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 2. 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
body-longSKILL.md body ≈ 6194 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 48/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
- 30Running it twice. 13 mutating operations with no state check
- 40Consistency. Frontmatter name (jielong-cli) differs from the folder (tianba-jielong)
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 6194 tokens
- 100Tools and files. No external tools needed
- 100Steps. 80 steps
- 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
- +3Output format is not stated: the model decides each time
- -219 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 298: enough signal without eating the budget
- +4Structure: 54 headings
- +3Step-by-step instructions: 80 items
- +4Has examples (51 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.