AB jishudb
安装或连接 JishuDB，适用于首次设置、找不到服务、配置 Agent MCP、 连接失败、OAuth 或 Token 授权，以及选择本机或远程连接方式。 不用于知识库问答或完整 MCP 验收。 / Install, locate, connect, or troubleshoot JishuDB for an agent, including Desktop setup, service discovery, MCP transport, connection failures, and OAuth or Token authorization. Reuse a working service and verify the actual client connection; not for knowledge search or full MCP acceptance.
安装或连接 JishuDB，适用于首次设置、找不到服务、配置 Agent MCP、 连接失败、OAuth 或 Token 授权，以及选择本机或远程连接方式。 不用于知识库问答或完整 MCP 验收。 / Install, locate, connect, or troubleshoot JishuDB for an…
As a process B 72/100 · Nearly there — weak spots: result and completion, progress reporting
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 62, 217): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 72/100
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4909 tokens
- 85Steps. 52 steps, 1 vague phrases
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 392: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.