dale

Any time a markdown file is edited in the docs/ directory, this skill should be run.

Quality

32%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/dale/SKILL.md

Quality

Content

42%

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

The skill defines a clear linting workflow with a well-structured output format, but suffers from missing supporting files (rules and schema) that are critical to its function. The persona framing adds unnecessary verbosity, and the lack of concrete examples of rule files or validation steps weakens both actionability and workflow clarity.

Suggestions

Provide the referenced bundle files (rules/*.yml and references/rule-schema.yml) or include inline examples of rule definitions so the skill is self-contained enough to be actionable.

Remove or significantly trim the persona framing ('You are not a skill or an agent...') — Claude doesn't need this level of identity instruction; focus on the task mechanics.

Add error handling guidance: what to do if a rule file is malformed, if the target document doesn't exist, or if the rules directory is empty.

Include at least one complete example of a rule YAML file and show how it maps to a detected violation in the output table.

Dimension	Reasoning	Score
Conciseness	The content has some unnecessary framing (e.g., 'You are not a skill or an agent. You are a piece of software—a linter, called Dale') and repetitive instructions. The persona setup is verbose, and some instructions like 'Do not talk to the user' are things Claude can infer. However, the core workflow and output format are reasonably tight.	2 / 3
Actionability	The skill provides a clear step-by-step loop for processing rules and a concrete output table format with an example. However, it lacks executable code/commands—there are no actual commands to run, no concrete examples of rule YAML files, and the references to ./rules/*.yml and /references/rule-schema.yml are not backed by any provided bundle files, making the guidance incomplete.	2 / 3
Workflow Clarity	The workflow is clearly sequenced (read rule, check document, note violations, output table) with a Todo-based tracking mechanism. However, there are no validation checkpoints or error recovery steps—e.g., what happens if a rule file is malformed, if the document path is invalid, or if the rules directory is empty. For a linting operation that processes multiple files, these gaps matter.	2 / 3
Progressive Disclosure	The skill references ./rules/*.yml and /references/rule-schema.yml but no bundle files are provided, making these references dead ends. There's no way to evaluate or use the skill without these supporting files, and the skill doesn't provide any inline fallback or summary of what those files contain.	1 / 3
	Total	7 / 12 Passed

Description

22%

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

This description is severely lacking because it only specifies a trigger condition ('markdown file edited in docs/') without explaining what the skill actually does. A skill description must communicate both purpose and trigger conditions to enable Claude to make informed selection decisions. As written, Claude would know when to invoke it but have no idea what it accomplishes.

Suggestions

Add a clear statement of what the skill does (e.g., 'Validates formatting, updates table of contents, and checks links in documentation files').

Reframe the trigger guidance using a 'Use when...' clause and include natural user terms like '.md files', 'documentation', 'docs update'.

Describe the concrete outputs or transformations the skill produces so Claude can distinguish it from other documentation-related skills.

Dimension	Reasoning	Score
Specificity	The description does not describe any concrete actions or capabilities. It only states when the skill should be triggered ('when a markdown file is edited') but says nothing about what the skill actually does.	1 / 3
Completeness	The description answers 'when' (editing markdown files in docs/) but completely fails to answer 'what does this do'. There is no indication of the skill's purpose, actions, or outputs.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'markdown file', 'docs/ directory', and 'edited', which are somewhat natural terms. However, it lacks variations (e.g., '.md files', 'documentation') and doesn't cover what users might actually say when needing this skill.	2 / 3
Distinctiveness Conflict Risk	The scope is narrowed to markdown files in the docs/ directory, which provides some distinctiveness. However, without knowing what the skill does, it could conflict with any other skill that also operates on documentation files.	2 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: netwrix/docs
Commit: 6b797b3

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.