Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-oriented Go reactive-streams skill whose sensitive-looking items are disclosed library features, not hidden behavior by the skill itself.
Install this if you want Go assistance for samber/ro reactive streams. Be aware that generated application code may use plugins for HTTP, filesystem watching, cron scheduling, signals, or process integration when you ask for those patterns, so review such code for appropriate paths, timeouts, retry limits, and operational permissions.
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
"Mentions that samber/ro is at v0.x (pre-v1.0.0)",
"Warns about potential breaking changes before v1",
"Mentions that the library follows SemVer",
"Does NOT present the library as fully stable/production-ready without caveats"
]
}
]
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
| `Catch[T](fn func(error) Observable[T])` | Catch error, switch to recovery observable |
| `OnErrorReturn[T](value T)` | Replace error with fallback value |
| `OnErrorResumeNextWith[T](obs ...Observable[T])` | Continue with fallback observables on error |
| `Retry[T]()` | Retry indefinitely on error |
| `RetryWithConfig[T](cfg RetryConfig)` | Retry with max attempts, delay, backoff |
| `ThrowIfEmpty[T](fn func() error)` | Error if stream completes empty |
The manifest frames the skill as guidance for using the samber/ro reactive programming library and its stream-processing features. Advertising a plugins/proc capability for process execution introduces a system-command capability that is not an obvious requirement of adopting a reactive streams library and expands into a materially different operational domain.
No suspicious patterns detected.