lint-and-validate

Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/lint-and-validate/SKILL.md

The canonical home for this skill is jbvc/lint-and-validate

Quality

Content

72%

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

The body is highly actionable with concrete executable commands and good file structure. Its weak spots are minor verbosity from duplicated emphasis and a workflow checkpoint that points to an undefined report section.

Suggestions

Define or remove the 'FINAL AUDIT REPORT' reference so the validation checkpoint is concrete, or replace it with the actual script output to inspect.

Collapse the redundant 'MANDATORY' and 'Strict Rule' statements into a single rule and drop '(Fast & Modern)' to tighten the token budget.

Avoid repeating 'npm run lint && npx tsc --noEmit' in the Quality Loop since it already appears in the Node.js procedures.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with direct commands, but it carries redundant emphasis ('MANDATORY' note vs 'Strict Rule'), an editorial '(Fast & Modern)', and repeats 'npm run lint && npx tsc --noEmit' already shown in the Node section.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands per ecosystem (e.g. 'npx eslint "path" --fix', 'ruff check "path" --fix', 'mypy "path"') plus a runnable scripts table.	3 / 3
Workflow Clarity	The Quality Loop sequences steps with a Fix & Repeat feedback loop, but the validation checkpoint references a 'FINAL AUDIT REPORT' section that is never defined in the skill, leaving the checkpoint implicit.	2 / 3
Progressive Disclosure	A short, well-sectioned skill (under 50 lines) with one-level-deep, clearly signaled script references (scripts/lint_runner.py, scripts/type_coverage.py) that exist in the bundle.	3 / 3
	Total	10 / 12 Passed

Description

82%

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 is strong: it explicitly covers what the skill does, when to use it, and lists natural trigger keywords. Its main weakness is that several trigger terms are generic verbs that risk overlapping with unrelated skills.

Suggestions

Tighten generic triggers like 'check', 'validate', and 'format' with qualifiers (e.g. 'lint check', 'validate types') to reduce conflict with other skills.

Replace the abstract phrase 'quality control procedures' with a couple of concrete actions to lift specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and some actions ('quality control, linting, and static analysis procedures') but lists categories rather than multiple specific concrete operations, unlike the score-3 example.	2 / 3
Completeness	Clearly states what it does and gives explicit when-guidance ('Use after every code modification') plus explicit trigger keywords, satisfying both halves.	3 / 3
Trigger Term Quality	Explicitly lists natural terms users would say ('lint, format, check, validate, types, static analysis'), giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The lint/static-analysis niche is clear, but generic trigger verbs like 'check', 'validate', and 'format' could plausibly overlap with other skills.	2 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/lint-and-validate/SKILL.md
Commit: 04514f0

Reviewed: about 11 hours 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.