Skills golang-samber-ro

📦

golang-samber-ro

Name: golang-samber-ro
Author: samber

v1.2.2 Content revision r1 Safe ⚙️ External commands🌐 Network access

Build Reactive Go Pipelines with samber/ro

Asynchronous Go pipelines can become difficult to compose, cancel, and test. This skill guides reliable samber/ro designs with typed operators and lifecycle controls.

Supports: Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "golang-samber-ro" from https://skillstore.io/skills/samber-golang-samber-ro.md and its manifest at https://skillstore.io/api/skills/samber-golang-samber-ro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/samber-golang-samber-ro.md Signed manifest GET /api/skills/samber-golang-samber-ro/manifest Signed lockfile GET /api/skills/samber-golang-samber-ro/lockfile

Test it

Using "golang-samber-ro". Choose an operator for parsing JSON events while propagating parse failures.

Expected outcome:

Recommendation: use MapErr with a parsing function that returns a value and an error. Handle failures in the observer error callback.

Using "golang-samber-ro". Five subscribers must connect before a shared source begins emitting.

Expected outcome:

Use a Connectable observable instead of Share.
Register every subscriber before starting the connection.
Define cancellation and completion behavior for the shared source.

Using "golang-samber-ro". Review an infinite stream that has no timeout or unsubscribe path.

Expected outcome:

Risk: the subscription can outlive its owner and retain resources. Add context cancellation, a terminating operator, and an explicit cleanup test.

Security Audit

Safe

v1 • 9/23/2026 Open versioned report

All 77 static findings are contextual false positives caused by Markdown backticks, ordinary Go examples, scoped tool declarations, and documentation links. No prompt injection, covert execution, reconnaissance, credential access, or data-exfiltration intent was found.

Files scanned

1,468

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (50)

🌐 Network access (6)

SKILL.md:12 SKILL.md:29 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:179

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/samber-golang-samber-ro/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-samber-ro/security.svg)](https://skillstore.io/skills/samber-golang-samber-ro?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/samber-golang-samber-ro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-samber-ro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/samber-golang-samber-ro.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

samber. (2026). golang-samber-ro security audit report (audit version 1) [Author version 1.2.2]. Skillstore. https://skillstore.io/skills/samber-golang-samber-ro/audits/1

BibTeX citation

@techreport{samber-samber-golang-samber-ro-2026,
  author = {samber},
  title = {golang-samber-ro security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-samber-ro/audits/1},
  note = {Author version 1.2.2}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-samber-ro security audit report (audit version 1)"
version: "1.2.2"
type: report
authors:
  - name: "samber"
date-released: "2026-09-23"
url: "https://skillstore.io/skills/samber-golang-samber-ro/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-samber-ro:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Design an event pipeline

Choose operators, cancellation, and error handling for a service that processes asynchronous events.

Review reactive architecture

Assess hot and cold stream choices, subscription lifecycles, and resource cleanup before production deployment.

Learn samber/ro patterns

Translate channel-based workflows into typed observables while understanding subjects, composition, retries, and completion.

Try These Prompts

Create a basic pipeline

Build a samber/ro pipeline from [source]. Filter [condition], transform each value into [type], collect the results, and explain error handling.

Add cancellation and retries

Design a samber/ro pipeline for [operation]. Add context cancellation, a [duration] timeout, [count] bounded retries, and a final fallback.

Choose a sharing strategy

Compare cold, Share, ShareReplay, Connectable, and subjects for [event source]. Recommend one based on [subscriber behavior] and lifecycle requirements.

Audit a production pipeline

Review this samber/ro design: [description]. Find lifecycle, ordering, backpressure, concurrency, and error-propagation risks. Propose tests and a safer architecture.

Best Practices

Handle next, error, and completion events explicitly for every production subscription.
Prefer typed Pipe functions and bound infinite streams with cancellation or terminating operators.
Use Tap operators for logging and metrics without changing stream values.

Avoid

Do not use untyped Pipe when a typed Pipe function can preserve compile-time checks.
Do not share a cold source unless subscribers require one coordinated execution.
Do not leave infinite subscriptions without context cancellation, timeout, or explicit unsubscribe behavior.