CtrlK
BlogDocsLog inGet started
Tessl Logo

nested-tool

Nested monorepo component skill for harness doctor path resolution.

32

Quality

25%

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/tests/fixtures/good-project-owned-nested/apps/svc/.agents/skills/nested-tool/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

18%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 content body is effectively empty beyond a heading, providing no executable guidance, workflow, or structured material. It is not verbose simply because there is nothing there, which fails on actionability and workflow clarity.

Suggestions

Add concrete, executable guidance (commands or code snippets) for the path-resolution task the skill is meant to perform.

Document a sequenced workflow with explicit validation checkpoints, especially if path resolution involves destructive or batch operations.

Organize the body into clear sections (e.g., Quick start, Advanced) so the skill has navigable structure.

DimensionReasoningScore

Conciseness

The body is just '# nested-tool' — not verbose and free of over-explanation, but it carries no actual content to be lean-and-useful, so it sits at the midpoint rather than the 5 anchor which requires lean content that earns its tokens.

3 / 5

Actionability

There is no concrete code, command, or instruction anywhere in the body — it does not even describe a task, matching 'Entirely vague or abstract; no concrete code or commands'.

1 / 5

Workflow Clarity

No steps, sequence, or validation checkpoints exist; the body provides only a heading, matching 'Steps missing or incoherent; no sequence'.

1 / 5

Progressive Disclosure

Structure is minimal (a single heading) with no references and no bundle files present; it avoids a monolithic wall but offers no organized sections or navigation, fitting 'Minimal structure' better than the 3 anchor.

2 / 5

Total

7

/

20

Passed

Description

32%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 identifies a specific niche but does so in technical jargon, with only a minimal action and no explicit 'when to use' guidance. It is distinguishable from other skills yet under-specified on capabilities and triggers.

Suggestions

Add an explicit 'Use when...' clause stating the natural trigger phrases (e.g., 'Use when resolving nested monorepo paths for the harness doctor').

Replace internal jargon with user-facing terms and synonyms so the description matches what a user would actually say.

List 1-2 concrete actions the skill performs (e.g., 'resolves', 'validates') rather than naming only the domain.

DimensionReasoningScore

Specificity

The phrase 'harness doctor path resolution' names a narrow domain and one minimal action, but lists no concrete capabilities — closer to 'Names the domain but actions are minimal or generic' than the 3 anchor which expects 1-2 concrete actions.

2 / 5

Completeness

It offers a vague 'what' (a component skill for path resolution) and no 'when' clause at all; the missing 'Use when...' trigger guidance and vague what align with the 2 anchor rather than the 3 anchor's clear what.

2 / 5

Trigger Term Quality

Terms like 'nested monorepo component', 'harness doctor', and 'path resolution' are internal/technical jargon rather than phrases a user would naturally say; only one or two generic keywords are present, matching the 2 anchor.

2 / 5

Distinctiveness Conflict Risk

The niche ('harness doctor path resolution' in nested monorepos) is specific and unlikely to collide with unrelated skills, fitting 'Mostly distinct; minor overlap risk'; it stops short of 5 because the triggers are jargon, not crisp natural phrases.

4 / 5

Total

10

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.