Name: golang-samber-ro
Rating: 68.8 (1 reviews)
Author: samber

golang-samber-ro

Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill).

Quality

85%

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

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

A well-structured reference skill with executable examples, strong decision tables, and clean progressive disclosure into real bundle files. Minor conciseness and actionability refinements would push it to the top anchor.

Suggestions

Trim the conceptual restatement in 'Why samber/ro' (e.g. the goroutine/channel pain points) to assume Claude's existing knowledge of Go concurrency.

Add one or two short inline code snippets for the highest-frequency operators (e.g. Merge, CombineLatest, Retry) alongside the operator tables to lift actionability.

Consider a brief 'quick start' section at the top so the most common build-a-pipeline flow is immediately visible before the conceptual comparison tables.

Dimension	Reasoning	Score
Conciseness	Mostly lean — uses tables and executable code and assumes Claude's Go competence — but a few sentences restate concepts Claude knows (e.g. 'Go channels + goroutines become unwieldy for complex async pipelines: manual channel closures, verbose goroutine lifecycle...') that could be trimmed.	4 / 5
Actionability	Provides an executable Pipe2/Subscribe/Collect example, concrete operator tables, the `go get` command, and specific function names; minor gaps in that many operators are only named in tables rather than demonstrated.	4 / 5
Workflow Clarity	As a conceptual/reference skill rather than a destructive multi-step process, it supplies clear decision guidance via 'When to use which tool' and 'Common Mistakes' tables; no validation feedback loop is required here, and the single-purpose guidance is unambiguous.	4 / 5
Progressive Disclosure	The body is a concise overview that splits detailed material into four real, well-signaled one-level-deep references (subjects-guide.md, operators-guide.md, plugin-ecosystem.md, patterns.md), all present in ./references/, with clear navigation.	5 / 5
	Total	17 / 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.

A strong, specific description that names concrete capabilities, includes explicit 'Apply when...' trigger guidance, and disambiguates from the related samber/lo skill. Slight room for more natural synonym coverage, but overall excellent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'declarative pipelines via Pipe', 'cold/hot observables', '5 subject types (Publish, Behavior, Replay, Async, Unicast)', '40+ plugins (HTTP, cron, fsnotify, JSON, logging)', 'automatic backpressure, error propagation' — comprehensive coverage.	5 / 5
Completeness	Clearly and explicitly answers both 'what' (detailed capability list) and 'when' ('Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines...') with a concrete 'Not for...' boundary.	5 / 5
Trigger Term Quality	Strong natural trigger phrases ('reactive streams', 'event-driven programming', 'asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go') with good synonym coverage; a few common variations (e.g. 'RxGo', 'observables') are absent, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche (samber/ro reactive streams in Go) with an explicit disambiguating boundary ('Not for finite slice transforms (→ See samber/lo skill)'), minimizing conflict with sibling skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
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: 3 missing	Warning

	Total	13 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-samber-ro/SKILL.md
Commit: 19a0626

Reviewed: 1 day 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.