LobeHub Alint Rule Set Maintenance
lobehub/lobehub
Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.
Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP).
Install Sap Fiori Eslint Plugin
$ npx skills add SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SAP/open-ux-tools sap-fiori-eslint-plugin --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/SAP/open-ux-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin .claude/skills/sap-fiori-eslint-plugin && 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 "sap-fiori-eslint-plugin" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin into .claude/skills/sap-fiori-eslint-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-eslint-plugin", 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/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-eslint-pluginType 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 SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SAP/open-ux-tools sap-fiori-eslint-plugin --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP/open-ux-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin .agents/skills/sap-fiori-eslint-plugin && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sap-fiori-eslint-plugin" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin into .agents/skills/sap-fiori-eslint-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-eslint-plugin", 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 SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SAP/open-ux-tools sap-fiori-eslint-plugin --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP/open-ux-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin .cursor/skills/sap-fiori-eslint-plugin && 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 "sap-fiori-eslint-plugin" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin into .cursor/skills/sap-fiori-eslint-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-eslint-plugin", 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/SAP/open-ux-tools.git --path plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin--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 SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SAP/open-ux-tools sap-fiori-eslint-plugin --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP/open-ux-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin .gemini/skills/sap-fiori-eslint-plugin && 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 "sap-fiori-eslint-plugin" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin into .gemini/skills/sap-fiori-eslint-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-eslint-plugin", 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 SAP/open-ux-tools sap-fiori-eslint-pluginInstalls 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 SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SAP/open-ux-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin .github/skills/sap-fiori-eslint-plugin && 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 "sap-fiori-eslint-plugin" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin into .github/skills/sap-fiori-eslint-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-eslint-plugin", 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 SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SAP/open-ux-tools sap-fiori-eslint-plugin --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP/open-ux-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin .opencode/skills/sap-fiori-eslint-plugin && 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 "sap-fiori-eslint-plugin" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin into .opencode/skills/sap-fiori-eslint-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-eslint-plugin", 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
sap-fiori-eslint-plugin- GitHub stars
- 158
- Token cost
- ~640 tokens
- SKILL.md length
- 154 words
- Files
- 4 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP).
- ESLint is missing and the user wants to add it
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Add code quality checks
- An existing .eslintrc
What it does
Sap Fiori Eslint Plugin is an agent skill from SAP/open-ux-tools, published by the product's own GitHub organization. Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP). Use when ESLint is missing and the user wants to add it or add code quality checks; when an existing .eslintrc or eslint@8 config needs upgrading to ESLint 9 flat config; when the user wants to run linting, fix lint errors, or ESLint is broken or not working; or when the user wants to see the application issues or UX consistency issues for a specific app — e.g. "show application issue(s) for my…
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/lint.md`, `references/migrate.md` and `references/setup.md`). Compatibility notes: Requires Node.js with npm, pnpm, or yarn. Designed for SAP Fiori freestyle and Fiori elements projects (standalone or inside a CAP project).
It sits in Development, covering Linting and formatting. It works with ESLint and SAP. The repository describes itself as: Enable community collaboration to jointly promote and facilitate best in class tooling capabilities. The licence is Apache-2.0.
When your agent uses it
- ESLint is missing and the user wants to add it
- Add code quality checks
- An existing .eslintrc
- Eslint@8 config needs upgrading to ESLint 9 flat config
Example prompts
- “show application issue(s) for my project <projectname”
- “show application issues for app X”
- “UX consistency issues”
- “/sap-fiori-eslint-plugin”
Requirements
- Node.js
- Compatibility (from SKILL.md): Requires Node.js with npm, pnpm, or yarn. Designed for SAP Fiori freestyle and Fiori elements projects (standalone or inside a CAP project).
What it can do on your machine
Read from SKILL.md and the folder at commit ddeddbe. 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 (its code samples are bash).
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.
Compatibility
Requires Node.js with npm, pnpm, or yarn. Designed for SAP Fiori freestyle and Fiori elements projects (standalone or inside a CAP project).
From compatibility in the SKILL.md frontmatter.
Context cost
Sap Fiori Eslint Plugin loads about 640 tokens when it runs, and up to ~7.7k if it reads all its reference files. Until then it costs about 175 tokens; SKILL.md has 154 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 SAP/open-ux-tools at commit ddeddbe, republished under its Apache-2.0 licence (© SAP). 154 words, ~640 tokens.
Download SKILL.mdSave it as
.claude/skills/sap-fiori-eslint-plugin/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- sap-fiori-eslint-plugin
- description
- Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP). Use when ESLint is missing and the user wants to add it or add code quality checks; when an existing .eslintrc or eslint@8 config needs upgrading to ESLint 9 flat config; when the user wants to run linting, fix lint errors, or ESLint is broken or not working; or when the user wants to see the application issues or UX consistency issues for a specific app — e.g. "show application issue(s) for my project <project_name>", "show application issues for app X", "UX consistency issues", "issues consistent with Page Map", "same issues as Application Information".
- compatibility
- Requires Node.js with npm, pnpm, or yarn. Designed for SAP Fiori freestyle and Fiori elements projects (standalone or inside a CAP project).
- metadata.author
- sap-fiori-tools
- metadata.version
- 0.0.2
SAP Fiori ESLint Plugin
Work with @sap-ux/eslint-plugin-fiori-tools on SAP Fiori projects: set up ESLint from scratch, migrate from a legacy configuration, or run and fix lint issues.
Determine which task to perform
Identify the user's intent from their request:
| User says / situation | Task | Reference |
|---|---|---|
"Set up ESLint", "Add ESLint", no eslint.config.mjs exists | Set up | references/setup.md |
"Migrate ESLint", .eslintrc / eslint@8 present, upgrade ESLint | Migrate | references/migrate.md |
"Run ESLint", "Check my code", "Fix lint errors", eslint.config.mjs exists | Lint | references/lint.md |
| "Show all application issues", "show UX consistency issues", "issues for app X", "same issues as Page Map/App Info" | App issues only | references/lint.md — follow the App-scope mode section |
If the intent is unclear, check the project state:
# Check for existing ESLint config (any format)
ls eslint.config.mjs eslint.config.js .eslintrc .eslintrc.js .eslintrc.cjs .eslintrc.json .eslintrc.yml .eslintrc.yaml 2>/dev/null- No config found → follow references/setup.md
- Legacy config found (
.eslintrc*) → follow references/migrate.md - Flat config found (
eslint.config.mjs) → follow references/lint.md
If the intent is still unclear, ask the user to clarify whether they want to set up ESLint, migrate an existing config, or run linting.
© SAP, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin of SAP/open-ux-tools.
- SKILL.md
- references/lint.md
- references/migrate.md
- references/setup.md
Open the folder on GitHubat commit ddeddbe
Compare with similar skills
Sap Fiori Eslint Plugin 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 |
|---|---|---|---|---|---|---|
| Sap Fiori Eslint Plugin this skillSAP/open-ux-tools | 158 | — | ~640 | Automated safety check: Pass | Apache-2.0 | |
| LobeHub Alint Rule Set Maintenancelobehub/lobehub | 83k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Eslint Migrate Optionsbiomejs/biome | 26k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Ultraciteagustinusnathaniel/nextarter-tailwind | 125 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Qualityredis/RedisInsight | 8.9k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Boundaries Architectjavierbrea/eslint-plugin-boundaries | 997 | — | ~4.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Eslint Migrate Options
biomejs/biome
A skill your agent uses when biome migrate eslint must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures.
Ultracite
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
- Official
Code Quality
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
Boundaries Architect
javierbrea/eslint-plugin-boundaries
Act as a software architect: analyze a repository's folder structure and cross-file import dependencies, detect its architectural pattern, design element/file boundaries with the user, and configure…
Port Rule
web-infra-dev/rslint
Port a new ESLint core or plugin rule to rslint, including explicitly requested batches.
More from SAP/open-ux-tools
All 9 skills in this repo- Official
Eslint Rule Development
SAP/open-ux-tools
Develop a new ESLint rule for @sap-ux/eslint-plugin-fiori-tools.
- Official
Sap Fiori Opa5 Test Development
SAP/open-ux-tools
A skill your agent uses when writing, fixing, extending, or reviewing OPA5 integration tests for SAP Fiori Elements applications - whether the app uses OData V4 (sap.fe.test library) or OData V2…
- Official
Odata Vocabularies Sync
SAP/open-ux-tools
Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL.
- Official
Sap Fiori Add Visual Filter
SAP/open-ux-tools
Add visual filters (chart-based) to SAP Fiori Elements filter bar or value help using CAP or ABAP RAP.
- Official
Sap Fiori Analytical Chart
SAP/open-ux-tools
Add analytical chart (chart + table hybrid) to SAP Fiori Elements List Report using aggregated data.
- Official
Sap Fiori App Development
SAP/open-ux-tools
Guidelines for SAP Fiori app development for CAP and standalone projects.
Related
Categories
Questions about Sap Fiori Eslint Plugin
What does Sap Fiori Eslint Plugin do?
Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP). Sap Fiori Eslint Plugin is an agent skill from SAP/open-ux-tools, published by the product's own GitHub organization. Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP).
When should I use Sap Fiori Eslint Plugin?
Sap Fiori Eslint Plugin fits situations like: ESLint is missing and the user wants to add it; add code quality checks; an existing .eslintrc; eslint@8 config needs upgrading to ESLint 9 flat config.
How do I install Sap Fiori Eslint Plugin in Claude Code?
Run `npx skills add SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a claude-code`. Or copy the skill folder (plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin in SAP/open-ux-tools) into .claude/skills/sap-fiori-eslint-plugin in your project. Claude Code loads it when a task matches its description.
How do I install Sap Fiori Eslint Plugin in Codex?
Run `npx skills add SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a codex`. Or copy the skill folder (plugins-coding-agents/fiori/skills/sap-fiori-eslint-plugin in SAP/open-ux-tools) into .agents/skills/sap-fiori-eslint-plugin in your project. Codex loads it when a task matches its description.
Can I use Sap Fiori Eslint Plugin 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 SAP/open-ux-tools --skill sap-fiori-eslint-plugin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sap-fiori-eslint-plugin, .gemini/skills/sap-fiori-eslint-plugin, .github/skills/sap-fiori-eslint-plugin and .opencode/skills/sap-fiori-eslint-plugin in your project.
What does Sap Fiori Eslint Plugin need to run?
SKILL.md names no scripts, command-line tools or credentials: Sap Fiori Eslint Plugin is instructions for the agent only. Our summary lists: Node.js. Compatibility (from SKILL.md): Requires Node.js with npm, pnpm, or yarn. Designed for SAP Fiori freestyle and Fiori elements projects (standalone or inside a CAP project)..
Does Sap Fiori Eslint Plugin 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 Sap Fiori Eslint Plugin 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 Sap Fiori Eslint Plugin use?
Sap Fiori Eslint Plugin is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sap Fiori Eslint Plugin use?
About 640 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7k tokens, read only when the agent opens those files.
What are the alternatives to Sap Fiori Eslint Plugin?
Skills that share tags, products or a category with Sap Fiori Eslint Plugin: LobeHub Alint Rule Set Maintenance (lobehub/lobehub, 83k stars), Eslint Migrate Options (biomejs/biome, 26k stars), Ultracite (agustinusnathaniel/nextarter-tailwind, 125 stars) and Code Quality (redis/RedisInsight, 8.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sap Fiori Eslint Plugin?
SAP (a GitHub organization, an official publisher) maintains it in SAP/open-ux-tools, which has 158 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.
Source: SAP/open-ux-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.