CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-samber-mo

Monadic types for Golang using samber/mo — Option, Result, Either, Future, IO, Task, and State types for type-safe nullable values, error handling, and functional composition with pipeline sub-packages. Apply when using or adopting samber/mo, when the codebase imports `github.com/samber/mo`, or when considering functional programming patterns as a safety design for Golang. Not for nil-safety and zero-value design without this library (→ See `samber/cc-skills-golang@golang-safety` skill), nor for native error wrapping with fmt.Errorf, errors.Is and errors.As (→ See `samber/cc-skills-golang@golang-error-handling` skill).

71

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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, action-packed reference: executable code throughout, clear decision rules, and clean progressive disclosure to verified reference files. It is slightly verbose in a few framing sections but otherwise respects the context budget.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, explaining only Go-specific gotchas (e.g., the method type-parameter limitation); minor trimmable elements like the persona block and a few analogy columns keep it just below a 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Go code ('go get github.com/samber/mo', import statements, full Option/Result/Either/Do/Pipe snippets) plus concrete key-method lists and common patterns covering the typical cases.

5 / 5

Workflow Clarity

Decision guidance is clear and sequenced ('Use Result for errors, Either for alternatives', direct-method vs sub-package rule of thumb); no destructive or batch operations require validation checkpoints, and the reference-style structure is well organized.

4 / 5

Progressive Disclosure

The body is an overview that points to six one-level-deep reference files (monads-guide, option, result, either, pipelines, advanced-types), all verified present, clearly signaled via markdown links and organized for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

92%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 highly specific, complete, and distinctive, explicitly stating both what the skill provides and when to invoke it while fencing off adjacent skills. Its only minor weakness is a slightly technical, jargon-leaning trigger vocabulary rather than broad natural synonyms.

DimensionReasoningScore

Specificity

Enumerates seven concrete monadic types (Option, Result, Either, Future, IO, Task, State) plus three concrete use cases (type-safe nullable values, error handling, functional composition with pipeline sub-packages), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (monadic types for Golang using samber/mo) and 'when' ('Apply when using or adopting samber/mo, when the codebase imports... or when considering functional programming patterns'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a Go engineer would say ('samber/mo', 'when the codebase imports `github.com/samber/mo`', 'functional programming patterns', monadic type names); good coverage but slightly jargon-heavy and missing a few synonyms.

4 / 5

Distinctiveness Conflict Risk

Names the specific library and explicitly disambiguates from sibling skills via 'Not for nil-safety...' and 'nor for native error wrapping...' clauses with cross-references, giving a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 4 missing

Warning

Total

13

/

16

Passed

Repository
samber/cc-skills-golang
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.