go-types-conversion

Naming convention for type-translation files and functions. Use when creating or editing files that convert between domain, API, and DB types.

Quality

95%

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

Quality

Content

100%Weight 40%Scale 1-3

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 tight, actionable naming-convention reference: concrete Go signatures, a decision tree, explicit forbidden patterns, and verification guidance for renames. It assumes Claude's competence, avoids concept re-explanation, and is well-organized as a self-contained file.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — tables, decision trees, and code signatures with no padding or explanation of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Provides concrete, executable guidance: a file-naming table, real Go signatures, a forbidden-patterns list, and copy-ready suggestion phrasings rather than abstract direction.	3 / 3
Workflow Clarity	The decision tree is a clearly sequenced 4-step process, and the cleanup guidance includes a verification checkpoint ('Grep for the old name to catch misses') for the destructive rename path.	3 / 3
Progressive Disclosure	No bundle files are provided and none are needed; the single self-contained body is well-organized into clearly headed sections that read as an overview with easy navigation.	3 / 3
	Total	12 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 third-person, concise, and clearly answers both what and when with an explicit 'Use when' trigger. It is specific to its niche and low conflict risk; its only weakness is that it names a single action rather than enumerating multiple concrete actions.

Suggestions

Optionally expand the description to name one or two more concrete actions (e.g. 'rename mapper.go files') to push specificity toward the score-3 anchor.

Consider adding a common-variation synonym like 'mapping' or 'type conversion' alongside 'type-translation' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('type-translation files and functions') and an action ('naming') but does not list multiple concrete actions like the score-3 anchor; it is a convention skill so actions are narrow.	2 / 3
Completeness	Explicitly states what it does ('Naming convention for type-translation files and functions') and when to use it via an explicit 'Use when creating or editing files that convert between domain, API, and DB types' clause.	3 / 3
Trigger Term Quality	Includes natural terms a user would say when needing this skill — 'convert between domain, API, and DB types' and 'creating or editing files' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Go type-translation naming) with distinct, specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: openmeterio/openmeter
Path: .agents/skills/go-types-conversion/SKILL.md
Commit: 1cdc2cb

Reviewed: 9 days 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.