spotlight-search

Runs two scoped spotlight queries across a Grok Bot account and reports recorded hits with sources.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill spotlight-search-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spotlight-search
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/spotlight-search
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill spotlight-search-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When someone asks "where is that routine, shard, or setting" on a Grok Bot account, answers are often guesses or unverified claims. This Skill turns that question into two recorded, scoped spotlight queries so every hit cites its query, scope, and timestamp instead of relying on memory. ## Core Features & Use Cases - Scoped dual queries: Runs a narrow exact-match query first, then a broader synonym or neighboring-scope pass, recording query, scope, timestamp, and hits for each. - Hit verification: Confirms the most consequential hit against the authoritative surface (inventory, routine list, or settings read) before treating it as a finding. - Coverage honesty: Reports what the spotlight surface could not search, separating "no hits" from "does not exist". - Use Case: A teammate asks whether a specific routine exists anywhere on the account; the Skill runs both queries, verifies the top hit against the routine list, and answers found, absent, or unmeasured in one line. ## Quick Start Ask the assistant to use spotlight search to find where a named routine or setting lives on the Grok Bot account and report the recorded hits.

Frequently Asked Questions about spotlight-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find where a routine or setting lives on a Grok Bot account?▼

Run two scoped spotlight queries: first an exact-name query in the tightest scope, then a broader synonym or neighboring-scope pass. Record query, scope, timestamp, and hits for each, then verify the top hit against the owning surface such as the routine list or settings read.

How to verify a spotlight search hit before trusting it?▼

Take the single most consequential hit and confirm it against the authoritative surface that owns that object, such as the inventory or settings read. A spotlight hit confirmed elsewhere is a finding; unconfirmed, it is only a lead.

Does spotlight search modify anything on the account?▼

No, the skill is strictly read-only. It never changes settings, renames objects, or acts on a hit while searching, and if the surface needs access that was not granted, it records the scope as unreachable instead of improvising access.

Why does a spotlight search with no hits not prove something is absent?▼

No hits only means the searched scopes returned nothing; any scope the queries did not cover is a gap, not a negative. The report must name every unsearched scope and distinguish absent (scopes checked) from unmeasured (what blocked the read).

What are the limitations of account-wide spotlight search?▼

Spotlight is an index over the account, not the authoritative record, so a hit that contradicts the owning surface is flagged rather than trusted. Coverage is limited to the scopes the surface can actually search, and unreachable scopes are reported as gaps.