CtrlK
BlogDocsLog inGet started
Tessl Logo

precommit

Discover and run all pre-commit code quality checks (linters, type checks, i18n extraction) in a monorepo, auto-fix failures, and report results. Use when the user asks to run pre-commit checks, validate code before committing, or ensure CI checks pass locally.

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-structured, highly actionable instruction-only skill: phased workflow with validation feedback loops, concrete commands and discovery sources, and a clear output/report template. Its only weakness is minor verbosity in the example output block, which could be tightened without losing clarity.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows, but the full sample summary table and asides like "These sub agents can be run in parallel" are minor padding that could be trimmed — the efficient-with-trimmable-instances anchor rather than every-token-earns-its-place.

4 / 5

Actionability

Concrete file globs (`.github/workflows/*.yml`, `pnpm-workspace.yaml`), real commands (`make check-style`, `tsc --noEmit`, `prettier --write`, `ruff --fix`), an exact checklist template, and a report format make the guidance fully executable; per the instruction-only scoring note, the absence of code is not penalized.

5 / 5

Workflow Clarity

Three ordered phases (Discovery → Plan → Execute) with a checklist artifact and an explicit feedback loop ("Run → Evaluate → Fix → Re-run the check to verify the fix worked → Report") plus escalation to manual reporting match the anchor for clear sequencing with validation and error-recovery loops.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: the skill is a single self-contained file with well-signaled sections (Objective, Process phases, Output Format, Guidelines) and no inlined reference material that belongs elsewhere, so content placement is appropriate and navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

88%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.

A strong description that explicitly covers both what (discover, run, auto-fix, report code quality checks in a monorepo) and when (explicit "Use when…" triggers). Keyword coverage is good but could add common synonyms like "lint" or "pre-commit hooks" to sharpen trigger matching and distinctiveness.

DimensionReasoningScore

Specificity

"Discover and run all pre-commit code quality checks (linters, type checks, i18n extraction)… auto-fix failures, and report results" lists four concrete actions covering the full workflow (discover, run, fix, report), matching the comprehensive-coverage anchor rather than leaving minor gaps.

5 / 5

Completeness

It clearly states what the skill does in the first sentence and gives an explicit "Use when…" clause with three concrete trigger phrases, exactly matching the top anchor; not 4 because the when-guidance is already concrete and specific.

5 / 5

Trigger Term Quality

The trigger clause offers natural phrases ("run pre-commit checks", "validate code before committing", "ensure CI checks pass locally") but omits common variations such as "lint", "pre-commit hooks", or "make CI green", fitting the good-coverage-with-a-few-missing anchor.

4 / 5

Distinctiveness Conflict Risk

"pre-commit… in a monorepo" carves a clear niche, but triggers like "ensure CI checks pass locally" overlap with generic lint/CI/test-runner skills, so it is mostly distinct with minor overlap risk rather than fully minimal.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mattermost/mattermost-ai-marketplace
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.