x-research

X/Twitter public sentiment research for recent market, company, product, or community discourse. Use when the brief asks what people are saying on X, Twitter sentiment, CT sentiment, public opinion, expert posts, or social reaction around a stock, sector, company, product, or market event.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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.

A well-structured, actionable workflow contract that gives Claude specific query decomposition, coverage tracking, and a ready-to-fill report template without padding. The main improvement opportunity is tightening the introductory boundary disclaimer and adding an explicit post-synthesis verification step.

Suggestions

Tighten the introductory boundary sentence: replace the enumerated 'does not add ...' list with a single statement that the skill is a workflow contract and adds no tools or credentials.

Add an explicit verification step to the workflow (e.g., confirm every cited post maps to a Sources entry and that coverage status is recorded for each source before saving).

Specify how sentiment confidence is determined (e.g., based on source count, agreement across themes, and freshness) so the synthesis step is fully actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no over-explanation of concepts; the only minor padding is the boundary disclaimer enumerating what the skill does NOT add ('x_search tool, X API credentials, provider settings, slash commands, daemon routes, or runtime modules'), so it sits at efficient-with-minor-trim rather than a 5.	4 / 5
Actionability	Concrete, specific guidance throughout: enumerated query signal terms ('bullish', 'upside', 'catalyst'), explicit coverage-status values, and a copy-paste-ready Markdown report template; falls just short of 5 because sentiment-confidence determination and a few execution details remain implicit.	4 / 5
Workflow Clarity	Six clearly numbered, well-sequenced steps with a source-coverage checkpoint (checked/unavailable/thin/not relevant) and caveats; not a 5 because there is no explicit verify/feedback loop after synthesis, though this research task is neither destructive nor batch so the validation cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Source Access Rules, Workflow, Markdown Report Contract, Attribution) with no nested references and no content that clearly belongs in a separate file; not a 5 only because the body exceeds 50 lines and lacks the one-level-deep reference structure the top anchor describes.	4 / 5
	Total	16 / 20 Passed

Description

90%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, well-structured description that clearly defines a niche domain and provides explicit, natural trigger phrases covering both what and when. The only mild weakness is that it names a single research action rather than enumerating several concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('X/Twitter public sentiment research') and a concrete action ('research ... discourse') but offers only one core action rather than a comprehensive list, matching the 'names domain and 1-2 concrete actions' anchor; not a 4 because no several specific actions are enumerated.	3 / 5
Completeness	Explicitly states what it does ('X/Twitter public sentiment research for recent market, company, product, or community discourse') and when to use it with concrete trigger phrases, matching the 'clearly answers both what AND when' anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including 'what people are saying on X', 'Twitter sentiment', 'CT sentiment', 'public opinion', 'expert posts', and 'social reaction' with synonyms; matches the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (X/Twitter public sentiment) with distinct, specialized triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/x-research/SKILL.md
Commit: 1a7a23d

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

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.