BD kurobbs-wiki
库街区（kurobbs）鸣潮 WIKI 资料查询 + 查看自己账号角色。当用户询问鸣潮（游戏）的角色/共鸣者、武器、武器投影、声骸、合鸣效果、敌人、全息战略、合成道具、任务/活动/特殊道具、补给、资源、素材、角色攻略、玩法攻略、区域探索、新手入门、版本攻略等图鉴或攻略信息时使用；也可通过 my 命令登录库街区账号查看自己拥有的角色（my roles）、用自己角色配队（my team）。可列出分类下的条目、获取词条详情、按名称搜索词条，全部通过公开 JSON API 查询。★ 注意：鸣潮 WIKI 查询无需登录；但查"我有什么角色/我的账号角色"需要 my login 登录一次。
库街区（kurobbs）鸣潮 WIKI 资料查询 + 查看自己账号角色。当用户询问鸣潮（游戏）的角色/共鸣者、武器、武器投影、声骸、合鸣效果、敌人、全息战略、合成道具、任务/活动/特殊道具、补给、资源、素材、角色攻略、玩法攻略、区域探索、新手入门、版本攻略等图鉴或攻略信息时使用；也可通过 my…
As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Risky intent
intent-offensive-securityREADME.en.md:149Offensive-security / dual-use content (legitimate for authorised testing; review intended use)├── post_fetch.py # Community post media fetching (Playwright to bypass WAF)
Files scanned: 13. 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")
Process rating: all ten parameters 44/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
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70Execution cost. Instruction body is 4503 tokens
- 100Steps. 102 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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
- -2localhost URLs: will not work for another user
- -238 emoji in the instructions: noise for the model
- -31 of 3 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 292: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 102 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.