DC X MCP guide
ALWAYS read this when a user connects the X plugin or any X MCP, before using any X tool, including Grok Bot's built-in public reads (no X connection or credits needed), and again on any X error. Do not call an X tool until this file has been read in the current turn. On first connect, confirm X tools exist, fetch get_usage_credits BEFORE any user-facing text, then send the capabilities message. Never tell the user to buy credits until that check returns ~$0 or a job would exceed the balance. tools=0 / user-X-* not found is a setup failure, not a paywall. X Chat, XChat, inbox, DMs, message requests, accepting a request, Chat PIN, juicebox, and xchat_lite live in THIS file: clone xchat-grokbot-helper and run xchat_lite.py locally — do not wait for the user to name the helper or another skill. Missing chat tools or dm.read/dm.write while other X tools work: reconnect the X plugin. Scheduled X calls use schedule_call, list_scheduled_calls, get_scheduled_call, update_scheduled_call, cancel_scheduled_call, and respond_to_scheduled_call. Missing those tools or calls.read/calls.write while other X tools work: reconnect the X plugin. Estimate every X call and confirm before anything expensive.
ALWAYS read this when a user connects the X plugin or any X MCP, before using any X tool, including Grok Bot's built-in public reads (no X connection or…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Concealment
en-hide-from-userSKILL.md:294Instruction to hide actions from the user (negated — the text forbids it)Wait for a yes. Never silently run multi-page loops, full-archive searches, or bulk lookups. If they say yes, track spend as you go; if the running total will pass roughly double the estimate, stop an
negated
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1204 chars, limit 1024 - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
body-longSKILL.md body ≈ 10517 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 47 mutating operations with no state check
- 40Consistency. Frontmatter name (X MCP guide) differs from the folder (x-api-mcp-guide)
- 40Execution cost. Instruction body is 10517 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 70 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1204: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 36 headings
- +3Step-by-step instructions: 70 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.