CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

74

Quality

93%

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

87%

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 concise, actionable reference with excellent progressive disclosure and executable examples. Its only gap is the absence of an explicit, checkpointed multi-step workflow for building and verifying a reactive pipeline.

Suggestions

Add a short sequenced 'Build a pipeline' workflow (e.g., choose cold/hot → compose typed Pipe chain → handle all three events → bound with TakeUntil/context → verify with Collect) with an explicit validation/verification checkpoint before relying on the stream.

Include a one-line reminder to run `go vet`/`golangci-lint` or a quick `Collect` smoke test after wiring an observable, giving the pipeline-construction process a concrete feedback loop.

Cross-link the Common Mistakes fixes to the corresponding Best Practice numbers so the recovery path from a mistake is immediately findable.

DimensionReasoningScore

Conciseness

Lean, table-dense reference material that assumes Claude's competence and avoids explaining basic concepts (channels, goroutines, generics); every section earns its tokens with decision tables and operator catalogs.

3 / 3

Actionability

Provides a complete executable Go example (Pipe2 + Subscribe with all three callbacks and Collect), a concrete `go get` install command, and specific operator/subject names that are copy-paste ready.

3 / 3

Workflow Clarity

Decision guidance (when-to-use table, Common Mistakes, Best Practices) is well organized, but there is no explicit sequenced multi-step workflow with validation checkpoints of the kind the top anchor requires, and pipeline construction is only implicitly sequenced.

2 / 3

Progressive Disclosure

SKILL.md is a clear overview with four well-signaled, one-level-deep references (subjects-guide, operators-guide, plugin-ecosystem, patterns), all of which exist as real files, keeping detail out of the main body.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete, answering both what and when with natural user-facing terms and explicit disambiguation against a sibling slice skill. It uses appropriate third-person/imperative voice throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('150+ type-safe operators', '5 subject types (Publish, Behavior, Replay, Async, Unicast)', 'declarative pipelines via Pipe', '40+ plugins', 'automatic backpressure, error propagation, and Go context integration') rather than vague language.

3 / 3

Completeness

Clearly answers both what the skill does and when to use it via an explicit 'Apply when using or adopting samber/ro...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms users would say ('asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go') plus a concrete import-path trigger ('codebase imports github.com/samber/ro').

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (ReactiveX streams in Go) and explicitly disambiguates with 'Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill)', reducing conflict with sibling skills.

3 / 3

Total

12

/

12

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: 3 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.