Official agent skill

Sap Fiori App Development

Guidelines for SAP Fiori app development for CAP and standalone projects.

OfficialApache-2.0Auto-check passed

Install Sap Fiori App Development

skills CLI

$ npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install SAP/open-ux-tools sap-fiori-app-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-app-development .claude/skills/sap-fiori-app-development && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "sap-fiori-app-development" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-app-development into .claude/skills/sap-fiori-app-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-app-development", 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

$skill-installer install https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-app-development

Type 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.

skills CLI

$ npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install SAP/open-ux-tools sap-fiori-app-development --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-app-development .agents/skills/sap-fiori-app-development && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sap-fiori-app-development" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-app-development into .agents/skills/sap-fiori-app-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-app-development", 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.

skills CLI

$ npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install SAP/open-ux-tools sap-fiori-app-development --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-app-development .cursor/skills/sap-fiori-app-development && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sap-fiori-app-development" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-app-development into .cursor/skills/sap-fiori-app-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-app-development", 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

$ gemini skills install https://github.com/SAP/open-ux-tools.git --path plugins-coding-agents/fiori/skills/sap-fiori-app-development

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install SAP/open-ux-tools sap-fiori-app-development --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-app-development .gemini/skills/sap-fiori-app-development && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "sap-fiori-app-development" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-app-development into .gemini/skills/sap-fiori-app-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-app-development", 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.

GitHub CLI

$ gh skill install SAP/open-ux-tools sap-fiori-app-development

Installs 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).

skills CLI

$ npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-app-development .github/skills/sap-fiori-app-development && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "sap-fiori-app-development" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-app-development into .github/skills/sap-fiori-app-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-app-development", 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.

skills CLI

$ npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install SAP/open-ux-tools sap-fiori-app-development --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-app-development .opencode/skills/sap-fiori-app-development && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sap-fiori-app-development" agent skill from https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori/skills/sap-fiori-app-development into .opencode/skills/sap-fiori-app-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sap-fiori-app-development", 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-app-development
GitHub stars: 158
Token cost: ~1.7k tokens
SKILL.md length: 829 words
Files: 1
Skills in repo: 9
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Guidelines for SAP Fiori app development for CAP and standalone projects.

Works in 6 steps: Always ask the user whether they want to… → Use the Fiori MCP tools to create the… → After the Fiori MCP Server tools execute… → …
Modifying SAP Fiori Elements applications
SKILL.md covers General Guidelines (Applicable…, CAP-Specific Guidelines and Standalone Fiori Project…
Calls npm

What it does

Sap Fiori App Development is an agent skill from SAP/open-ux-tools, published by the product's own GitHub organization. Guidelines for SAP Fiori app development for CAP and standalone projects. Use when creating or modifying SAP Fiori Elements applications, adding a List Report, Object Page, or Worklist, or connecting a Fiori app to a CAP service or OData endpoint.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with SAP and Model Context Protocol. 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

Modifying SAP Fiori Elements applications
Adding a List Report
Connecting a Fiori app to a CAP service

Example prompts

“Use the sap-fiori-app-development skill to guideline for SAP Fiori app development for CAP and standalone projects”
“/sap-fiori-app-development”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Always ask the user whether they want to create a Fiori app for CAP (Cloud Application Programming) or a standalone Fiori project…
Use the Fiori MCP tools to create the Fiori UI using SAP Fiori Elements.
After the Fiori MCP Server tools execute successfully, inform the user of completion. Do not verify or double-check - treat successful…
The data model should be suitable for SAP Fiori elements: at minimum one entity type that serves as the main entity for the application…
Each property of an entity must have a proper datatype.
Before modifying the code directly - first check whether Fiori MCP server provides a suitable function or tool, or if a specialized skill…

What it can do on your machine

Read from SKILL.md and the folder at commit 118fa39. 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:
- npm
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

Sap Fiori App Development loads about 1.7k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 829 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~68
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

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 118fa39, republished under its Apache-2.0 licence (© SAP). 829 words, ~1,678 tokens.

Download SKILL.mdSave it as .claude/skills/sap-fiori-app-development/SKILL.md (or your agent's skills folder).

name: sap-fiori-app-development
description: Guidelines for SAP Fiori app development for CAP and standalone projects. Use when creating or modifying SAP Fiori Elements applications, adding a List Report, Object Page, or Worklist, or connecting a Fiori app to a CAP service or OData endpoint.
argument-hint: fiori elements application creation or modification
metadata.author: sap-fiori-tools
metadata.version: 0.0.3

SAP Fiori App Development Guidelines (CAP & Standalone Projects)

General Guidelines (Applicable to CAP and Standalone Fiori Projects)

Always ask the user whether they want to create a Fiori app for CAP (Cloud Application Programming) or a standalone Fiori project connected to an external OData service before proceeding with implementation, unless the technology stack is explicitly specified in the user's request.
Use the Fiori MCP tools to create the Fiori UI using SAP Fiori Elements.
After the Fiori MCP Server tools execute successfully, inform the user of completion. Do not verify or double-check - treat successful tool execution as confirmation.
The data model should be suitable for SAP Fiori elements: at minimum one entity type that serves as the main entity for the application. Navigation properties to related entities are optional but enable richer UI patterns.
Each property of an entity must have a proper datatype.
Before modifying the code directly - first check whether Fiori MCP server provides a suitable function or tool, or if a specialized skill exists (e.g.sap-fiori-analytical-chart).

Available Application Templates (Both CAP and Standalone Projects)

The Fiori MCP can create the following application templates for both CAP and standalone project backends:

FE_LROP - List Report Object Page (most common, OData V2/V4)
FE_ALP - Analytical List Page (OData V2/V4)
FE_OVP - Overview Page (OData V2/V4)
FE_WORKLIST - Worklist (OData V2/V4)
FE_FEOP - Form Entry Object Page (OData V4 only)
FE_FPM - Flexible Programming Model / Custom Page (OData V4 only)
FF_SIMPLE - Basic SAPUI5 Freestyle template (can work without a data source)

Available Page Types

The Fiori MCP can add the following page types to existing applications:

ListReport - Table view with filtering and search
ObjectPage - Detail page for viewing/editing records
CustomPage - Fully custom page with your own views

Application Structure

When asked to create a SAP Fiori elements app, check whether the user input can be interpreted as an application organized into one or more pages containing table data or forms.
Applications typically start with a List Report page showing data in a table, but other templates are available (see above).
Details of a specific table row are shown in an Object Page based on the base entity.
An Object Page can contain sections based on navigation properties (both to-one (0..1) and to-many associations) of its entity type.
Details of a table section row (for to-many associations) can be shown in another Object Page based on the association's target entity.

Application Preview Guidelines

Use the most specific script for the app in package.json.
For CAP: Use watch scripts (e.g., npm run watch-manage-travel)
For standalone Fiori projects: Use npm start (live backend) or npm run start-mock (mock data)

CAP-Specific Guidelines

The fiori app must be created in the app folder under the CAP application root folder created before with cds init operation. This root folder is always a subfolder directly under working directory.
When creating UI applications following a CAP application summary, make sure to use UI application names as described in the project structure of the summary, unless user explicitly requested otherwise.
On any follow-up request to change or modify the UI of the full stack CAP application, always try first to make the change in the fiori app unless really required in service.
Provide primary keys of type UUID for all entities.
When creating sample data in CSV files, all primary keys and foreign keys MUST be in UUID format (e.g., 550e8400-e29b-41d4-a716-446655440001).

Show full SKILL.md (276 more words)Show less

Standalone Fiori Project Guidelines

For standalone Fiori projects based on external services, the application is created at the root level by Fiori MCP tools.
Destination or SAP System Name: If the user doesn't provide a destination name or SAP system name, use the Fiori MCP Server to retrieve and present available destinations/systems for user selection.
Fetching OData Service Metadata (for initial app creation only): Refer to the tools instructions for downloading OData service metadata. If Service Center MCP is available use that, otherwise use the Fiori MCP Server to download the metadata file. To refresh metadata in an already-created app, see point 8 below.
Annotations should primarily be maintained in the backend service, and only app-specific UI customizations or overrides should be placed in local (frontend) annotations.
Use frontend annotations only for app-specific UI tweaks (e.g., /webapp/annotations/annotation.xml) referenced in manifest.json with matching uri and localUri values:
json
```
"annotation": {
  "type": "ODataAnnotation",
  "uri": "annotations/annotation.xml",
  "settings": {
    "localUri": "annotations/annotation.xml"
  }
}
```
Standalone Fiori projects connect to remote OData V2 or V4 services (defined in manifest.json dataSources).
OData Service Metadata is Read-Only: The service metadata file (/webapp/localService/mainService/metadata.xml) referenced in manifest.json must not be edited locally. Any changes to entity definitions, properties, or service structure must be made at the backend source:
json
```
"dataSources": {
  "mainService": {
    "uri": "/path/to/odata/service/",
    "type": "OData",
    "settings": {
      "annotations": ["annotation"],
      "localUri": "localService/mainService/metadata.xml",
      "odataVersion": "4.0"
    }
  }
}
```
Updating Service Metadata: To refresh the local metadata.xml from the live backend for an existing Fiori app, do not use download_odata_service_metadata (that tool is for initial metadata download during app or page creation, not for refreshing metadata already present in the project). Instead, invoke the sap-fiori-create-cli skill's update service-metadata section.

Files

Just SKILL.md in plugins-coding-agents/fiori/skills/sap-fiori-app-development of SAP/open-ux-tools.

Open the folder on GitHubat commit 118fa39

Compare with similar skills

Sap Fiori App Development 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.

Sap Fiori App Development compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sap Fiori App Development this skillSAP/open-ux-tools	158	—	~1.7k	Automated safety check: Pass	Apache-2.0	yesterday
Sap Dependency Securitysecondsky/sap-skills	462	—	~5.9k	Automated safety check: Warn	GPL-3.0	5 days ago
MCP Server WorkflowsSAP-samples/hana-developer-cli-tool-example	112	—	~310	Automated safety check: Pass	Apache-2.0	3 days ago
Sap Cap Capiresecondsky/sap-skills	462	—	~4.4k	Automated safety check: Pass	GPL-3.0	5 days ago
Sap Fiori Toolssecondsky/sap-skills	462	—	~4.1k	Automated safety check: Pass	GPL-3.0	5 days ago
Sap Hana CLIsecondsky/sap-skills	462	—	~3.1k	Automated safety check: Notes	GPL-3.0	5 days ago

Similar skills

Sap Dependency Security
secondsky/sap-skills
SAP dependency security and MCP executable trust policy with secure upgrades, cooldowns, staged rollout, and supply-chain protection.
462 GitHub stars~5.9k tokensUpdated 5 days ago
Agent WorkflowsAuto-check: warnings
MCP Server Workflows
SAP-samples/hana-developer-cli-tool-example
Create or update MCP server tools, JSON-RPC handlers, and registrations.
112 GitHub stars~310 tokensUpdated 3 days ago
Agent WorkflowsAuto-check passed
Sap Cap Capire
secondsky/sap-skills
SAP Cloud Application Programming Model (CAP) development skill using Capire documentation.
462 GitHub stars~4.4k tokensUpdated 5 days ago
DatabasesAuto-check passed
Sap Fiori Tools
secondsky/sap-skills
Develops SAP Fiori applications using SAP Fiori tools extensions for VS Code and SAP Business Application Studio.
462 GitHub stars~4.1k tokensUpdated 5 days ago
Agent WorkflowsAuto-check passed
Sap Hana CLI
secondsky/sap-skills
Assists with SAP HANA Developer CLI (hana-cli) for database development and administration.
462 GitHub stars~3.1k tokensUpdated 5 days ago
DatabasesAuto-check: notes
Sapui5
secondsky/sap-skills
This skill should be used when developing SAP UI5 applications, including creating freestyle apps, Fiori Elements apps, custom controls, testing, data binding, OData integration, routing, and…
462 GitHub stars~4.1k tokensUpdated 5 days ago
Testing & QAAuto-check passed

More from SAP/open-ux-tools

All 9 skills in this repo

Eslint Rule Development
SAP/open-ux-tools
Official
Develop a new ESLint rule for @sap-ux/eslint-plugin-fiori-tools.
158 GitHub stars~3k tokensUpdated yesterday
Auto-check passed
Sap Fiori Opa5 Test Development
SAP/open-ux-tools
Official
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…
158 GitHub stars~3.6k tokensUpdated yesterday
Auto-check passed
Odata Vocabularies Sync
SAP/open-ux-tools
Official
Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL.
158 GitHub stars~1.5k tokensUpdated yesterday
Auto-check passed
Sap Fiori Add Visual Filter
SAP/open-ux-tools
Official
Add visual filters (chart-based) to SAP Fiori Elements filter bar or value help using CAP or ABAP RAP.
158 GitHub stars~3k tokensUpdated yesterday
Auto-check passed
Sap Fiori Analytical Chart
SAP/open-ux-tools
Official
Add analytical chart (chart + table hybrid) to SAP Fiori Elements List Report using aggregated data.
158 GitHub stars~3.5k tokensUpdated yesterday
Auto-check passed
Sap Fiori Eslint Plugin
SAP/open-ux-tools
Official
Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP).
158 GitHub stars~640 tokensUpdated yesterday
Auto-check passed

Works with

Questions about Sap Fiori App Development

What does Sap Fiori App Development do?

Guidelines for SAP Fiori app development for CAP and standalone projects. Sap Fiori App Development is an agent skill from SAP/open-ux-tools, published by the product's own GitHub organization. Guidelines for SAP Fiori app development for CAP and standalone projects.

When should I use Sap Fiori App Development?

Sap Fiori App Development fits situations like: modifying SAP Fiori Elements applications; adding a List Report; connecting a Fiori app to a CAP service.

How do I install Sap Fiori App Development in Claude Code?

Run `npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a claude-code`. Or copy the skill folder (plugins-coding-agents/fiori/skills/sap-fiori-app-development in SAP/open-ux-tools) into .claude/skills/sap-fiori-app-development in your project. Claude Code loads it when a task matches its description.

How do I install Sap Fiori App Development in Codex?

Run `npx skills add SAP/open-ux-tools --skill sap-fiori-app-development -a codex`. Or copy the skill folder (plugins-coding-agents/fiori/skills/sap-fiori-app-development in SAP/open-ux-tools) into .agents/skills/sap-fiori-app-development in your project. Codex loads it when a task matches its description.

Can I use Sap Fiori App Development 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-app-development -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-app-development, .gemini/skills/sap-fiori-app-development, .github/skills/sap-fiori-app-development and .opencode/skills/sap-fiori-app-development in your project.

What does Sap Fiori App Development need to run?

Going by SKILL.md and its folder, Sap Fiori App Development needs the command-line tools its instructions call (npm).

Does Sap Fiori App Development 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 Sap Fiori App Development 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 App Development use?

Sap Fiori App Development 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 App Development use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 Sap Fiori App Development?

Skills that share tags, products or a category with Sap Fiori App Development: Sap Dependency Security (secondsky/sap-skills, 462 stars), MCP Server Workflows (SAP-samples/hana-developer-cli-tool-example, 112 stars), Sap Cap Capire (secondsky/sap-skills, 462 stars) and Sap Fiori Tools (secondsky/sap-skills, 462 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sap Fiori App Development?

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 9, 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.

Install Sap Fiori App Development

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SAP Fiori App Development Guidelines (CAP & Standalone Projects)

General Guidelines (Applicable to CAP and Standalone Fiori Projects)

Available Application Templates (Both CAP and Standalone Projects)

Available Page Types

Application Structure

Application Preview Guidelines

CAP-Specific Guidelines

Standalone Fiori Project Guidelines

Files

Compare with similar skills

Similar skills

More from SAP/open-ux-tools

Related

Questions about Sap Fiori App Development