x-chat-provider

Focus on implementing custom Chat Provider, helping to adapt any streaming interface to Ant Design X standard format

Quality

58%

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/x-chat-provider/SKILL.md

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.

The content is highly actionable with executable TypeScript examples and a clear four-step workflow, but it repeats core rules across multiple sections and references a missing EXAMPLES.md while inlining material that could live in separate reference files.

Suggestions

Create the referenced 'reference/EXAMPLES.md' (or correct the path to 'references/') so the promised complete examples are actually available.

Consolidate the repeated 'only 3 methods / no status / no request method' guidance into one canonical section and cross-reference it from the checklist to reduce redundancy.

Move the detailed 'Core Types and Exports' and 'XRequest Advanced Configuration' material into a separate reference file, keeping SKILL.md a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete code with no basic-concept padding, but the same three rules (only 3 methods, no status field, no request method) are repeated across Step 3, Important Reminders, Quick Checklist, and Development Rules, which could be consolidated.	3 / 5
Actionability	Provides copy-paste-ready TypeScript (full MyChatProvider class, XRequest configs, callbacks, retry, transformStream) covering common cases, with only minor placeholders like 'https://your-api.com/chat' and a '/* ... */' dynamic example.	4 / 5
Workflow Clarity	The four-step process is clearly sequenced with a Step 3 verify table and a 'tsc --noEmit' type-check checkpoint, plus a post-completion checklist, but it lacks an explicit validate->fix->retry feedback loop.	4 / 5
Progressive Disclosure	Headers and a TOC give good structure and the EXAMPLES.md reference is clearly signaled, but the referenced 'reference/EXAMPLES.md' file does not exist in the bundle, and substantial API/type reference content is inlined rather than split into reference files.	3 / 5
	Total	14 / 20 Passed

Description

53%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 clearly conveys a focused, distinctive purpose but omits any explicit 'when to use' trigger guidance, which caps completeness and limits trigger-term quality. It is concise and niche-specific rather than generic.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when adapting a custom or non-standard streaming API to Ant Design X's Chat Provider, or when built-in OpenAI/DeepSeek/Default providers do not fit.'

Add natural synonyms users might say (e.g. 'X SDK', 'custom provider', 'useXChat integration') to broaden trigger coverage.

Optionally enumerate 1-2 more concrete actions (e.g. configuring XRequest, handling SSE transforms) to lift specificity from 3 toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain (Ant Design X) and two concrete actions — 'implementing custom Chat Provider' and 'adapt any streaming interface to Ant Design X standard format' — but does not list several specific actions for comprehensive coverage.	3 / 5
Completeness	Clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance for when Claude should invoke it, capping completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant terms ('Chat Provider', 'streaming interface', 'Ant Design X') a user of this SDK would say, but offers no synonyms or common variations (e.g. X SDK, useXChat, custom provider) and no explicit trigger phrases.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Ant Design X custom Chat Provider) with distinct triggers and minimal conflict risk, with only minor overlap against the related useXChat skill.	4 / 5
	Total	13 / 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: 2 missing	Warning

	Total	14 / 16 Passed

Repository: modelscope/ms-agent
Path: .agents/skills/x-chat-provider/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.