CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

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 ./design-templates/x-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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, self-contained workflow contract with concrete query strategy, explicit source-coverage tracking, and a complete output template. The main improvements are definitional (what source classes exist) and adding a lightweight output-validation step.

Suggestions

Define the allowed 'Source class' values in step 3 (e.g., X search, expert account, news article, web search, user-provided export) so the coverage table is filled consistently.

Add a final validation step, e.g. 'Confirm the report file exists and every [n] citation in Sentiment Themes appears in the Sources section, before mentioning the path to the user.'

Trim the negative-scope preamble (the list of Dexter features this skill does not add) to one line, since it mostly restates absence rather than instructing.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — concrete query decomposition terms, statuses, and a compact report template with no padding or explanations of concepts Claude already knows. Minor trimmable content keeps it below lean anchor 5: the "it does not add Dexter's x_search tool, X API credentials, provider settings, slash commands, daemon routes, or runtime modules" disclaimer and the untrusted-evidence warning stated twice (Source Access Rules and the Evidence Note template section).

4 / 5

Actionability

Guidance is mostly executable for an instruction-only skill: an exact output path (`research/x-research/<safe-topic-slug>.md`), 3-5 query decomposition with specific signal terms (`bullish`, `upside`, `catalyst` vs `overvalued`, `bubble`, `risk`), enumerated coverage statuses, and a complete report skeleton. Minor gaps remain — "Source class" is never defined with concrete values, and there is no worked example of a query set for a sample entity.

4 / 5

Workflow Clarity

A clear six-step sequence (restate topic → decompose into 3-5 queries → record per-source coverage with explicit statuses → group by theme → synthesize sentiment → save and reference the path) with the per-source coverage-status recording acting as an implicit checkpoint. It falls short of anchor 5 because there is no explicit validation step (e.g., verifying the saved file exists or that every cited [n] appears in the Sources section), though the non-destructive nature keeps it solidly at 4 rather than 3.

4 / 5

Progressive Disclosure

The skill is self-contained with no references/, scripts/, or assets/ bundle directories, and nothing inlined that belongs in a separate file at its ~88-line scale. Sections (Source Access Rules, Workflow, Markdown Report Contract, Attribution) are well-organized and easy to navigate, so per the simple-skill guidance a well-organized single-file structure earns full marks.

5 / 5

Total

17

/

20

Passed

Description

78%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 description with an explicit Use-when clause, third-person voice, rich natural trigger phrasing (including crypto-Twitter slang and Chinese terms), and a well-defined niche. Its only real weakness is that it describes a single capability rather than enumerating multiple concrete actions.

DimensionReasoningScore

Specificity

Names the domain precisely ("X/Twitter public sentiment research for recent market, company, product, or community discourse") and one concrete action (sentiment research), but does not list several distinct concrete actions the way a 4 or 5 requires. It is a single-capability description rather than a comprehensive action list.

3 / 5

Completeness

Explicitly answers both questions: the "what" ("X/Twitter public sentiment research for recent market, company, product, or community discourse") and the "when" via a concrete "Use when the brief asks what people are saying on X, Twitter sentiment, CT sentiment, public opinion..." clause with concrete trigger phrases. This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Strong natural-phrase coverage — "what people are saying on X", "Twitter sentiment", "CT sentiment", "public opinion", "expert posts", "social reaction" — including slang and bilingual variants. A few natural terms users might say (e.g. "tweets", "X sentiment", "stocktwits") are absent, which keeps it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The X/Twitter market-sentiment niche is distinct with dedicated triggers, but broader phrases like "public opinion" and "social reaction" create minor overlap risk with general research or social-media analysis skills — matching "mostly distinct; minor overlap risk" rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

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.

Validation — 15 / 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
nexu-io/open-design
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.