CtrlK
BlogDocsLog inGet started
Tessl Logo

harness-generating

Harness 规范文档生成——harness-engineering 的子 skill,负责项目上下文感知、 信息收集、五大组件与技术规范文档的生成/修正、开发地图生成及总结报告。 由 harness-engineering 按生成类触发词路由调用,不独立触发。

56

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/harness-engineering/harness-generating/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, highly actionable workflow with strong validation gates and feedback loops and good file-level navigation, held back from a top score mainly by cross-section redundancy that inflates length.

DimensionReasoningScore

Conciseness

The body is information-dense with no beginner-concept padding and assumes Claude's competence, but it is lengthy (~400 lines) with real redundancy — the tooling.md prohibitions and the 'no workflow' rule are restated across step 1, step 3, step 3-D, and the quality checks, so it could be tightened.

3 / 5

Actionability

It provides concrete, executable commands — 'git ls-files -- AGENTS.md **/AGENTS.md', 'bash …/detect-standards.sh --json', 'bash …/harness-verify.sh', 'git rm --ignore-unmatch …', '/graphify .' — plus concrete file trees and decision tables, with only minor gaps where guidance stays rule-based rather than copy-paste.

4 / 5

Workflow Clarity

The six steps are explicitly sequenced with a TodoWrite checklist (gen-1…gen-6), and validation/feedback loops are present throughout: the 第五步 self-audit (对账→补检→合并), the 12-item 质量检查, and the hard 'harness-verify.sh … 直到 exit 0' gate with retry-until-pass — fully matching the checklist+feedback-loop anchor.

5 / 5

Progressive Disclosure

Structure is good: a clear reference table maps each file to purpose and 'when to read', references are one level deep and well-signaled, and detail is split into templates/best-practices files; however the body still inlines substantial rule blocks and decision tables, and most referenced paths resolve to the parent skill's bundle rather than this skill's own.

4 / 5

Total

16

/

20

Passed

Description

58%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a clear 'what' with several concrete actions and a distinct parent-routed niche, but it omits an explicit concrete trigger phrase and leans on jargon, leaving the 'when' only weakly specified.

Suggestions

Add an explicit 'Use when...' clause with concrete generation trigger phrases (e.g. '生成规范文档', '创建 AGENTS.md', '生成开发地图') so the when-trigger is concrete rather than only 'routed by parent'.

Expand trigger terms with natural user synonyms and the concrete artifacts the skill produces (AGENTS.md, docs/harness/, docs/dev-map/) to improve keyword coverage beyond technical jargon.

Name the '五大组件' explicitly in the description (上下文工程/架构约束/熵管理/工具能力/执行与验证) to lift specificity from abstract to comprehensive.

DimensionReasoningScore

Specificity

The description enumerates several concrete actions — '项目上下文感知', '信息收集', '五大组件与技术规范文档的生成/修正', '开发地图生成及总结报告' — giving comprehensive coverage of its scope, but '五大组件' is left abstract rather than named individually, leaving a minor gap.

4 / 5

Completeness

The 'what' is clear (generates spec docs, dev map, summary report), and a 'when' mechanism is present ('由 harness-engineering 按生成类触发词路由调用'), but there is no explicit 'Use when...' clause with concrete trigger phrases, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

It contains some relevant domain keywords ('规范文档生成', '开发地图', '总结报告') but relies heavily on technical jargon ('harness-engineering', '五大组件') and, because it is explicitly '不独立触发', lacks the natural user-facing trigger phrases and synonyms a user would actually say.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche as the generation sub-skill of harness-engineering and the explicit '不独立触发' routing keeps conflict risk low, though it remains part of a family of related harness sub-skills with minor overlap potential.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 4 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
TencentBlueKing/bk-bcs
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.