iii-hq
- 61 skills
- 0 followers
- 9 hours ago last updated
- ▌ Vercel React Best Practices · iii-hq bundleReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
- ▌ Vite · iii-hq bundleVite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
- ▌ UI UX Pro Max · iii-hq bundleUI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
- ▌ Broken Worker · iii-hq bundleA worker shipped with intentional rule violations for testing the validator.
- ▌
- ▌
- ▌ Iii Doc Authoring · iii-hq bundleSkill bundle index for authoring Mintlify-shaped docs that iii-skill-check validates.
- ▌ Iii Skill Authoring · iii-hq bundleSkill bundle index for authoring the partials iii-skill-check renders into a worker README and a single skill.md (leaves inlined as HOWTOs).
- ▌ Fp · iii-hqMove and reshape big values between iii functions without routing them through the model — fp::pipe worker-side pipelines plus pure lodash-style transforms (get, pick, omit, take, drop, map, filter, split, join, uniq).
- ▌ Pi · iii-hqRun pi coding-agent turns over the iii bus — headless with `pi::run`, or as a terminal page on the console a person types into — with verbatim event streaming, session resume, and live steering.
- ▌ PDF · iii-hqRead PDFs locally without OCR or an API key — classify text-based versus scanned in tens of milliseconds and name the pages that still need OCR, convert to markdown with headings, lists and tables intact, and pull positioned text or the exact characters inside a box on a page.
- ▌ Skills · iii-hq> **Callable id:** `web::fetch` — pass to `agent_trigger { function: "web::fetch" }` (NOT the `iii://...` skill path; that's docs, not a function id). Use this **instead of** `shell::exec` with `curl`/`wget` for any HTTP request: you get a parsed `{ ok, status, headers, body }` envelope, enforced size/timeout caps, and server-side SSRF protection a shell `curl` doesn't have.
- ▌ A2ui · iii-hqGenerate safe interactive A2UI surfaces when a Harness response is clearer as a dashboard, form, summary, comparison, or decision interface than prose.
- ▌ Cron · iii-hqSchedule any registered function on a 6- or 7-field cron expression with the standalone cron worker. Its whole surface is the `cron` trigger type.
- ▌ Grok · iii-hqRun headless xAI Grok CLI turns over the iii bus — shell, file edits, and tools against any host directory — with verbatim event streaming and session resume.
- ▌ HTTP · iii-hqExpose registered functions as HTTP endpoints with the standalone http worker. Its whole surface is the `http` trigger type.
- ▌ Codex · iii-hqRun headless OpenAI Codex turns over the iii bus — sandboxed shell, file edits, and web search against any host directory — with verbatim event streaming, thread resume, and full SDK option pass-through.
- ▌ Devin · iii-hqDrive Devin over the iii bus. Run the local Devin CLI agent (SWE-1.6) with the iii runtime context so it discovers and operates your workers, or start and steer autonomous Devin cloud sessions through the REST API, with a passthrough to any Devin v1/v3 endpoint.
- ▌ Email · iii-hqSend and read email from the iii engine — SMTP send, IMAP read, and real-time `IDLE` push as a subscribable trigger type. Credentials live in `harness/auth-credentials`; this worker fetches them on every connect.
- ▌ Queue · iii-hqDurable topic queues for iii: subscribe functions to topics, publish work asynchronously, retry failed deliveries with backoff, and inspect/redrive dead-lettered messages.
- ▌ Shell · iii-hqRun Unix commands and structured filesystem ops from the iii engine: exec, background jobs, and a structured fs (ls/stat/mkdir/rm/chmod/mv/grep/sed/ read/write, jailed only if fs.host_roots is configured), all forwardable into a sandbox microVM.
- ▌ Slack · iii-hqDrive Slack from iii — expose the Slack Web API as slack::* functions (post messages, manage channels, reactions, files, users, views, search, assistant threads), configurable from the console. Anything the Slack API can do, this worker can do.
- ▌ State · iii-hqShared, adapter-backed key/value store addressed by scope and key, with a reactive `state` trigger so other functions can run on every create, update, or delete without polling.
- ▌ Voice · iii-hqSpeech in and out for iii — transcribe audio files to timestamped text, run live dictation sessions fed with microphone audio, and read text aloud.
- ▌ Bridge · iii-hqConnect this engine to another iii engine over a long-lived WebSocket so functions call across the boundary. Wire stable ids with `forward:`/`expose:`; `bridge.invoke` is the ad-hoc escape hatch.
- ▌ Canvas · iii-hqCreate and edit diagrams as code — store mermaid text or excalidraw scenes under stable ids the console renders live, fetch the per-family mermaid syntax primer, and validate generated source before storing it.
- ▌ Cursor · iii-hqUse Cursor through iii as a login-backed text provider or as a direct coding agent with durable local and cloud sessions.
- ▌ Editor · iii-hqA code workspace shared with the user — open buffers, a file tree, diffs, fuzzy find, and saves that refuse to clobber. Backed by the shell worker for files and the state worker for the workspace record.
- ▌ Github · iii-hqOperate GitHub through the gh CLI — typed github::* functions for pull requests, issues, repos, Actions runs/workflows, releases, and search, plus github::exec / github::api escape hatches for everything else.
- ▌ Hermes · iii-hqRun headless Hermes agent turns over the iii bus, deliver messages to 27+ chat platforms, and react to inbound platform/webhook events — with the agent carrying the live iii runtime context.
- ▌ Kanban · iii-hqPlan, launch, inspect, review, and land multiple Harness or external-worker tasks as one repository-aware run with dependencies and isolated worktrees.
- ▌ Memory · iii-hqDurable cross-session memory: named banks of always-injected markdown rules and auto-extracted memories with hybrid recall. Reach for it when the user asks you to remember, forget, or inspect what is remembered.
- ▌ Pubsub · iii-hqFire-and-forget topic pub/sub: broadcast an event with `publish` and every matching `subscribe` trigger receives it. Use for real-time notifications where missed events are acceptable.
- ▌ Vscode · iii-hqRun the VS Code Server for a workspace directory and open the Workbench in the Console; use it when a person needs a full editor next to the chat, not when the agent itself needs to read or edit files.
- ▌ Browser · iii-hqInteractive Chromium sessions for reading and driving real web pages: open a URL, read the page as text, click and type, and read the page's own console and network history. Also scrapes: HTTP and browser fetching, screenshots, persistent sessions, crawling, and CSS/XPath/regex parsing of HTML you already have. Reach for it when a task involves a running web app, especially "why is this page broken", or when pulling data off the web.
- ▌ Console · iii-hq bundleThe iii web console — chat, trace explorer, worker catalog, and the runtime host every worker injects its own pages, renderers, and configuration forms into. Read it before building or changing any console UI, and when an agent must drive the operator's workspace (open or close a screen, propose a working directory).
- ▌ Harness · iii-hq bundleThe durable agent turn loop — kick off a turn with `harness::send`, render it from session-manager transcript events, react to `harness::turn-completed`, with deny-by-default tool dispatch and synchronous hook extension points for policy siblings.
- ▌ Computer · iii-hqDrive a full desktop computer over the iii bus: start a session, see the screen as an image, and click, type, and scroll by coordinate. Reach for it when a task needs to operate a real GUI app or whole desktop, not just a web page.
- ▌ Database · iii-hqRun SQL against PostgreSQL, MySQL, or SQLite from the iii engine — reads, writes, transactions, and prepared statements over managed connection pools.
- ▌ Document · iii-hqRead Word, PowerPoint, Excel, OpenDocument, RTF, EPUB and CSV files locally with no API key — detect the format from the bytes, convert to markdown with headings, lists and tables intact, and pull out the images markdown drops.
- ▌ Opencode · iii-hqRun headless OpenCode turns over the iii bus — file edits, shell, and search against any host directory — with verbatim JSON event streaming, session resume, and inline token usage and cost.
- ▌
- ▌ Worktree · iii-hqMint isolated git worktrees for parallel agent work, track ownership in a cross-agent registry, and land finished branches back onto a target with a queued rebase, test gate, and atomic fast-forward merge.
- ▌ Scrapling · iii-hqScrape the web over the iii bus with Scrapling — fast HTTP fetch with TLS impersonation, a Camoufox anti-bot browser (Cloudflare bypass), full Playwright rendering, screenshots, and CSS/XPath/regex/adaptive extraction.
- ▌ Tailscale · iii-hqOperate this host's Tailscale node from iii: connectivity and peers, routes and exit nodes, preferences, Taildrop file transfer, HTTPS certificates, publishing local services or the Console to the tailnet (Serve) or the internet (Funnel), accounts, tailnet lock, updates. Use it for anything a person would otherwise do with the `tailscale` CLI or the Tailscale app.
- ▌ Compose UI · iii-hqExplain why a compose container failed or what the supervisor is doing by reading its log tail; use it when a person asks about container state, a worker that will not come up, or wants the Compose page open beside the chat.
- ▌ Opengantry · iii-hqOpenGantry iii worker. Use when an iii project needs deterministic promote gates: gantry::verify runs the repo gate command, gantry::middleware blocks promote-class calls until a verdict token matches the current mission.
- ▌ Claude Code · iii-hqRun headless Claude Code turns over the iii bus — file edits, shell, and web against any host directory — with verbatim message streaming, session resume, and full Agent SDK option pass-through. Also serves Claude Code as an interactive terminal page on the console.
- ▌ Telegram Bot · iii-hqBridge a harness agent onto Telegram — turn inbound chat messages into `harness::send` turns and stream assistant output, model pickers, and inline tool-call approvals back into the chat.
- ▌ Iii Directory · iii-hq bundleDiscovery entry point for the engine — search the live function catalog, read the skills, system prompts, and agent profiles that installed workers ship off local disk, browse the public iii workers registry over HTTP, and install new worker bundles. Reach for it first to find out which workers exist and how to call them.
- ▌
- ▌ Iii Worker Manager · iii-hqWebSocket listener that SDK workers connect to. Use to expose the engine to trusted (internal) and untrusted (RBAC-protected) workers, gate function and trigger registration, and audit or transform every invocation through a middleware function. Mounts channel WebSocket endpoints on every listener.
- ▌ Iii · iii-hqHow iii works and the iii-sdk surface for authoring workers, triggers, and functions. Teaches the ordered way to gain a capability before writing code — (1) check functions already registered in the engine, (2) search the public registry via iii-directory, (3) build a worker. Single self-contained skill — meant for system-prompt injection; do not re-fetch.
- ▌ Configuration · iii-hqSchema-validated, reactive registry for named configuration entries — the runtime configuration surface used by engine and Compose workers.
- ▌ Iii Observability · iii-hqOpenTelemetry-backed tracing, structured logs, metrics with rollups, alerts, sampling, and baggage for the engine — emit and query telemetry through `engine::*` functions and react to logs with a `log` trigger.
- ▌ Iii Sandbox · iii-hqEphemeral microVM sandboxes for running untrusted or agent-generated code in isolation — a one-call run path, a create/exec/stop lifecycle, and a set of filesystem operations.
- ▌ Presentation · iii-hq bundleTurn a tech-spec directory into an interactive, marketing-grade web presentation — built so engineers understand the design, the reader is convinced of the why, and the result is shareable in public. Use when someone wants a spec turned into a deck.
- ▌ Iii Engine Config · iii-hqConfigure a managed iii engine through worker-compose.yaml or a directly supervised engine through config.yaml. Use for engine ports, RBAC listeners, streams, sandboxes, and configuration storage.
- ▌ Iii Core Primitives · iii-hqUse when registering iii functions, binding triggers, selecting sync/void/enqueue invocation, creating workers, inspecting the live worker registry, installing registry workers, authoring custom triggers, moving channel data, or adapting external HTTP functions across TypeScript, Python, and Rust.
- ▌ Iii Getting Started · iii-hqInstall the iii engine, set up your first worker, and get a working backend running. Use when a user wants to start a new iii project, install the SDK, or needs help with initial setup and configuration.
- ▌ Iii Stream · iii-hqDurable real-time streams with a CRUD function surface plus reactive triggers that fire on item changes and WebSocket subscriber lifecycle — reach for it to build live backends without polling.