CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

go-proverbs

Validate Go code changes against Go Proverbs

Quality

68%

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/go-proverbs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a well-structured, actionable validator with concrete commands, explicit detection rules, and a complete output schema; its main weaknesses are minor redundancy and a couple of vague step instructions rather than structural problems.

DimensionReasoningScore

Conciseness

The body is efficient and free of concept over-explanation, but the proverb list appears twice (actionable rules and the raw fallback list) and the 'Why HARD'/'Justification' lines are mild padding, keeping it just below a 5.

4 / 5

Actionability

Provides a copy-paste git diff command, concrete per-proverb 'Look for'/'Should be' detection criteria, and a complete JSON output schema with example values; minor gaps like the vague Step 3 'Read each changed Go file' and 'process in batches' keep it at 4.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with an explicit WebFetch fallback error path and a pass/fail report checkpoint; as a read-only validator it is not destructive/batch-modifying so the cap does not apply, but no explicit check-then-fix feedback loop prevents a 5.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references; with no bundle files present, all content is appropriately inline, though the inline fallback proverb list and full JSON schema example are mild candidates for a reference file.

4 / 5

Total

16

/

20

Passed

Description

48%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 carves a clear, distinct niche but is minimal: one action verb and no explicit usage trigger, which leaves completeness and specificity in the lower-mid range.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when reviewing Go code changes for adherence to Go Proverbs design philosophy.'

List 1-2 more concrete actions beyond 'validate', such as 'checks concurrency and error-handling patterns' to lift specificity.

Include natural trigger synonyms like 'Go review', 'idiomatic Go', or '.go files' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Go code changes") but relies on a single generic verb ("Validate") with one reference framework, matching the score-2 anchor 'Processes PDF files' rather than the 1-2 concrete actions required for a 3.

2 / 5

Completeness

The 'what' is clear (validate Go code changes against Go Proverbs) but there is no 'Use when...' or equivalent trigger clause, so per the rubric cap completeness cannot exceed 3.

3 / 5

Trigger Term Quality

"Go code changes" and "Go Proverbs" are relevant keywords a knowledgeable user might say, but common variations like 'review', 'lint', or '.go files' are missing, matching the score-3 anchor 'Works with PDF files'.

3 / 5

Distinctiveness Conflict Risk

The 'Go Proverbs' philosophy niche is mostly distinct from generic Go linters and style tools, with only minor overlap risk when a user requests a generic Go review without naming proverbs.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

peteski22/agent-pragma

Path

plugins/pragma/skills/go-proverbs/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.