BB dev-mentor
面向有经验的开发者的跨领域学习伴侣。帮助开发者学习不熟悉的领域， 通过连续对话引导用户从零完成一个项目的完整生命周期。 首批支持：后端开发（多语言）、数据库、服务器部署、Rust 系统编程。 专业名词自带解释，代码使用最新技术栈和最佳实践。支持多项目、连续对话。 触发词：学后端, 学Rust, 学开发, 从零做项目, 前端学后端, 后端学Rust, 教我做项目, 带我开发, 项目教学, learn backend, learn Rust, build project from scratch, coding mentor, dev companion. NOT for: 接手已有成熟项目（用 project-onboarding）、 纯理论学习、代码审查、生产环境故障排查。
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, running it twice
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 ≈ 7741 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 26 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 7741 tokens
- 100Steps. 445 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 27 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
- +5Description has no quoted example phrases that should trigger the skill
- -242 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 341: enough signal without eating the budget
- +4Structure: 100 headings
- +3Step-by-step instructions: 445 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.