BD code-dev-v1-tool-free
面向个人开发者的结构化编码工作流工具,包含版本化开发流程管控。核心能力:. 当需要code dev v1 tool相关能力的开发场景,提供标准化流程和配置说明。结构化开发工具免费版为个人开发者提供版本化的编码工作流管理。工具遵循"请求 → 规划 → 执行 → 验证 → 交付"的五步结构化流程,每个步骤都有明确的检查点,支持回溯与状态追踪.
面向个人开发者的结构化编码工作流工具,包含版本化开发流程管控。核心能力:.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ReferenceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: code-dev-v1-tool-free (ClawHub)
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 9, column 130: …置说明。结构化开发工具免费版为个人开发者提供版本化的编码工作流管理。工具遵循"请求 → 规划 → 执行 → 验证 → 交付"的五步结构化流程,每个步骤都有明… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 170 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (code-dev-v1-tool-free) differs from the folder (code-dev-v1-2)
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 56 steps
- 100Execution cost. Instruction body is 1900 tokens
- 100Running it twice. No mutating operations
- 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
- +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
- +2Single-language instructions
- +3Description length 170: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (16 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.
External checks
ClawHub: suspicious
The skill is mostly a local coding-workflow guide, but its instructions conflict about execution, network/API use, and credential handling, so users should review it before installing.
LLM: suspicious (high) · 25 Aug 2026