Agent
A sub-agent is another agent that your agent hands one self-contained task to, waits for, and gets an answer back from. Use it when a piece of work wants a different role — research, code review, image generation — or when the intermediate steps would flood the main conversation.
Agent
Wire a project's ticket board to another system, in both directions.
Skill Claude CodeCodex
Use when the user asks how wick agents work — sessions, projects, presets, providers, channels (Slack/Telegram/web), the pool and its queue, scheduled messages, or where agent state lives on disk. Covers the mental model behind sessions and projects, how to point an agent at a folder, and how to reach the same agent…
Skill Claude CodeCodex
Use when the user asks to look something up or act on an external system through wick — check a ticket, query a database, read logs, search Slack, call an API — or asks which connectors are available. Covers the list → drill → schema → execute discovery cycle over MCP, session workspaces for throwaway credentials, and…
Skill Claude CodeCodex
Use when the user wants wick to reach an API it has no connector for yet — "buatin connector untuk X", "add a connector for this API", "wrap this cURL", "register our internal MCP server", "add an operation to that connector I made", or asks why a connector they built shows nothing. Covers the custom-connector…
Skill Claude CodeCodex
Use when asked anything about wick itself — what it is, what it can do, whether an update is available, what changed in a release, how a feature works, or how to configure something. Points to the live documentation site and release feed so answers come from current sources, never from memory.
Skill Claude CodeCodex
Use when the session's prompt says notes are waiting, when picking up work someone (or some earlier session) already started, when you learn something a later session would otherwise have to rediscover, or when the user mentions notes, handover, or "what did we find last time". Notes work on a plain session too — no…
Skill Claude CodeCodex
Use when the user asks about installing, updating, removing, disabling, or building a wick plugin — a connector shipped as a standalone binary that wick runs over gRPC. Covers the plugin CLI, the marketplace catalog, install verification and signing, when to choose a plugin over an in-tree module or a custom…
Skill Claude CodeCodex
Use when the user asks about agent memory or CPU limits, an agent being killed or OOM, the Resources page, usage history, disk space, why a spawn is queued, or how to cap what an agent may consume. Covers the three guard modes and what each actually does, which platform enforces what, how to read the four separate…
Skill Claude CodeCodex
Use BEFORE writing any HTML artifact, widget, diagram, chart, image gallery, or dashboard into a wick chat reply. Covers which fence to use (html vs htmlfile vs svg vs mermaid vs imagecard), the theme bridge variables an artifact must use, why fetch() is blocked inside an artifact and what to use instead…
Skill Claude CodeCodex
Use when finishing a turn nobody needs to read — a monitor or poll that found nothing new, a scheduled run mid-sequence, bookkeeping between steps. Covers the exact [silent] marker that keeps a reply out of Slack/Telegram and push notifications, where it must sit, what breaks it, and when to reply normally instead.
Skill Claude CodeCodex
Use BEFORE writing any reply that will be delivered to Slack — Slack uses mrkdwn, not markdown, and wick sends your text through unconverted. Covers the syntax that differs (bold, italic, strike, links, headings, tables), which rich fences degrade badly, how to write one message that reads well on both Slack and the…
Skill Claude CodeCodex
Use when the session's prompt names a ticket (T-XXXX), when the user talks about tickets, the board, statuses, assignees, or when a conversation has gone off the rails and the work should continue in a fresh session on the same ticket. Covers the ticket model (one ticket, many sessions), keeping status honest, and…
Skill Claude CodeCodex
Use when the user asks to build, edit, debug, or run a wick workflow — a multi-step automation stored as a graph of typed nodes with triggers (cron, channel, webhook, manual). Covers when a workflow is the right tool versus an agent or a job, the node catalog, trigger types, the render context, and how to author one…