use-x-chat

Focus on explaining how to use the useXChat Hook, including custom Provider integration, message management, error handling, multi-conversation management, and more

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/use-x-chat/SKILL.md

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.

The body is highly actionable with complete executable examples and a clear integration workflow including a validation checkpoint. Its main weakness is progressive disclosure: it points to reference/CORE.md, API.md, and EXAMPLES.md that are absent from the bundle, while inlining dense API tables that belong in those files.

Suggestions

Provide the missing reference/ files (CORE.md, API.md, EXAMPLES.md) or remove the broken links and keep that content inline intentionally.

Move the full Configuration Options and Return Values tables into reference/API.md, leaving a few key examples inline in SKILL.md.

Add an explicit validate→fix→retry loop around 'tsc --noEmit' (e.g. 'If errors appear, fix them and re-run until clean') to reach the top workflow-clarity anchor.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no 'what is a Hook/Provider' padding) and stays code-and-table dense, but carries minor trimmable overhead — emoji headers, a full table of contents, and inlined option/return-value tables — that keeps it just below the lean anchor 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TSX for the common cases — three-step integration, Bubble.List mapping, requestFallback/abort, and a complete multi-conversation pattern — covering the real scenarios a user would hit.	5 / 5
Workflow Clarity	A clear three-step sequence (Provider → Basic Usage → UI Integration) plus a Development Rules checklist with an explicit 'tsc --noEmit' validation checkpoint; falls short of anchor 5 only because the validate→fix→retry feedback loop is implied rather than spelled out.	4 / 5
Progressive Disclosure	Structure and section headers are good and references are clearly signaled, but the referenced files (reference/CORE.md, API.md, EXAMPLES.md) do not exist in the bundle and substantial reference material (full config/return-value tables) is inlined rather than split out.	3 / 5
	Total	16 / 20 Passed

Description

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

The description lists several concrete capabilities of the useXChat Hook but omits any explicit 'when to use' trigger guidance and leans on technical jargon over natural user phrasing. It is reasonably distinct within its niche but would benefit from a Use-when clause and synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building AI chat/conversation UIs with @ant-design/x-sdk and the useXChat Hook.'

Replace the vague 'and more' with the remaining concrete capabilities or drop it to avoid over-claiming.

Add natural synonyms users might say (e.g. 'AI chat app', 'conversation UI', 'x-sdk chat') alongside the technical terms.

Dimension	Reasoning	Score
Specificity	Names the domain (useXChat Hook) and several concrete actions — 'custom Provider integration, message management, error handling, multi-conversation management' — but the trailing 'and more' hedges and leaves coverage incomplete, stopping short of the comprehensive anchor 5.	4 / 5
Completeness	Has a clear 'what' (explaining useXChat usage with listed capabilities) but no 'when' / 'Use when...' trigger clause at all; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant domain terms ('useXChat Hook', 'Provider integration', 'multi-conversation') that practitioners would say, but relies on technical jargon with no natural user-facing phrasing or synonyms, missing common variations.	3 / 5
Distinctiveness Conflict Risk	The useXChat Hook is a specific niche tied to @ant-design/x-sdk with mostly distinct triggers, though it has minor overlap risk with the closely related x-chat-provider skill that it does not differentiate from.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 missing, 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: modelscope/ms-agent
Path: .agents/skills/use-x-chat/SKILL.md
Commit: a56afcc

Reviewed: 2 days 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.