bolivian-peru

Generate a concise daily infrastructure briefing. Covers: service health, resource usage, security events, overnight incidents, and cost tracking. Designed for Telegram/chat delivery.

Multi-perspective risk analysis using structured persona debate before deploying changes

Build software via spec-driven development (github/spec-kit). Whenever the user asks for a feature larger than a one-line tweak, scaffold a spec-kit project, capture WHAT + WHY, declare tech stack, break into tasks, then iterate the implementation until tests pass.

Large-scale social simulation with 50-200 demographically diverse AI personas debating on a simulated Twitter/Reddit board to predict outcomes

Deploy and manage AI agent workloads with GPU checks, API key management, and health monitoring

Detect configuration drift — manual changes that exist outside NixOS management. Offer to bring imperative changes into declarative config.

Deploy and manage user applications as managed systemd services

Predict resource exhaustion (disk, memory, swap) using trend analysis. Proactively alert and propose NixOS config fixes before things break.

Deeply analyze ANY software project's real source/config, then build a live, animated WebGL "system map" (an orbiting 3D force-graph of the whole ecosystem) PLUS a static PlantUML "analysed" architecture diagram — both driven by ONE code-verified data file, with real-time telemetry pulled from the project's own public endpoints. Use this skill whenever the user wants a system map, an architecture/ecosystem diagram, an interactive dependency or service graph, "show me / visualize the whole system", a force-directed graph of services, a live status/telemetry map, or a PlantUML component diagram generated from real code. Output is one self-contained static HTML page + a generated SVG, deployable to any static host, with no backend of its own. NEVER invents data — every node, edge, and number is verified against the real codebase or a live endpoint. Trigger on: "system map", "architecture diagram", "ecosystem graph", "WebGL graph", "force graph of our services", "visualize the whole platform/stack", "live infra m

Build a production-grade streaming agentic chat front-end: an SSE-streamed conversation with a live tool-call timeline, a collapsible "thinking" panel, typing/status animations, an auto-growing input, stop/retry/abort, and graceful failure. Framework-light (React + fetch + the Streams API + Tailwind + lucide icons — no chat library, no SSE library) so it ports cleanly into any Next.js/React product. Use when building ANY chat UI for an LLM/agent backend: a support assistant, a research agent, an admin copilot, a data-Q&A surface. Triggers on: "chat interface", "streaming assistant UI", "agent front-end", "tool-call timeline", "SSE chat", "real-time AI chat", "build a ChatGPT-style UI".

Embed a Coronium AI chat agent into any web app — branded for the integrator, authed via wallet-bound API keys, streams over SSE. The chat agent has tool access to the full Coronium 7-verb API (proxy_get / rotate / replace / release / balance / tariffs / deposit) and runs spend-capped. Use this skill whenever the user wants to add a "Talk to your proxies" / "AI assistant" / "chat support" / "concierge" / "buy a proxy by chatting" experience to their site, dashboard, reseller portal, or marketplace — even if they don't explicitly say "Coronium chat."

Embed Coronium agent-native signup directly into any web frontend — wallet generation, voucher redemption, SIWE signing, and API key issuance, all running browser-side. Use this skill whenever the user wants to add a "sign up" / "create account" / "connect wallet" / "onboard users to Coronium" / "embed the Coronium CLI" / "let users sign up on our site" flow into a website, dashboard, reseller portal, marketplace integration, or landing page — even if they don't explicitly say "Coronium" or "SIWE."

Trade, create, and manage Solana prediction markets on Baozi.bet — autonomous betting, market creation, affiliate earnings, and portfolio tracking

Auto-create Baozi Lab prediction markets from trending topics

Manage Proxies.sx mobile/residential proxies, mint x402 USDC sessions, rotate IPs, and consume marketplace data services from any MCP-compatible AI agent (Claude Desktop, Cursor, Windsurf, Continue, Cline, Claude Code). Trigger this skill the moment the user wants to install / configure / use the Proxies.sx MCP server, integrate proxies into a Claude Desktop or Cursor workflow, mint a proxy without an API key (x402 autonomous mode), build an AI scraping agent that buys its own bandwidth, troubleshoot MCP tool errors, or pick between API-key mode and x402 wallet mode. Use it whenever the user mentions "Proxies.sx MCP", "@proxies-sx/mcp-server", "MCP proxy tools", "Claude Desktop proxy", "x402 mcp", "agent proxy purchase", "proxy MCP", or anything implying machine-driven proxy management — even if they don't explicitly ask for "this skill".