Syncfusion JavaScript Chat UI — conversational interfaces (short listing)

Prerequisites: a JavaScript/TypeScript project; the @syncfusion/ej2-interactive-chat package installed (check license terms — a free community license exists for eligible users); your own messaging backend to wire up Install "Syncfusion JavaScript Chat UI — conversational interfaces (short listing)" for me. It gives my agent the official @syncfusion implementation guide for the Chat UI control: message management and grouping, typing indicators, file attachments, @mentions, suggestions, header/footer customization, message templates, load-on-demand, RTL and accessibility — with working examples. IMPORTANT: the license was not verifiable (the discovery manifest records null) — fetch from the link only, reproduce nothing beyond the link, and read the terms yourself before use. Syncfusion controls are commercial — check the license terms for your case. Repository: https://github.com/syncfusion/javascript-ui-controls-skills/blob/main/skills/syncfusion-javascript-chat-ui/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This is a UI-reference skill — any code beyond widget examples and package installs is a red flag. This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "syncfusion-javascript-chat-ui". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the pinned ej2-interactive-chat package, verify your Syncfusion license eligibility, wire up your own messaging backend, and check the package changelog before shipping). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.