CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

go-effective

Validate Go code against Effective Go and idiomatic conventions

Quality

67%

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

Quality

Content

68%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, mostly lean rule catalog with concrete examples, an executable input command, and a precise output schema. Its main gap is workflow clarity: it is a batch validation operation without an explicit validation/verification checkpoint or feedback loop, which caps that dimension.

Suggestions

Add an explicit validation/verification checkpoint for batch runs (e.g., after processing, confirm files_checked matches the changed-file count and re-run on parse errors), which would lift workflow_clarity above the batch cap of 3.

Split the HARD RULES / STRONG CONVENTIONS / WARNINGS catalogs into a referenced RULES.md to shorten the main body and improve progressive disclosure.

Trim the redundant scope restatements (the 'You do NOT...' block and 'Do not invent/relax/apply' lines overlap the Scope Declaration) to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is a lean rule catalog of bullet points with concrete inline examples (e.g., 'user.GetName() → user.Name()') and assumes Claude's competence; only minor redundancy (repeated scope statements, triple 'Do not...' lines) could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

It provides an executable bash one-liner for gathering changed files and a precise JSON output schema with concrete field examples, plus rules anchored by before/after examples; this is mostly executable guidance with only minor gaps (rules are guidelines rather than copy-paste code), matching the 'mostly executable; minor gaps' anchor.

4 / 5

Workflow Clarity

The sequence (gather changed files → read → evaluate rules in order → categorize HARD/SHOULD/WARN → emit JSON with pass/fail) is clear, but this is a batch file-processing operation with no explicit validation/verification checkpoint or error-recovery loop, so per the judging guideline batch operations without validation cap workflow clarity at 3.

3 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly signaled sections (Scope Declaration, HARD RULES, STRONG CONVENTIONS, WARNINGS, Output Requirements, References) with no nested references and only normative external links; at ~217 lines the rule catalog could arguably split into a reference file, leaving it at 'good structure; minor organization gaps' rather than a 5.

4 / 5

Total

15

/

20

Passed

Description

53%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 is clear and domain-specific but terse: it states what the skill does without a 'Use when...' trigger clause and with limited keyword coverage. It is distinguishable from sibling Go skills but would benefit from explicit use-when guidance and a few more natural trigger terms.

Suggestions

Add a 'Use when...' clause naming concrete triggers (e.g., 'Use when reviewing Go code for idiomatic style, naming, error handling, or Effective Go compliance').

Expand the action list beyond the single verb 'validate' to concrete checks (naming, error handling, interface design, control flow) to lift specificity.

Include natural synonyms users say ('Go style', 'idiomatic Go', 'Go code review') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Validate Go code against Effective Go and idiomatic conventions' names the domain (Go code) and one concrete action (validate against Effective Go), but offers only a single generic verb with no enumeration of what is checked, matching the anchor that names the domain with 1-2 actions but is not comprehensive.

3 / 5

Completeness

It gives a clear 'what' (validate Go code against Effective Go) but no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

'Go code' and 'Effective Go' are relevant keywords a user might say, but the description omits common variations or synonyms (e.g., 'Go style', 'idiomatic Go', 'lint', 'code review'), landing on the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

'Validate Go code against Effective Go and idiomatic conventions' carves a clear niche that is mostly distinct, with only minor overlap risk against closely related Go skills (e.g., go-proverbs, security) referenced in the body, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

13

/

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-effective/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.