Repository navigation
X skill: work with Grok Bot's built-in public reads - #566
Closed
santiagomed wants to merge 1 commit into
Closed
santiagomed wants to merge 1 commit into
santiagomed wants to merge 1 commit into
Conversation
Grok Bot reads public posts, users, search, trends, and news through its own X access, with no X connection and no user credits. The guide now covers those reads in its trigger, and says not to ask the user to connect X, check credits, or estimate a cost for them. get_usage_credits and get_users_me exist only on the user's X connection, so their absence next to built-in reads is not error 2 or an outage.
This was referenced Oct 12, 2026
Collaborator
Author
|
Combined into #580. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Grok Bot now reads public posts, users, search, trends, and news through its own X access, and tells the model those reads need no X connection. The X MCP guide didn't account for that. Its trigger only covered "any X connection", and its connect order, credits check, and cost estimates assume
get_usage_creditsandget_users_meare there. Those two tools only exist on the user's own X connection, so with built-in reads alone the guide pointed at error 2 or the outage line, which gave the model a reason to skip it.The trigger now names Grok Bot's built-in public reads, and a short section says not to ask the user to connect X, check credits, or estimate a cost for them, and that a missing
get_usage_creditsorget_users_methere isn't an error. The user's own account, home timeline, bookmarks, and X Chat still go through their X connection and the rest of the guide. Hosts without built-in reads, like Cursor, are unchanged.There's no version bump or CHANGELOG entry, so this merges cleanly with #563 and the X Chat media change stacked on it.
Test plan
Note
Low Risk
Documentation-only change to an agent skill file; no runtime code or auth paths modified.
Overview
Updates the X MCP guide skill so agents handle Grok Bot’s built-in public X reads without treating missing user-connection tools as setup failures or paywalls.
The skill description now requires reading the guide before any X tool use, including those built-in reads (no connect/credits). A new Built-in X reads section tells the model to skip connect,
get_usage_credits, and cost estimates for public posts, users, search, trends, and news when the host provides its own access, and clarifies that missingget_usage_credits/get_users_mein that mode is not error 2 or an outage. Connect order, credits checks, bookmarks, home timeline, and X Chat behavior for a real user X connection are unchanged; hosts without built-in reads (e.g. Cursor) are unaffected.Reviewed by Cursor Bugbot for commit c309585. Bugbot is set up for automated code reviews on this repo. Configure here.