スキル golang-samber-ro

📦

golang-samber-ro

Name: golang-samber-ro
Author: samber

v1.2.2 コンテンツリビジョン r1 安全 ⚙️ 外部コマンド🌐 ネットワークアクセス

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.

対応: Codex Code(CC)

🥉 78 ブロンズ

Maintain this Skill? Claim it 🥉 78 ブロンズ

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

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.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/samber-golang-samber-ro.md 署名済み manifest GET /api/skills/samber-golang-samber-ro/manifest 署名済み lockfile GET /api/skills/samber-golang-samber-ro/lockfile

テストする

「golang-samber-ro」を使用しています。 Choose an operator for parsing JSON events while propagating parse failures.

期待される結果:

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

「golang-samber-ro」を使用しています。 Five subscribers must connect before a shared source begins emitting.

期待される結果:

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

「golang-samber-ro」を使用しています。 Review an infinite stream that has no timeout or unsubscribe path.

期待される結果:

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

セキュリティ監査

安全

v1 • 2026/9/23 バージョン別レポートを開く

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.

スキャンされたファイル

1,468

解析済み行数

レビュー項目

誤検知を無視

リスク要因

⚙️ 外部コマンド (50)

🌐 ネットワークアクセス (6)

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

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

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

Markdownバッジ

[![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バッジ

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

埋め込みカード

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

学術引用 (APA · BibTeX · CFF)

APA形式の引用

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形式の引用

@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 スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

100

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

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.

これらのプロンプトを試す

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.

ベストプラクティス

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.

回避

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.