x-search-skill
- Repo stars 0
- Author updated Live
- Author repo Temple-of-Skills
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @Tomatio13 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: x-search-skill
description: Search X posts and get Grok-grounded summaries via the local x-search CLI. Use when the user wan…
category: writing
runtime: no special runtime
---
# x-search-skill output preview
## PART A: Task fit
- Use case: Search X posts and get Grok-grounded summaries via the local x-search CLI. Use when the user wants X search, summaries of reactions on X, cited X post URLs, or X result filtering by handle, date, image, or video..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Trigger conditions / Core workflow / Mode selection” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Search X posts and get Grok-grounded summaries via the local x-search CLI. Use when the user wants X search, summaries of reactions on X, cited X post URLs, or X result filtering by handle, date, image, or video.”.
- **02** When the source has headings, the agent prioritizes “Trigger conditions / Core workflow / Mode selection” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Trigger conditions / Core workflow / Mode selection”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: x-search-skill
description: Search X posts and get Grok-grounded summaries via the local x-search CLI. Use when the user wan…
category: writing
source: Tomatio13/Temple-of-Skills
---
# x-search-skill
## When to use
- Search X posts and get Grok-grounded summaries via the local x-search CLI. Use when the user wants X search, summaries…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Trigger conditions / Core workflow / Mode selection” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "x-search-skill" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Trigger conditions / Core workflow / Mode selection
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}X Search
Use the local x-search command when the user specifically needs information from X posts rather than general web results. Assumes x-search is already installed and authenticated.
Trigger conditions
- Use this skill when the user asks for reactions on X, cited X post URLs, or summaries grounded in X search results.
- Use this skill when the user wants X results filtered by handle, date, image, or video.
- Do not use this skill for general web research unless X is the required source.
- If X is the primary source, use this skill first and add non-X sources only when the user needs supplemental context.
Core workflow
- Convert the request into one clear X-search prompt with topic, timeframe, and expected deliverable.
- Pick the output mode first: summary, citations, URLs, or full JSON.
- Add only the narrowest filters needed: handle, date, image, or video.
- Run
x-searchonce and inspect whether the result is broad, empty, or missing evidence. - Tighten the prompt before stacking many flags.
- If the user needs evidence, rerun with
--mode citationsor--mode urls. - Verify that the result matches the requested timeframe, topic, and evidence level before answering.
Mode selection
- Use
--mode answerfor a direct summary. - Use
--mode citationsfor labeled citation URLs. - Use
--mode urlsfor raw source collection. - Use
--mode jsonfor debugging or downstream parsing.
Option rules
- Use
--allowed-handlefor a trusted-account subset. - Use
--excluded-handleto remove noisy accounts. - MUST NOT combine
--allowed-handleand--excluded-handle. - MUST use
--from-dateand--to-dateonly withYYYY-MM-DD. - Convert relative dates such as
today,yesterday, orthis weekinto explicit bounds when feasible. - Only enable
--imageor--videowhen the request depends on media understanding. - The default model is
grok-4.3. Override with--modelonly when the task needs a different tradeoff.
Prompt rules
- Ask for one concrete deliverable per call.
- Include the topic, timeframe, and angle in the prompt text.
- Prefer prompts such as
Summarize reactions on X,Find posts discussing, orCompare opinions on X. - If recency matters, say so in the prompt even when date filters are present.
- Prompt text may be written in English for consistency with the command examples.
Failure handling
- If
x-searchis not found, stop and report that the CLI must be installed first. - If the command fails because of invalid arguments, fix the command shape before retrying.
- If the command exits non-zero, check authentication or Hermes configuration next.
- If the result is empty, too broad, or lacks evidence, refine the prompt and rerun once.
- If citations are required but the summary is not enough, rerun with
--mode citations,--mode urls, or--mode json. - If the query comes from standard input, pipe it into
x-searchinstead of rewriting the content by hand.
References
- For ready-to-run command templates, see references/COMMANDS.md.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review