菜单
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 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.
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 | x-search |
| description | 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. |
| allowed-tools | bash |
Run x_search from bash. The script pipes a one-shot request to xAI's
Responses API with the x_search server tool enabled, then prints the
model's answer plus any citation URLs.
The shell command resolves the bearer token through oauth-token xai-grok,
so you must be signed in to xAI Grok first:
oauth-token xai-grok
If the command prints xai-grok: not signed in, run /login in the side
panel (or the same oauth-token xai-grok interactively) to complete the
xAI OAuth flow before searching.
# Free-form query — most common usage
x_search "what are people saying about Grok 4.3?"
# Restrict to specific handles (comma-separated, max 10)
x_search --from "elonmusk,xai" "ship dates for Grok"
# Date range (ISO 8601)
x_search --since 2025-01-01 --until 2025-03-31 "earnings call reactions"
# Pin the underlying search model (default: grok-4.3)
PI_XAI_X_SEARCH_MODEL=grok-4.20-0309-reasoning x_search "fed minutes hot takes"
Plain text answer followed by citations:
Recent posts indicate broadly positive sentiment …
Sources:
- https://x.com/user/status/...
- https://x.com/user/status/...
x_search is a separate xAI request, not a context-bearing tool call. The
result is folded into your transcript as a bash result, so you can quote
or summarize it directly.enable_image_understanding / enable_video_understanding
toggles are intentionally not exposed; xAI's defaults are sensible and the
toggles bloat the response.pi.registerTool does not
apply here. The behavior matches stnly/pi-grok's x_search tool.