메뉴
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 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 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.
Use this when you receive a Navigate Event lick — emitted whenever the user opens a tab whose main-frame response advertises a SLICC handoff via an RFC 8288 `Link` header. This skill renders the yes/no approval card the user must accept before anything happens. Covers the `handoff:` and `upskill:` verb prefixes and the security rules (never auto-accept, never fetch before approval).
| name | slicc-handoff |
| description | 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 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.
handoff:<instruction> — continue the task in SLICC.upskill:<github-url> — ask SLICC to install a skill from a GitHub repo.--open to open the handoff URL. Show one of:
.agents/skills/slicc-handoff/scripts/slicc-handoff --open "handoff:<instruction>".agents/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:<github-url>"If the user runs a non-default SLICC instance on another port, prefix the call with SLICC_PORT=5720 (or whatever port they chose) so the localhost POST hits the right instance.
The script builds a URL like https://www.sliccy.ai/handoff?handoff=<urlencoded> (or ?upskill=<urlencoded-github-url>). Two delivery paths fire in parallel:
http://localhost:${SLICC_PORT ?? 5710}/api/handoff with the structured payload { verb, target, instruction?, url, title } — verb is handoff or upskill, target is the github URL for upskill or the handoff URL for handoff, and instruction carries the prose for handoff. The node-server rebroadcasts it as a navigate lick to the connected webapp. Profile-independent: reaches SLICC even when the user's default browser is a different Chrome profile than the one SLICC controls.--open opens the URL in the local browser. If that browser profile has the SLICC extension installed, chrome.webRequest parses the response's RFC 8288 Link header (rel https://www.sliccy.ai/rel/handoff or https://www.sliccy.ai/rel/upskill) and emits the navigate lick when one of those rels is present.Either path results in a yes/no approval card in the cone; accept dispatches by verb prefix.
.agents/skills/slicc-handoff/scripts/slicc-handoff --open "Continue the signup flow in the browser"
.agents/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:https://github.com/slicc/skills-extra"
Install only a sub-path of a repo (a single skill on a specific branch):
.agents/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:https://github.com/slicc/skills-extra/tree/main/skills/foo"