agentsclimarketplace

Infrastructure

Skill ComeOnOliver/skillshub/skills/aiskillstore/marketplace/abdelstark/infrastructure

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install
npx -y skills add ComeOnOliver/skillshub --skill infrastructure

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Infrastructure as Code patterns for deploying Guts nodes using Terraform, Docker, and Kubernetes

SKILL.md

3.4 KB, 917 tokens by cl100k_base, as published. Nobody here has run it

Infrastructure Skill for Guts

You are managing infrastructure for a decentralized application with multiple node types.

Deployment Targets

  1. Local Development: Docker Compose
  2. Testing: Kubernetes (k3s/kind)
  3. Production: Cloud-agnostic Kubernetes + Terraform

Terraform Patterns

Module Structure

infra/
β”œβ”€β”€ terraform/
β”‚   β”œβ”€β”€ modules/
β”‚   β”‚   β”œβ”€β”€ network/
β”‚   β”‚   β”œβ”€β”€ compute/
β”‚   β”‚   └── storage/
β”‚   β”œβ”€β”€ environments/
β”‚   β”‚   β”œβ”€β”€ dev/
β”‚   β”‚   β”œβ”€β”€ staging/
β”‚   β”‚   └── prod/
β”‚   └── main.tf

Example Module

# modules/guts-node/main.tf
variable "node_count" {
  type        = number
  description = "Number of Guts nodes to deploy"
  default     = 3
}

variable "instance_type" {
  type        = string
  description = "Instance type for nodes"
  default     = "t3.medium"
}

resource "aws_instance" "guts_node" {
  count         = var.node_count
  ami           = data.aws_ami.ubuntu.id
  instance_type = var.instance_type

  tags = {
    Name        = "guts-node-${count.index}"
    Environment = var.environment
    Project     = "guts"
  }
}

Docker Best Practices

Multi-stage Builds

# Build stage
FROM rust:1.75-slim as builder
WORKDIR /app
COPY . .
RUN cargo build --release --bin guts-node

# Runtime stage
FROM debian:bookworm-slim
RUN apt-get update && apt-get install -y ca-certificates && rm -rf /var/lib/apt/lists/*
COPY --from=builder /app/target/release/guts-node /usr/local/bin/
EXPOSE 8080 9000
ENTRYPOINT ["guts-node"]

Docker Compose for Development

version: '3.8'

services:
  node1:
    build: .
    ports:
      - "8081:8080"
    environment:
      - GUTS_NODE_ID=node1
      - GUTS_PEERS=node2:9000,node3:9000
    volumes:
      - node1-data:/data

  node2:
    build: .
    ports:
      - "8082:8080"
    environment:
      - GUTS_NODE_ID=node2
      - GUTS_PEERS=node1:9000,node3:9000
    volumes:
      - node2-data:/data

  node3:
    build: .
    ports:
      - "8083:8080"
    environment:
      - GUTS_NODE_ID=node3
      - GUTS_PEERS=node1:9000,node2:9000
    volumes:
      - node3-data:/data

volumes:
  node1-data:
  node2-data:
  node3-data:

Kubernetes Patterns

StatefulSet for Nodes

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: guts-node
spec:
  serviceName: guts-nodes
  replicas: 3
  selector:
    matchLabels:
      app: guts-node
  template:
    metadata:
      labels:
        app: guts-node
    spec:
      containers:
      - name: guts-node
        image: guts/node:latest
        ports:
        - containerPort: 8080
          name: api
        - containerPort: 9000
          name: p2p
        volumeMounts:
        - name: data
          mountPath: /data
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes: ["ReadWriteOnce"]
      resources:
        requests:
          storage: 100Gi

Monitoring Stack

  • Metrics: Prometheus with custom Rust metrics
  • Logs: Loki + Grafana
  • Tracing: Jaeger with OpenTelemetry

Security Checklist

  • TLS certificates via cert-manager
  • Network policies for pod isolation
  • Secrets management with external-secrets
  • Regular security scanning with Trivy
  • RBAC for Kubernetes access

What ships with it

9.9 KB alongside SKILL.md

GitHub clipped this repository’s file list, so this is at least 1 file and may be more.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.