CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

validate

Run all validators against recent code changes

Quality

79%

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 ./plugins/pragma/skills/validate/SKILL.md
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.

The body is a highly actionable, well-sequenced orchestration workflow with executable bash, exact Task prompts, and a complete results template including explicit verdict/validation logic. Minor conciseness gains are available in the repeated per-language Task lists.

DimensionReasoningScore

Conciseness

Efficiently instructs with concrete bash, Task prompts, and a compact markdown template; minor padding in the repeated per-language Task lists that could be condensed.

4 / 5

Actionability

Fully executable: copy-paste git-diff bash, exact Task tool prompts, validator-to-extension mapping, and a ready-to-fill markdown results template covering common cases.

5 / 5

Workflow Clarity

Four clearly sequenced steps (detect changes, run validators in parallel, aggregate, verdict) with an explicit validation checkpoint: HARD/SHOULD/WARN classification and a defined PASS/FAIL verdict logic.

5 / 5

Progressive Disclosure

Single self-contained body under 50 lines with well-organized section headers and no need for external references, satisfying the simple-skill exception.

5 / 5

Total

19

/

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 clearly states what the skill does but omits an explicit 'Use when...' trigger, capping completeness, and lacks natural user-facing synonyms and file-extension triggers. It is distinct as an orchestrator but would benefit from explicit trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing staged/recent changes before commit or when the user asks to lint/validate code changes.'

Include natural trigger terms users would say, such as 'lint my changes', 'review before commit', and file extensions like '.go', '.py', '.ts'.

Optionally enumerate the validators it orchestrates (go-effective, python-style, security, etc.) to strengthen specificity.

DimensionReasoningScore

Specificity

States a concrete action ('Run all validators against recent code changes') naming the domain and the operation, but does not enumerate the specific validators or change-detection logic in the description itself.

4 / 5

Completeness

Clearly answers 'what' (run validators against recent code changes) but provides no 'Use when...' clause, so the 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Includes relevant keywords like 'validators', 'code changes', and 'recent', but lacks natural synonyms a user would say (e.g. 'lint', 'review my changes', 'check before commit') and any file-extension triggers.

3 / 5

Distinctiveness Conflict Risk

The orchestrator role ('Run all validators') plus 'recent code changes' gives it a distinct niche with only minor overlap risk against individual validator skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

peteski22/agent-pragma

Path

plugins/pragma/skills/validate/SKILL.md

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.