CtrlK
BlogDocsLog inGet started
Tessl Logo

x-components

Use when building AI chat UIs with @ant-design/x components — covers Bubble, Sender, Conversations, Prompts, ThoughtChain, Actions, Welcome, Attachments, Sources, Suggestion, Think, FileCard, CodeHighlighter, Mermaid, Folder, XProvider, and Notification.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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-organized, actionable overview with a clean workflow and concrete rules, but its progressive-disclosure promise is undermined because all three referenced detail files (reference/COMPONENTS.md, PATTERNS.md, API.md) are missing from the bundle.

Suggestions

Ship the referenced bundle files (reference/COMPONENTS.md, reference/PATTERNS.md, reference/API.md) so the one-level-deep links resolve; without them the skill's detail layer is unreachable.

Trim the redundant 'Skill Positioning' intro and emoji Table of Contents — both restate information already in the description and section headers — to push conciseness toward fully lean.

Inline one or two key prop snippets (e.g. Bubble.List items shape, Sender onSubmit) in the quick-start example so the skill is actionable even before the reader opens API.md.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with a single minimal code example and assumes Claude's competence; minor redundancy (the 'Skill Positioning' intro restates the description, plus an emoji Table of Contents) keeps it just below fully efficient.

4 / 5

Actionability

Provides a copy-paste-ready TSX example and concrete, specific rules ('Bubble.List not Bubble in loops', 'streaming={true} during stream'); precise prop details are deferred to API.md rather than shown inline, leaving minor gaps.

4 / 5

Workflow Clarity

The 'Recommended Workflow' gives a clear 4-step sequence (pick components, use patterns, wrap XProvider, use API); no validation checkpoints, but UI composition is non-destructive so they are not required, leaving only minor gaps.

4 / 5

Progressive Disclosure

Structure is good — an overview with clearly signaled one-level-deep references (decision-guide table + Reference Resources section) to COMPONENTS.md, PATTERNS.md, API.md — but those referenced files do not exist in the bundle, so the disclosed detail cannot actually be reached.

3 / 5

Total

15

/

20

Passed

Description

92%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, specific description that states a clear trigger ('Use when building AI chat UIs with @ant-design/x') and enumerates the full component surface it covers. It is concise, third-person, and well-differentiated from sibling x-skills.

DimensionReasoningScore

Specificity

Names the domain ('building AI chat UIs with @ant-design/x components') and comprehensively enumerates 17 concrete components (Bubble, Sender, Conversations, ... XProvider, and Notification), giving full concrete coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' ('covers Bubble, Sender, ... Notification') and 'when' ('Use when building AI chat UIs with @ant-design/x components') with a concrete trigger phrase, matching the top anchor.

5 / 5

Trigger Term Quality

Includes the natural phrase 'building AI chat UIs' and the package name users would cite, plus many component names; a few common synonyms (e.g. 'chatbot', 'conversation UI') are absent, so it is just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The '@ant-design/x components' niche is highly specific with distinct triggers and minimal conflict risk; data-flow sibling skills are explicitly out of scope, keeping the trigger boundary clean.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 18 missing

Warning

Total

14

/

16

Passed

Repository
modelscope/ms-agent
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.