Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

iggy

Sterne31

Forks3

Aktualisiert2. Juni 2026 um 19:57

Apache Iggy Incubating Rust-native message streaming platform expertise. Use when the user mentions Iggy, event streaming, Kafka/NATS alternatives, Iggy CLI or SDKs, Python apache-iggy, Docker apache/iggy images, Iggy MCP, QUIC/TCP/HTTP/WebSocket transports, streams, topics, partitions, retention, or consumer groups.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

gordonmurray

gordonmurray/data-engineering-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	iggy
description	Apache Iggy Incubating Rust-native message streaming platform expertise. Use when the user mentions Iggy, event streaming, Kafka/NATS alternatives, Iggy CLI or SDKs, Python apache-iggy, Docker apache/iggy images, Iggy MCP, QUIC/TCP/HTTP/WebSocket transports, streams, topics, partitions, retention, or consumer groups.

Apache Iggy Streaming Expert

Use this skill for Iggy deployment, stream/topic design, producer and consumer patterns, Docker Compose, SDK usage, and MCP-oriented AI workflows.

Current Facts

Current server release: 0.8.0-incubating, released April 22, 2026.
Previous release: 0.7.0-incubating, released February 24, 2026.
Status: Apache Incubating since February 4, 2025. Incubating releases are not yet official ASF products.
Images: apache/iggy, apache/iggy-web-ui, apache/iggy-mcp, apache/iggy-connect.
Ports: HTTP 3000, QUIC UDP 8080, TCP 8090, WebSocket 8092.
0.8 highlights: complete wire protocol rewrite, persistent WAL journal, shard/VSR clustering groundwork, iggy-server-ng, A2A protocol support, user header encryption breaking change, Java async pooling, Go TCP/TLS, revived C++ SDK, connector hot reload, Web UI 0.3.0, and security hardening.

How To Use

Determine deployment mode: local binary, Docker, Compose, Kubernetes/Helm, or SDK-only client work.
Determine transport: TCP for throughput, QUIC for latency, HTTP for REST/admin, WebSocket for browser-compatible clients.
For Python, verify the installed apache-iggy package API before writing detailed code; async-only API details changed quickly across 0.7/0.8.

Deployment Rules

Set IGGY_HTTP_ADDRESS=0.0.0.0:3000 and IGGY_TCP_ADDRESS=0.0.0.0:8090 in containers when exposing services outside the container.
Set IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD explicitly for first startup.
Persist /local_data.
Keep io_uring and thread-affinity requirements in mind; Compose examples often need SYS_NICE, seccomp:unconfined, and memlock ulimits.
Use fixed version tags in production rather than latest.

Update Checklist

Recheck Iggy downloads for latest incubating source release.
Recheck SDK package versions separately; server, Rust, Python, Java, Go, C#, and Web UI versions may differ.

Mehr aus diesem Repository

gleiches Repository

docker-compose

gordonmurray/data-engineering-skills

Docker Compose V2 and Compose Specification expertise for writing correct compose.yaml and docker-compose.yml files. Use when the user mentions Docker Compose, compose.yaml, docker-compose.yml, docker compose CLI, multi-container apps, profiles, healthchecks, depends_on, networks, volumes, secrets, build contexts, or avoiding deprecated V1 patterns.

2026-06-0231

flink

gordonmurray/data-engineering-skills

Apache Flink stream processing expertise for stateful computations over bounded and unbounded streams. Use when the user mentions Flink, Flink SQL, Table API, DataStream API, CDC, Kafka-to-Flink pipelines, checkpoints, savepoints, watermarks, windows, Flink Kubernetes Operator, or Flink integrations with Iceberg, Paimon, or Fluss.

2026-06-0231

fluss

gordonmurray/data-engineering-skills

Apache Fluss Incubating streaming storage expertise for real-time analytics, streamhouse and lakehouse architectures. Use when the user mentions Fluss, streaming storage, columnar streams, sub-second ingestion, tiered storage, Flink Delta Join, Paimon/Iceberg/Lance tiering, Spark access to streams, or Fluss table design.

2026-06-0231

iceberg

gordonmurray/data-engineering-skills

Apache Iceberg table format expertise for data lakehouses. Use when the user mentions Iceberg, lakehouse, table format v2 or v3, deletion vectors, partition evolution, time travel, snapshot isolation, Polaris, Nessie, REST catalogs, metadata.json, manifest lists, snapshots, Spark, Flink, Trino, Athena, Snowflake, or table maintenance.

2026-06-0231

lance

gordonmurray/data-engineering-skills

Lance columnar data format and LanceDB expertise for ML/AI workloads, vector search, embeddings, multimodal datasets, and .lance files. Use when the user mentions Lance, LanceDB, pylance, vector indexes, ANN search, IVF_PQ, IVF_HNSW_FLAT, HNSW, full-text search, dataset versioning, or migrating ML data from Parquet.

2026-06-0231

paimon

gordonmurray/data-engineering-skills

Apache Paimon streaming lake format expertise for real-time ingestion and lakehouse architectures. Use when the user mentions Paimon, streaming lakehouse, primary-key tables, changelog, Flink CDC into a lake, Paimon Materialized Tables, PyPaimon, deletion vectors, lookup joins, buckets, compaction, or Spark/Flink Paimon tables.

2026-06-0231

name	iggy
description	Apache Iggy Incubating Rust-native message streaming platform expertise. Use when the user mentions Iggy, event streaming, Kafka/NATS alternatives, Iggy CLI or SDKs, Python apache-iggy, Docker apache/iggy images, Iggy MCP, QUIC/TCP/HTTP/WebSocket transports, streams, topics, partitions, retention, or consumer groups.

Apache Iggy Streaming Expert

Use this skill for Iggy deployment, stream/topic design, producer and consumer patterns, Docker Compose, SDK usage, and MCP-oriented AI workflows.

Current Facts

Current server release: 0.8.0-incubating, released April 22, 2026.
Previous release: 0.7.0-incubating, released February 24, 2026.
Status: Apache Incubating since February 4, 2025. Incubating releases are not yet official ASF products.
Images: apache/iggy, apache/iggy-web-ui, apache/iggy-mcp, apache/iggy-connect.
Ports: HTTP 3000, QUIC UDP 8080, TCP 8090, WebSocket 8092.
0.8 highlights: complete wire protocol rewrite, persistent WAL journal, shard/VSR clustering groundwork, iggy-server-ng, A2A protocol support, user header encryption breaking change, Java async pooling, Go TCP/TLS, revived C++ SDK, connector hot reload, Web UI 0.3.0, and security hardening.

How To Use

Determine deployment mode: local binary, Docker, Compose, Kubernetes/Helm, or SDK-only client work.
Determine transport: TCP for throughput, QUIC for latency, HTTP for REST/admin, WebSocket for browser-compatible clients.
For Python, verify the installed apache-iggy package API before writing detailed code; async-only API details changed quickly across 0.7/0.8.

Deployment Rules

Set IGGY_HTTP_ADDRESS=0.0.0.0:3000 and IGGY_TCP_ADDRESS=0.0.0.0:8090 in containers when exposing services outside the container.
Set IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD explicitly for first startup.
Persist /local_data.
Keep io_uring and thread-affinity requirements in mind; Compose examples often need SYS_NICE, seccomp:unconfined, and memlock ulimits.
Use fixed version tags in production rather than latest.

Update Checklist

Recheck Iggy downloads for latest incubating source release.
Recheck SDK package versions separately; server, Rust, Python, Java, Go, C#, and Web UI versions may differ.