x-request

Focus on explaining the practical configuration and usage of XRequest, providing accurate configuration instructions based on official documentation

Quality

50%

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-request/SKILL.md

Quality

Content

46%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 concrete executable TypeScript examples, but it is padded with decorative structure and repeated diagrams, and its progressive disclosure is broken because the referenced reference/ files do not exist in the bundle. Workflow sequencing is implicit rather than crisply validated.

Suggestions

Create the missing reference files (reference/CORE.md, reference/API.md, reference/EXAMPLES_SERVICE_PROVIDER.md) or move their promised content inline so the links are not broken.

Trim the decorative table of contents, redundant emoji headers, and the duplicated skill-collaboration mermaid diagram to reduce token overhead.

Add an explicitly numbered workflow with validation checkpoints (e.g. configure → validateSecurity → tsc --noEmit → send test request) so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: a large decorative table of contents, emoji-laden headers, repeated skill-collaboration mermaid diagrams (the same x-request→x-chat-provider→use-x-chat graph appears twice), and padded comparison tables that could be trimmed without losing information.	2 / 5
Actionability	Code examples are concrete and executable (install commands, XRequest TypeScript usage, a validateSecurity function, a checkConfig script), covering the common cases with only minor gaps such as incomplete placeholder checks.	4 / 5
Workflow Clarity	Sections imply a rough order (Quick Start → Core Config → Security → Debugging → Usage) and a checklist plus validation function exist, but there is no explicitly numbered sequence with validation checkpoints tying the steps together.	3 / 5
Progressive Disclosure	The body delegates 'Core Configuration Details' and API reference to reference/CORE.md, reference/API.md, and reference/EXAMPLES_SERVICE_PROVIDER.md, but those files do not exist in the bundle, so the promised detail is inaccessible and key reference content is effectively missing.	2 / 5
	Total	11 / 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 identifies a specific tool (XRequest) and its configuration focus, but it lacks an explicit 'when to use' trigger clause and leans on abstract meta-language ('explaining', 'providing instructions') rather than concrete capability verbs. It is mostly distinct from sibling skills but would benefit from trigger phrases.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when configuring XRequest for streaming AI chat requests, SSE/JSON responses, or integrating @ant-design/x-sdk request handling.'

Replace abstract meta-verbs ('explaining', 'providing instructions') with concrete capability verbs like 'Configure XRequest for streaming, authentication, and error handling across Node.js and browser environments.'

Include natural trigger synonyms users would actually say, such as 'XRequest', 'x-sdk request', 'streaming chat API', and 'SSE configuration'.

Dimension	Reasoning	Score
Specificity	The description names the domain concretely ("XRequest") and gives 1-2 actions ("explaining the practical configuration and usage", "providing accurate configuration instructions"), but these are meta-actions about explaining rather than concrete capabilities, and coverage is not comprehensive.	3 / 5
Completeness	A clear 'what' is present (explain/apply XRequest configuration per official docs) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	"XRequest" and "configuration" are relevant terms a user might say, but common variations/synonyms and natural trigger phrases are missing, so keyword coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Naming "XRequest" specifically gives a clear niche with minimal conflict risk; only minor overlap exists with sibling @ant-design/x-sdk skills such as x-chat-provider and use-x-chat, so it is mostly distinct rather than fully conflict-free.	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: 3 missing	Warning

	Total	14 / 16 Passed

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