ric-infra-safety

Manage RIC infrastructure services with non-destructive operations and namespace isolation.

Updated Jun 4, 2026

Search Tags:#security #redis #infrastructure #kafka #elasticsearch #timescale #ric

Ready to run

npx skills add https://github.com/lichong-a/ric-skills --skill ric-infra-safety

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ric-infra-safety
Source: https://github.com/lichong-a/ric-skills/tree/main/skills/ric-infra-safety
Command: npx skills add https://github.com/lichong-a/ric-skills --skill ric-infra-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for secure and compliant infrastructure management in RIC workflows, providing a safety net for operations involving Elasticsearch, Kafka, TimescaleDB/PostgreSQL, Redis, NATS, MinIO, and more.

Core Features & Use Cases

Shared Infrastructure: Offers pre-configured services for Elasticsearch, Kafka, TimescaleDB/PostgreSQL, Redis, NATS, and MinIO.
Safety Rules: Enforces non-destructive operations, ric namespace isolation, and environment-variable secrets usage.
Provisioning Policy: Prompts for shared infrastructure verification before creating new services to avoid duplication.
Implementation Patterns: Outlines best practices for infrastructure-related code, including configuration, health checks, and logging.

Quick Start

Use the ric-infra-safety skill to configure a new Elasticsearch index with the prefix 'ric-'.

Frequently Asked Questions about ric-infra-safety

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I secure Elasticsearch and Kafka infrastructure services in RIC workflows?▼

To secure Elasticsearch and Kafka infrastructure in RIC workflows, enforce non-destructive operations, apply ric namespace isolation, and manage credentials using environment-variable secrets to prevent unauthorized access or accidental data deletion.

What is the best way to avoid duplicating shared infrastructure like Redis and TimescaleDB?▼

The best way to avoid duplicating shared Redis and TimescaleDB infrastructure is to verify existing pre-configured services before provisioning new ones, ensuring shared infrastructure reuse and preventing resource overlap in RIC environments.

Can I use environment-variable secrets for MinIO and NATS configuration?▼

Yes, you can and should use environment-variable secrets for MinIO and NATS configuration to enforce safety rules, ensuring sensitive credentials remain isolated and compliant within the enforced ric namespace.

How do I configure a new Elasticsearch index with the ric namespace prefix?▼

To configure a new Elasticsearch index with the ric namespace prefix, apply the infrastructure safety rules that enforce non-destructive operations, ensuring the index is properly isolated and managed within the RIC workflow.

Why does provisioning new infrastructure require verifying shared services first?▼

Provisioning new infrastructure requires verifying shared services first to avoid duplication, enforce the provisioning policy, and ensure non-destructive operations are maintained across RIC workflows using existing pre-configured components.

What are the limitations of non-destructive operations in infrastructure safety?▼

Non-destructive operations in infrastructure safety limit the ability to execute destructive commands like dropping databases or deleting Kafka topics, enforcing namespace isolation and protecting shared RIC infrastructure from irreversible data loss.