samber-lo

Use when writing or refactoring Go collection/pointer helper code in OpenMeter, especially when choosing between standard library slices/maps helpers and github.com/samber/lo for cloning, copying, equality, sorting, pointer literals, slice-to-map transforms, map keys/values, mapping, filtering, grouping, uniqueness, set-like conversions, and map entry transformations.

Quality

92%

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

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

A tight, highly actionable helper catalog with executable signatures and a worked Examples block, well-organized as a self-contained single file. The only weakness is the inline version pin, which the rubric treats as time-sensitive information that should live in a deprecated/old-patterns section.

Suggestions

Move or isolate the version pin 'github.com/samber/lo v1.53.0' into a small 'Pinned versions' or 'Old patterns' note so the main guidance stays version-neutral and token-efficient.

Consider splitting the long Common Helpers catalog into a references file if the body grows further, keeping SKILL.md as a decision/overview pointer to preserve progressive disclosure.

Add a one-line validation hint for the *Err variants (e.g. 'the first error stops the transform; surface it to the caller') to make the error-path workflow explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept-explanation fluff, but it inlines the time-sensitive version pin 'github.com/samber/lo v1.53.0' rather than placing it in a deprecated/old-patterns section, which the rubric flags as a conciseness penalty. It is not a level 3 because of that inline version-sensitive detail.	2 / 3
Actionability	It gives concrete, executable guidance — exact function signatures with argument orders (e.g. 'lo.Map(items, func(item T, index int) R)') and a copy-paste-ready Examples block — matching the fully-executable anchor.	3 / 3
Workflow Clarity	As a single-purpose decision skill (stdlib-first vs lo), the core action is unambiguous and the Correctness Notes supply the equivalent of validation checkpoints (e.g. 'Sort keys or results before comparing, logging, serializing, or asserting on order'). No destructive/batch loop is required, so no cap at 2 applies.	3 / 3
Progressive Disclosure	It is a self-contained single file with no bundle files and no nested references, organized into clear sections (Imports, Standard Library First, Common Helpers, Correctness Notes, Examples), satisfying the well-organized-sections criterion for skills that need no external references.	3 / 3
	Total	11 / 12 Passed

Description

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

A strong, specific description with an explicit 'Use when...' trigger, concrete capability list, and a clear niche that minimizes conflict risk. It uses the standard third-person/trigger form consistent with the good examples.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete actions — 'cloning, copying, equality, sorting, pointer literals, slice-to-map transforms, map keys/values, mapping, filtering, grouping, uniqueness, set-like conversions, and map entry transformations' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly answers both what (the listed helper operations) and when, opening with 'Use when writing or refactoring Go collection/pointer helper code in OpenMeter, especially when choosing between...', satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	It uses natural terms a developer would actually say — 'writing or refactoring Go collection/pointer helper code', 'standard library slices/maps helpers', 'github.com/samber/lo' — giving good coverage rather than opaque jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply defined — stdlib slices/maps vs samber/lo within OpenMeter — making it unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
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: openmeterio/openmeter
Path: .agents/skills/samber-lo/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.