Cometchat Angular V5 Migration
cometchat/cometchat-skills
Upgrade an Angular app from CometChat UI Kit v4 → v5 (@cometchat/chat-uikit-angular ^4 → ^5).
Quick-reference for building the core Ignite UI for Angular library and related packages.
Install Igniteui Angular Build
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-build --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/igniteui-angular-build .claude/skills/igniteui-angular-build && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "igniteui-angular-build" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-build into .claude/skills/igniteui-angular-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-build", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-buildType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-build --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/igniteui-angular-build .agents/skills/igniteui-angular-build && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "igniteui-angular-build" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-build into .agents/skills/igniteui-angular-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-build", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-build --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/igniteui-angular-build .cursor/skills/igniteui-angular-build && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "igniteui-angular-build" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-build into .cursor/skills/igniteui-angular-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-build", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/IgniteUI/igniteui-angular.git --path .agents/skills/igniteui-angular-build--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-build --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/igniteui-angular-build .gemini/skills/igniteui-angular-build && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "igniteui-angular-build" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-build into .gemini/skills/igniteui-angular-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-build", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-buildInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/igniteui-angular-build .github/skills/igniteui-angular-build && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-angular-build" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-build into .github/skills/igniteui-angular-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-build", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-build --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/igniteui-angular-build .opencode/skills/igniteui-angular-build && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-angular-build" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-build into .opencode/skills/igniteui-angular-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-build", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
igniteui-angular-build- GitHub stars
- 599
- Token cost
- ~898 tokens
- SKILL.md length
- 315 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Quick-reference for building the core Ignite UI for Angular library and related packages.
- Works in 2 steps: ng build igniteui-angular… → npm run build:styles — runs node…
- An agent needs to compile the library
- SKILL.md covers Prerequisites, Full Build, Library Build (most common) and Partial Builds, plus 2 more sections
- Calls npm and node
What it does
Igniteui Angular Build is an agent skill from IgniteUI/igniteui-angular. Quick-reference for building the core Ignite UI for Angular library and related packages. Covers the full production build (build:lib), individual partial builds (styles, extras, migrations, schematics, i18n, elements), and the combined build-all command. Use when an agent needs to compile the library, produce a dist output, or verify that code changes compile cleanly. Do NOT use for running tests — use igniteui-angular-testing instead. Do NOT use for linting — use igniteui-angular-linting instead.
Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Internationalization and Linting and formatting. It works with Angular and npm. The repository describes itself as: Ignite UI for Angular is a complete library of Angular UI components with the fastest grids and charts, dock manager, and more.
When your agent uses it
- An agent needs to compile the library
- Produce a dist output
- Verify that code changes compile cleanly
- Running tests — use igniteui-angular-testing instead
Example prompts
- “/igniteui-angular-build”
Requirements
- Node.js
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- ng build igniteui-angular --configuration production — compiles the library with ng-packagr using Angular Package Format. Uses…
- npm run build:styles — runs node scripts/build-styles.mjs to compile and bundle Sass themes into distributable CSS.
What it can do on your machine
Read from SKILL.md and the folder at commit 436e825. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Igniteui Angular Build loads about 898 tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 315 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 315 words (~898 tokens).
“Quick-reference card for the core library and related build commands in this repository.”
- name
- igniteui-angular-build
- user-invocable
- true
Files
Just SKILL.md in .agents/skills/igniteui-angular-build of IgniteUI/igniteui-angular.
Open the folder on GitHubat commit 436e825
Compare with similar skills
Igniteui Angular Build next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Igniteui Angular Build this skillIgniteUI/igniteui-angular | 599 | — | ~898 | Automated safety check: Pass | Custom licence | |
| Cometchat Angular V5 Migrationcometchat/cometchat-skills | 129 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Stylelintmanagedcode/dotnet-skills | 486 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Frontend Build Timing Auditopenops-cloud/openops | 1.1k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Sanity Best Practicesrobotostudio/turbo-start-sanity | 182 | — | ~940 | Automated safety check: Pass | MIT | |
| Managing MCP IndexComfy-Org/workflow_templates | 1.3k | — | ~1.9k | Automated safety check: Notes | MIT |
Similar skills
Stylelint
managedcode/dotnet-skills
Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends.
Frontend Build Timing Audit
openops-cloud/openops
Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t()…
Sanity Best Practices
robotostudio/turbo-start-sanity
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and…
Managing MCP Index
Comfy-Org/workflow_templates
Builds and maintains templates/index.mcp.json for Comfy Cloud MCP tools.
Desktop i18n for Cursor BYOK
leookun/cursor-byok
Rules for localizing the Cursor BYOK desktop app: the global t() function, complete locale catalogs, system-language selection and the scan-and-check commands.
More from IgniteUI/igniteui-angular
All 9 skills in this repoIgniteui Angular Linting
IgniteUI/igniteui-angular
Quick-reference for linting the core Ignite UI for Angular library.
Igniteui Angular Generate From Image Design
IgniteUI/igniteui-angular
Implements Angular application views from design images using Ignite UI Angular components.
Igniteui Angular Theming
IgniteUI/igniteui-angular
Generates and customizes Ignite UI for Angular themes including color palettes, typography, elevations, and component-level styles using the Sass theming system and the igniteui-theming MCP server.
Igniteui Angular Figma To App
IgniteUI/igniteui-angular
Builds Angular views from Figma designs with Ignite UI for Angular, supporting Indigo.Design kits, third-party kits, and plain frames.
Igniteui Angular Testing
IgniteUI/igniteui-angular
Quick-reference for running Ignite UI for Angular test suites.
Igniteui Angular Components
IgniteUI/igniteui-angular
Covers all non-grid Ignite UI for Angular UI components: application scaffolding and setup, form controls (inputs, combos, selects, date/time pickers, calendar, checkbox, radio, switch, slider)…
Related
Categories
Questions about Igniteui Angular Build
What does Igniteui Angular Build do?
Quick-reference for building the core Ignite UI for Angular library and related packages. Igniteui Angular Build is an agent skill from IgniteUI/igniteui-angular. Quick-reference for building the core Ignite UI for Angular library and related packages.
When should I use Igniteui Angular Build?
Igniteui Angular Build fits situations like: an agent needs to compile the library; produce a dist output; verify that code changes compile cleanly; running tests — use igniteui-angular-testing instead.
How do I install Igniteui Angular Build in Claude Code?
Run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a claude-code`. Or copy the skill folder (.agents/skills/igniteui-angular-build in IgniteUI/igniteui-angular) into .claude/skills/igniteui-angular-build in your project. Claude Code loads it when a task matches its description.
How do I install Igniteui Angular Build in Codex?
Run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a codex`. Or copy the skill folder (.agents/skills/igniteui-angular-build in IgniteUI/igniteui-angular) into .agents/skills/igniteui-angular-build in your project. Codex loads it when a task matches its description.
Can I use Igniteui Angular Build in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-build -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/igniteui-angular-build, .gemini/skills/igniteui-angular-build, .github/skills/igniteui-angular-build and .opencode/skills/igniteui-angular-build in your project.
What does Igniteui Angular Build need to run?
Going by SKILL.md and its folder, Igniteui Angular Build needs the command-line tools its instructions call (npm and node). Our summary lists: Node.js.
Does Igniteui Angular Build access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Igniteui Angular Build safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Igniteui Angular Build use?
Igniteui Angular Build has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Igniteui Angular Build use?
About 898 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Igniteui Angular Build?
Skills that share tags, products or a category with Igniteui Angular Build: Cometchat Angular V5 Migration (cometchat/cometchat-skills, 129 stars), Stylelint (managedcode/dotnet-skills, 486 stars), Frontend Build Timing Audit (openops-cloud/openops, 1.1k stars) and Sanity Best Practices (robotostudio/turbo-start-sanity, 182 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Igniteui Angular Build?
IgniteUI (a GitHub organization) maintains it in IgniteUI/igniteui-angular, which has 599 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.
Source: IgniteUI/igniteui-angular on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.