Menu
Use this when setting up event-driven automation in SLICC — webhooks, cron tasks, or filesystem watchers that route events to scoops. Covers `webhook`, `crontask`, and `fswatch` shell commands. Read this BEFORE wiring up anything that should fire on a schedule, an HTTP call, or a VFS change.
| name | automation |
| description | Use this when setting up event-driven automation in SLICC — webhooks, cron tasks, or filesystem watchers that route events to scoops. Covers `webhook`, `crontask`, and `fswatch` shell commands. Read this BEFORE wiring up anything that should fire on a schedule, an HTTP call, or a VFS change. |
| allowed-tools | bash |
SLICC's automation primitives turn external or VFS-internal events into licks — messages routed to a scoop (or to the cone if no scoop is named). Three shell commands set them up:
| Command | Trigger | Use case |
|---|---|---|
webhook | Inbound HTTP request | Receive callbacks from external services |
crontask | Cron schedule | Recurring background work |
fswatch | VFS file create / modify / delete | React to authored content changes |
All three deliver events as licks. If --scoop <name> is set, the lick goes to that scoop; otherwise it goes to the cone.
webhookReceive HTTP callbacks. The event lick carries the request method, path, headers, and body. Each webhook create allocates a path; the URL is printed on creation.
webhook create --scoop pr-watcher --name gh-prs
webhook create --scoop bot --name slack --filter 'event.body.includes("deploy")'
webhook list
webhook delete wh-1
Flags:
--scoop <name> — route the event to a specific scoop. Omit to route to the cone.--name <label> — human-friendly label shown in webhook list.--filter <js> — JavaScript expression evaluated per request; falsy result drops the event before it reaches the agent.crontaskRun a scoop on a cron schedule. Standard 5-field cron (minute hour day month weekday).
crontask create --cron "0 * * * *" --scoop hourly-summary --name hourly
crontask list
crontask delete ct-1 # `kill` is an alias for `delete`
Flags:
--cron <expr> — required; 5-field cron expression.--scoop <name> — target scoop. Omit to route to the cone.--name <label> — human-friendly label.--filter <js> — JavaScript expression evaluated each tick; falsy result skips that fire.fswatchWatch a VFS path; deliver events as licks when files matching the pattern are created, modified, or deleted.
# Route .md changes under /workspace to a scoop.
fswatch create --path /workspace --pattern "*.md" --scoop doc-watcher --name md-changes
# Untargeted: route to the cone.
fswatch create --path /workspace/src --pattern "*.ts"
fswatch list
fswatch delete fsw-1
Events include the change type (create, modify, delete) and the file path.
crontask to do work the cone could do reactively. Cron is for genuinely recurring jobs (digests, refreshes); reactive work belongs on fswatch or webhook.... list and ... delete to clean up.Use this when the user wants to write a new skill, edit an existing one, or understand SLICC's skill system. Covers SKILL.md frontmatter (name, description, allowed-tools), how to write a description that triggers reliably, native `/workspace/skills/` vs compatibility `.agents/` / `.claude/skills/` discovery, and when to ship companion files like `.jsh` scripts or `.bsh` browser hooks.
Use this when the user wants a persistent UI panel — a dashboard, form, editor, report, or visualization that lives alongside the chat. Sprinkles are `.shtml` files under `/shared/sprinkles/` rendered in the side rail or as a full-screen tab. For ephemeral inline widgets, use dips instead. Covers creation, modification, layout constraints, the cone-to-scoop orchestration rules, the `slicc.*` bridge API, and `sprinkle chat` for blocking inline prompts.
Use this when a cherry target is connected — a third-party host web page that has embedded a SLICC follower via the @ai-ecoverse/cherry SDK and lent itself to you (a cloud-cone leader) as a driveable, capability-limited browser target. Covers what you can and cannot do with a cherry target (navigate / screenshot / open URL, NEVER raw network), the `cherry-emit` command for pushing host-page events, and the `[cherry]` licks you receive when the host page reports an event.
Use this skill when the user says things like `handoff to slicc`, `move this to slicc`, `move to the browser`, `test in the browser`, `handoff to browser`, `install this skill in slicc`, `upskill slicc with this repo`, `add this skill to slicc`, or otherwise asks you to continue the work in the SLICC browser agent or install a skill into it.
Use this whenever a response could benefit from richer visualization, guided interaction, or a touch of fun — pickers, calculators, sliders, mini explorers, charts, animated demos, choose-your-own-adventure prompts, anything that lands better as a hydrating widget than as plain prose. Dips are ephemeral `shtml` code blocks rendered inline in chat (no state persistence, lick-only). Reach for them generously: every interactive moment the user gets is a moment they don't have to type a clarifying message. For persistent dashboards, editors, or multi-page apps use sprinkles instead.
Search X (formerly Twitter) for real-time posts, sentiment, and citations via xAI's `x_search` server-side tool. Works with any model — the search call runs through your xAI Grok OAuth credentials regardless of which model is steering the cone. Use when you need fresh social-media signal, public reactions, or to find specific posts by keyword, hashtag, or handle.
