Context Mode Ops
mksglu/context-mode
Runs maintenance for the context-mode project with parallel subagents: issue triage, PR review, releases, bug fixes, announcements and branch syncing.
Provides rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the…
Install Skill Authoring
$ npx skills add IgniteUI/igniteui-webcomponents --skill skill-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents skill-authoring --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-webcomponents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/skill-authoring .claude/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/.agents/skills/skill-authoring into .claude/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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-webcomponents/tree/master/.agents/skills/skill-authoringType 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-webcomponents --skill skill-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents skill-authoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/skill-authoring .agents/skills/skill-authoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-authoring" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/.agents/skills/skill-authoring into .agents/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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-webcomponents --skill skill-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents skill-authoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/skill-authoring .cursor/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/.agents/skills/skill-authoring into .cursor/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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-webcomponents.git --path .agents/skills/skill-authoring--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-webcomponents --skill skill-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents skill-authoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/skill-authoring .gemini/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/.agents/skills/skill-authoring into .gemini/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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-webcomponents skill-authoringInstalls 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-webcomponents --skill skill-authoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/skill-authoring .github/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/.agents/skills/skill-authoring into .github/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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-webcomponents --skill skill-authoring -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-webcomponents skill-authoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/skill-authoring .opencode/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/.agents/skills/skill-authoring into .opencode/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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
skill-authoring- GitHub stars
- 170
- Token cost
- ~789 tokens
- SKILL.md length
- 305 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Provides rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the…
- Works in 4 steps: Frontmatter passes the rules above. → The description includes WHEN TO USE:… → The body is under 500 lines, and every… → …
- Tasks that involve Skill authoring
- SKILL.md covers Location, Frontmatter, Token Budget and Checklist, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill Authoring is an agent skill from IgniteUI/igniteui-webcomponents. Provides rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the 500-line body budget with progressive disclosure into reference files. WHEN TO USE: creating a new skill under .agents/skills/ or skills/, or editing an existing skill's frontmatter, scope, or length. WHEN NOT TO USE: writing component code, styles, or tests (use create-new-component, add-component-property, or…
Its SKILL.md is about 790 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 Agent Workflows, covering Skill authoring and Pull requests. It works with GitHub. The repository describes itself as: Ignite UI for Web Components is a complete library of UI components, giving you the ability to build modern web applications using encapsulation and the concept of reusable… The licence is MIT.
When your agent uses it
- Tasks that involve Skill authoring
- Tasks that involve Pull requests
Example prompts
- “Use the skill-authoring skill to provide rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and…”
- “/skill-authoring”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Frontmatter passes the rules above.
- The description includes WHEN TO USE: and WHEN NOT TO USE:.
- The body is under 500 lines, and every reference file is linked from SKILL.md.
- The skill is listed in the Skills table of its README: .agents/skills/README.md for internal skills, skills/README.md for public skills…
What it can do on your machine
Read from SKILL.md and the folder at commit ab2cd1d. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Skill Authoring loads about 789 tokens when it runs. Until then it costs about 171 tokens; SKILL.md has 305 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
The full file from IgniteUI/igniteui-webcomponents at commit ab2cd1d, republished under its MIT licence (© IgniteUI). 305 words, ~789 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-authoring/SKILL.md (or your agent's skills folder).- name
- skill-authoring
- description
- Provides rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the 500-line body budget with progressive disclosure into reference files. WHEN TO USE: creating a new skill under .agents/skills/ or skills/, or editing an existing skill's frontmatter, scope, or length. WHEN NOT TO USE: writing component code, styles, or tests (use create-new-component, add-component-property, or update-component-styles), reviewing a component pull request (use review-component-pr), or changing the coding rules themselves (edit .github/CODING_GUIDELINES.md).
- license
- MIT
- user-invocable
- true
Ignite UI for Web Components — Skill Authoring
Quick-reference for writing a SKILL.md that agents can discover and load reliably.
Location
- Internal, contributor-facing skills:
.agents/skills/<name>/SKILL.md - Public skills that ship with the package:
skills/<name>/SKILL.md - The folder name must match the
namefield.
Frontmatter
| Field | Rules |
|---|---|
license | Required. Must specify the license under which the skill is released. Default is MIT. |
name | Required. Max 64 characters. Lowercase letters, numbers, and hyphens only. No XML tags. No reserved words (anthropic, claude). Public skills use the igniteui-wc- prefix; internal skills use a plain kebab-case name. |
description | Required. Non-empty. Max 1,024 characters. No XML tags. |
Write the description in the third person: say what the skill covers, then add both markers:
WHEN TO USE:the tasks or triggers that should load the skill.WHEN NOT TO USE:nearby tasks it does not cover, naming the skill to use instead.
Agents see only name and description until they load the skill, so the description decides whether it is ever used.
Token Budget
- Keep the
SKILL.mdbody under 500 lines. - If it grows past that, use progressive disclosure: keep the overview and core rules in
SKILL.mdand move detail intoreferences/<topic>.mdfiles. - Link each reference file directly from
SKILL.md(one level deep) and say when to read it, so agents load it only when needed.
Checklist
- Frontmatter passes the rules above.
- The description includes
WHEN TO USE:andWHEN NOT TO USE:. - The body is under 500 lines, and every reference file is linked from
SKILL.md. - The skill is listed in the Skills table of its README: .agents/skills/README.md for internal skills, skills/README.md for public skills. Internal skills are also listed in the Workflow section of .agents/context/project.md.
Related Skills
create-new-component— Scaffolding a new componentadd-component-property— Adding a reactive propertyupdate-component-styles— Changing SCSS or themesreview-component-pr— Reviewing a component pull request
© IgniteUI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/skill-authoring of IgniteUI/igniteui-webcomponents.
Open the folder on GitHubat commit ab2cd1d
Compare with similar skills
Skill Authoring 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 |
|---|---|---|---|---|---|---|
| Skill Authoring this skillIgniteUI/igniteui-webcomponents | 170 | — | ~789 | Automated safety check: Pass | MIT | |
| Context Mode Opsmksglu/context-mode | 26k | — | ~6k | Automated safety check: Pass | Custom licence | |
| LubanLearnPrompt/luban-skill | 957 | — | ~3.1k | Automated safety check: Pass | MIT | |
| PRP LoopWirasm/prp | 2.3k | — | ~894 | Automated safety check: Pass | MIT | |
| Open PRArcadeAI/arcade-mcp | 1k | — | ~2.9k | Automated safety check: Pass | MIT | |
| PRP Workstream OrchestratorWirasm/prp | 2.3k | — | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
Luban
LearnPrompt/luban-skill
鲁班（Luban）——Skill打磨工坊。把一个"能用的Skill"打磨成"能被理解、能被安装、能被传播、能被验证、能持续进化"的公共Skill资产。
PRP Loop
Wirasm/prp
Runs the plan, implement and review pipeline detached in fresh headless sessions, looping review and fix until the pull request is clean.
Open PR
ArcadeAI/arcade-mcp
Prepare arcade-mcp changes for review by verifying intended behavior, filling the repository PR template, and creating or updating the PR.
PRP Workstream Orchestrator
Wirasm/prp
Coordinates several PRP workstreams in isolated Git worktrees from one session, verifying proof, holding merge gates and sequencing the merges.
Codex Issue Coordinator
owainlewis/blueprint
Lets one Codex thread run a batch of GitHub issues through separate worker threads, each with its own worktree, branch, tested pull request and gated merge.
More from IgniteUI/igniteui-webcomponents
All 13 skills in this repoIgniteui Wc Customize Component Theme
IgniteUI/igniteui-webcomponents
Theme and style Ignite UI Web Components (and igniteui-react) apps using CSS custom properties, optional Sass, and the igniteui-theming MCP server.
Igniteui Wc Generate From Image Design
IgniteUI/igniteui-webcomponents
Implement application views from design images (screenshots, mockups, wireframes) using Ignite UI Web Components, with the igniteui-cli and igniteui-theming MCP servers for component discovery…
Igniteui Wc Integrate With Framework
IgniteUI/igniteui-webcomponents
Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package…
Add Component Property
IgniteUI/igniteui-webcomponents
Add a reactive property to an existing Lit web component with proper decorators, types, tests, specification updates, and documentation
Create New Component
IgniteUI/igniteui-webcomponents
Create a new Lit web component following project conventions, including specification, component class, styles, tests, Storybook story, and exports
Igniteui Wc Choose Components
IgniteUI/igniteui-webcomponents
Identify the right Ignite UI Web Components (igniteui-webcomponents, grids, charts, dock manager, React wrappers) for a UI requirement and point to official docs, examples, and API references.
Related
Works with
Categories
Questions about Skill Authoring
What does Skill Authoring do?
Provides rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the…. Skill Authoring is an agent skill from IgniteUI/igniteui-webcomponents.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the 500-line body budget with progressive disclosure into reference files.
When should I use Skill Authoring?
Skill Authoring fits situations like: tasks that involve Skill authoring; tasks that involve Pull requests.
How do I install Skill Authoring in Claude Code?
Run `npx skills add IgniteUI/igniteui-webcomponents --skill skill-authoring -a claude-code`. Or copy the skill folder (.agents/skills/skill-authoring in IgniteUI/igniteui-webcomponents) into .claude/skills/skill-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Skill Authoring in Codex?
Run `npx skills add IgniteUI/igniteui-webcomponents --skill skill-authoring -a codex`. Or copy the skill folder (.agents/skills/skill-authoring in IgniteUI/igniteui-webcomponents) into .agents/skills/skill-authoring in your project. Codex loads it when a task matches its description.
Can I use Skill Authoring 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-webcomponents --skill skill-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-authoring, .gemini/skills/skill-authoring, .github/skills/skill-authoring and .opencode/skills/skill-authoring in your project.
What does Skill Authoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Authoring is instructions for the agent only.
Does Skill Authoring access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skill Authoring 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 Skill Authoring use?
Skill Authoring is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Authoring use?
About 789 tokens (SKILL.md is roughly 3.2k 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 Skill Authoring?
Skills that share tags, products or a category with Skill Authoring: Context Mode Ops (mksglu/context-mode, 26k stars), Luban (LearnPrompt/luban-skill, 957 stars), PRP Loop (Wirasm/prp, 2.3k stars) and Open PR (ArcadeAI/arcade-mcp, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Authoring?
IgniteUI (a GitHub organization) maintains it in IgniteUI/igniteui-webcomponents, which has 170 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.
Source: IgniteUI/igniteui-webcomponents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.