CtrlK
BlogDocsLog inGet started
Tessl Logo

xai-x-search

Search Twitter/X in real-time using Grok API. Use when searching X posts, tracking trends, monitoring accounts, or analyzing social discussions.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/xai-x-search/SKILL.md

The canonical home for this skill is xai-x-search in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with complete, executable code examples, but suffers from noticeable verbosity due to repetitive near-identical functions and inlines content that would benefit from progressive disclosure into separate reference files.

Suggestions

Consolidate the seven near-identical search wrapper functions into one parameterized example plus a compact table of prompt templates, removing the repetitive chat.completions.create boilerplate.

Move the detailed use-case examples (financial news, earnings reaction, competitor analysis) and the Agent Tools API reference into separate reference files linked from SKILL.md to improve progressive disclosure.

Trim the Best Practices section so it does not repeat the full API call pattern; show only the differing query strings.

DimensionReasoningScore

Conciseness

Noticeably verbose: seven near-identical chat.completions.create wrapper functions (topic, stock, account, trending, plus three use cases) and a Best Practices section that repeats the same call pattern are padded sections that could be consolidated into one parameterized example.

2 / 5

Actionability

Fully executable, copy-paste-ready code throughout, with specific examples covering topic search, stock mentions, account monitoring, trending, handle/date filters, JSON-structured output, and error handling.

5 / 5

Workflow Clarity

The single core action (one API call) is unambiguous and an error-handling example provides a basic feedback loop; no multi-step sequence is required for this simple skill, but explicit checkpoints are absent.

4 / 5

Progressive Disclosure

Content is well-sectioned with clear headers, but at ~310 lines it inlines API reference and many use-case examples that could live in separate reference files; the only references are external doc URLs with no internal file split.

3 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states the capability and provides explicit 'Use when' trigger guidance with natural keywords. Minor improvements possible around action variety and synonym coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('searching X posts, tracking trends, monitoring accounts, analyzing social discussions') but they are all variations of the single underlying search capability, leaving minor coverage gaps rather than comprehensive distinct actions.

4 / 5

Completeness

Explicitly answers both 'what' ('Search Twitter/X in real-time using Grok API') and 'when' ('Use when searching X posts, tracking trends, monitoring accounts, or analyzing social discussions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Twitter/X', 'X posts', 'trends', 'accounts', 'social discussions') that users would actually say, though a few synonyms such as 'tweets' are missing.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (real-time X search via Grok) with distinct triggers, but minor overlap risk with closely related xai-sentiment / xai-stock-sentiment skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
fernandezbaptiste/Skrillz
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.