infrastructure
Kubernetes and infrastructure operations. Use for cluster management, ArgoCD, Tailscale, deployments.
pinned to #8376b92updated last month
Ask your AI client: “install agents/infrastructure”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install agents/infrastructuremetahub onboarded this repo on the author's behalf.
If you own github.com/xxczaki/wicek on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1
Last commit
last month
Latest release
published
- #ai
- #ai-agent
- #bash
- #claude
- #claude-agent
- #claude-code
- #claude-code-agent
- #edit
- #glob
- #grep
- #openclaw
- #openclaw-alternative
- #personal-ai-assistant
- #personal-assistant
- #read
- #websearch
- #write
About this agent
Pulled from agent.json + the entry file at publish time.
“You manage a single-node K3s cluster on Raspberry Pi 4. Stack: Cilium CNI, Tailscale ingress/egress, ArgoCD GitOps, Sealed Secrets, Longhorn storage. Grafana Cloud for monitoring (Prometheus, Loki, Tempo). When making infrastructure changes: - Always use the GitOps workflow (pus”
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.8376b92· last month
Behavioral checks haven't run yet: the sandbox couldn't execute this artifact (it may need credentials we don't provide, or an unsupported build). An environment limit, not a verdict.
Structural
7 passed1 warningVersion is semverwarn
No version declared.
Add a "version" field to infrastructure.md.
Repository is reachable
https://github.com/xxczaki/wicek @ 8376b92 — ★ 1 · TypeScript · MIT · last push today
Manifest detected
kind=agent slug=infrastructure · path=.claude/agents/infrastructure.md · source=.claude/agents/infrastructure.md
Slug is URL-safe
"infrastructure" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for agent/infrastructure
Version is semver
0.1.0
Manifest present and parseable
Manifest found at infrastructure.md.
Name declared and well-formed
Name "infrastructure" is well-formed.
Release history
1- releasecurrent8376b92warnlast month
Contents
Wicek
Task-focused AI assistant running as a Discord bot, powered by Claude Code
A minimal Node.js application that drives the Claude Agent SDK and exposes it through Discord. Built to replace a bloated third-party Kubernetes operator (openclaw-rocks) with something lean and maintainable.
[!WARNING] This project is experimental and should not be used directly as-is.
Motivation
OpenClaw is a capable AI agent platform with a broad feature set – multiple messaging channels, vector memory, browser automation, self-configuration, and more. For a single-user setup on a Raspberry Pi where only Discord and a handful of tools are needed, most of that goes unused. Wicek replaces it with ~500 lines of TypeScript, a single Deployment, and a Helm chart.
What it does
- Discord integration – DMs, @mentions, and threaded conversations via discord.js
- Claude Agent SDK – runs
query()per request on a Pro/Max subscription (OAuth token, no API key), streaming results back to Discord with thinking (blockquotes), tool use, and text - Browser automation – headless Chrome sidecar with Chrome DevTools MCP, screenshots auto-attached to Discord
- Cron jobs – GitOps-defined scheduled prompts (e.g., daily ETF updates)
- Custom subagents –
.claude/agents/for ETF analysis, infrastructure ops, Home Assistant - File handling – receives Discord attachments, sends back generated files and screenshots
- Self-update – knows how to push changes through the GitOps pipeline (git -> ArgoCD)
- Long-term memory – Claude Code's native auto-memory on persistent storage
Deployment
Runs on a single-node K3s cluster (Raspberry Pi 4). See xxczaki/homelab for the full cluster setup and xxczaki/charts for the Helm chart.
AI disclosure
This project contains code generated by Large Language Models (LLMs), under human supervision and proofreading.
License
MIT
Reviews
No reviews yet. Be the first.
Related
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or enable design possibilities.
producer
The Producer manages all production concerns: sprint planning, milestone tracking, risk management, scope negotiation, and cross-department coordination. This is the primary coordination agent. Use this agent when work needs to be planned, tracked, prioritized, or when multiple departments need to synchronize.
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.
mh install agents/infrastructure