The CF command line logged in and targeted at an org and space before deploying, which the requirements state The MultiApps Build Tool for building the MTA and the CF multiapps plugin for cf deploy, both named in the requirements A subaccount with the Application Frontend service entitlement and the Cloud Foundry environment enabled
SAP-samples/html5-applications-migration-skills-for-sap-btp
A Claude Code plugin with migrate, validate and cleanup skills that move an HTML5 app from SAP Neo, html5-apps-repo or a standalone approuter to the SAP BTP Application Frontend (appFront) service.
Migrating to appFront means rewriting mta.yaml, xs-app.json and xs-security.json by hand and getting the routing, auth-service and business-solution grouping right; the migrate skill reads the source project's own files (or, for Neo, neo-app.json and neo-mta.yaml), presents a migration plan, and only writes into a separate appfront-migrated/ folder after approval, leaving the source untouched. Several related Neo apps can be migrated together into one business solution sharing a single XSUAA instance and app-front instance. The validate skill checks a migrated project's configuration and produces a PASS/WARN/FAIL report, optionally against the live deployed app, and cleanup undeploys and removes the local output. It runs entirely on local files through Claude Code's own Read, Glob, Grep, Write, Edit and Bash tools, with a sub-agent reviewing each migration; no MCP server or network access is required. What reaches Cloud Foundry comes from the tools the requirements name beside the plugin: the MultiApps Build Tool for building the MTA, the CF command line logged in and targeted at an org and space, the CF multiapps plugin for cf deploy, and, optionally, the appFront command line, which is what fetches the runtime URL after a deployment.
Facts
Where it sits
Who is behind it
In the atlas: maintains 222@SAP-samplesmaintainerAmin TehauchaContributes to this
In the atlas: contributes to 1@charphobSergio RozenszajnContributes to this
In the atlas: contributes to 1@sergioRozenszajn2 contributors
What it declares
Every artifact
- Type
- Skill
- Origin
- By SAP
As a skill
- Distributed through
- does not say
For agent guidance
- Installs into
- Claude Code
- Topics
- Application Frontend service
Tasks this contributes to
Change a BTP service from an agent sessionA developer working with an agent wants the change made in their own BTP account or service, a Command deployed, an agent pushed, a deployment created, rather than a command to copy out and run themselves.
Connections
Packaged knowledge that teaches a coding agent a framework
Download
README
quoted from SAP-samples/html5-applications-migration-skills-for-sap-btp under Apache-2.0, readAI Skills for HTML5 Applications Migration to Application Frontend Service
Claude Code plugin providing AI-assisted skills for SAP BTP Application Frontend (appFront) service: migrate existing HTML5 apps from Neo or html5-apps-repo, and validate appFront configurations.
Table of Contents
- Skills Overview
- What is appFront?
- Options Matrix
- Requirements
- Download and Installation
- Usage
- Reference Material
- Architecture
- Skill Behavior Summary
- Known Issues
- How to obtain support
- Contributing
- Changelog
- Related Resources
- License
Skills Overview
| Skill | How to invoke | Description |
|---|---|---|
migrate | /appfront:migrate [neo|html5-repo|standalone-approuter] [cf|kyma] [xsuaa|ias] | Migrates an existing HTML5 app from SAP Neo, html5-apps-repo, or a standalone approuter (localDir) to appFront. Produces updated mta.yaml, xs-app.json, and xs-security.json. |
validate | /appfront:validate [path] | Checks appFront configuration for correctness and deployment readiness. Produces a PASS/WARN/FAIL report for local files; optionally validates the live deployed app via browser. |
cleanup | /appfront:cleanup | Undeploys a deployed appFront app from Cloud Foundry (optionally deleting service instances and keys) and removes the local output folder. Works for migrated apps (appfront-migrated/). |
What is appFront?
SAP Application Frontend (appFront) is an SAP BTP service that provides a simpler deployment model for HTML5 applications compared to the older html5-apps-repo (HTML5 Application Repository) service. It eliminates the need for:
- A
destination-contentMTA module - The
HTML5Runtime_enabled: trueflag on the destination service
This plugin helps teams migrate to appFront and stay productive during development.
Options Matrix
Migration Paths (/appfront:migrate)
Supported Migration Paths
| Source | Target Runtime | Auth Service | Status |
|---|---|---|---|
| SAP Neo HTML5 App | Cloud Foundry | XSUAA | ✅ Fully documented |
| SAP Neo HTML5 App | Cloud Foundry | IAS | ✅ Fully documented |
| html5-apps-repo (managed approuter) | Cloud Foundry | XSUAA | ⚠️ Skill logic present — populate references/migration-guides/html5-repo-to-appfront.md for best results |
| html5-apps-repo (managed approuter) | Cloud Foundry | IAS | ⚠️ Skill logic present — populate references/migration-guides/html5-repo-to-appfront.md for best results |
| html5-apps-repo (managed approuter) | Kyma | XSUAA | ⚠️ Skill logic present — populate references/migration-guides/html5-repo-to-appfront.md for best results |
| html5-apps-repo (WorkZone managed approuter) | Cloud Foundry | XSUAA | ⚠️ Skill logic present — CDM steps required; populate references/troubleshooting/workzone-integration.md |
| Standalone approuter (localDir routes) | Cloud Foundry | XSUAA | ⚠️ Skill logic present — populate references/migration-guides/standalone-approuter-to-appfront.md for best results |
Requirements
- Claude Code CLI — Install Claude Code
- SAP BTP subaccount with Application Frontend service entitlement and Cloud Foundry environment enabled (org and space created)
- MBT (SAP MultiApps Build Tool) —
npm install -g mbt— for building MTAs after migration - CF CLI — logged in (
cf login) and targeted (cf target -o <org> -s <space>) before deploying - CF MultiApps plugin —
cf install-plugin multiapps— required forcf deploy - Optional:
afctl(appFront CLI) — for deploying, listing, and managing appFront applications; required for fetching the runtime URL after deployment
Download and Installation
Claude Code
claude plugin install appfront --marketplace https://github.com/SAP-samples/html5-applications-migration-skills-for-sap-btp.git
After installation, restart Claude Code, then type / and look for appfront:migrate, appfront:validate, and appfront:cleanup in the listed skills.
To update to the latest version:
claude plugin update appfront
Other agents
The skills in this repository follow the agentskills.io open standard and can be used with any compatible agent by copying the skill directory to your agent's skills location.
# Clone the repo
git clone https://github.com/SAP-samples/html5-applications-migration-skills-for-sap-btp.git
# Copy all three skills to your agent's skills directory
cp -r html5-applications-migration-skills-for-sap-btp/skills/migrate ~/.agents/skills/
cp -r html5-applications-migration-skills-for-sap-btp/skills/validate ~/.agents/skills/
cp -r html5-applications-migration-skills-for-sap-btp/skills/cleanup ~/.agents/skills/
Example — GitHub Copilot:
cp -r html5-applications-migration-skills-for-sap-btp/skills/migrate .github/skills/
cp -r html5-applications-migration-skills-for-sap-btp/skills/validate .github/skills/
cp -r html5-applications-migration-skills-for-sap-btp/skills/cleanup .github/skills/
Usage
Migrating an app
Navigate to your project directory in Claude Code, then:
/appfront:migrate html5-repo cf xsuaa
Or:
/appfront:migrate standalone-approuter cf xsuaa
Or with natural language (after the skill is loaded):
Migrate this html5-repo app to appFront on Cloud Foundry using XSUAA
What happens:
- Claude detects the source type (html5-repo, standalone-approuter, or Neo) and asks blocking questions one at a time to confirm source, target, and auth service
- Claude reads your project files:
- html5-repo / standalone-approuter:
mta.yaml,xs-app.json,xs-security.json - Neo:
neo-app.json(routes, securityConstraints, welcomeFile),neo-mta.yaml, andwebapp/manifest.json
- html5-repo / standalone-approuter:
- Claude presents a migration plan — no files are changed until you approve
- After your approval, Claude writes changes to
appfront-migrated/(the source project is never touched) - A critic sub-agent reviews the migration for common errors
- Claude produces a migration report with deployment commands and optionally builds and deploys
Neo specifics: The skill reads neo-app.json to extract routes (destinations, SAPUI5 service, User API), securityConstraints (mapped to XSUAA scopes), welcomeFile, and optional cacheControl/responseHeaders/logoutPage settings. It creates a fresh mta.yaml, xs-app.json, and xs-security.json from scratch — the Neo files (neo-app.json, neo-mta.yaml) are deleted from the output folder.
sap.cloud.service and the business solution concept: Neo has no equivalent to sap.cloud.service. When migrating to appFront, this value defines a business solution — a logical grouping of one or more HTML5 apps that share a single XSUAA instance, a single app-front service instance, and a single MTA. The skill will ask you to define this value and explain your intent. See the Mass Migration section below for consolidating multiple Neo apps.
Mass Migration
If you have several related Neo HTML5 apps (e.g. belonging to the same product or team), you can migrate them together into one appFront business solution. This produces a single mta.yaml with shared infrastructure (one app-front instance, one XSUAA instance) and one deployment.
To trigger mass migration, invoke the skill and answer "Yes" when asked whether you want to group multiple apps:
/appfront:migrate neo cf xsuaa
When the skill asks about sap.cloud.service, choose option 2 (mass migration) and provide the list of Neo app directories to include. The skill will:
- Read
neo-app.jsonandmanifest.jsonfrom each app directory - Merge all
securityConstraintsinto a singlexs-security.json - Create one
html5source module per app inmta.yaml - Wire all app zips into a single deployer module
- Set the same
sap.cloud.servicevalue in every app'smanifest.json
Example: migrating three Neo apps app-leave, app-payslip, app-orgchart into one business solution com.sap.hr:
appfront-migrated/
├── mta.yaml ← one MTA, three html5 modules
├── xs-security.json ← merged scopes from all three apps
├── hr-leave/webapp/...
├── hr-payslip/webapp/...
└── hr-orgchart/webapp/...
Standalone approuter specifics: If your source uses approuter.nodejs with localDir routes, the skill replaces the approuter module with an appFront deployer module, converts localDir routes to "service": "app-front", and converts group: destinations to config.destinations.
WorkZone integration: If your source app uses sap.cloud.service in the destination-content module, the skill will flag the required CDM steps and wait for your acknowledgment before proceeding.
Validating an app
Navigate to your appFront project directory:
/appfront:validate
Or point to a specific project:
/appfront:validate ./my-appfront-project
Output: A structured PASS / WARN / FAIL report covering:
mta.yamlstructure (appFront resource, deployer module, residual html5-repo artifacts)xs-app.jsonrouting (appFront service routes, authentication consistency)xs-security.jsonorias-security.json(scopes, role templates, oauth2-configuration)manifest.json(app ID, dataSource URIs, Fiori Elements dependencies)
After static validation, the skill can optionally validate the live deployed app by fetching runtime files via browser (requires a deployed app and browser access).
Reference Material
The skills/appfront-migrate/references/ directory contains reference guides that Claude loads during migration. Populate these files with your team's specific guidance to get more accurate and landscape-specific results.
Priority files to populate
| File | Impact | What to add |
|---|---|---|
skills/appfront-migrate/references/migration-guides/html5-repo-to-appfront.md | High | Your team's step-by-step migration guide |
skills/appfront-migrate/references/migration-guides/neo-to-appfront.md | High | Neo-specific migration steps |
skills/appfront-migrate/references/migration-guides/standalone-approuter-to-appfront.md | High | Standalone approuter (localDir) migration steps |
skills/appfront-migrate/references/services/app-front-service.md | High | Service plan names in your landscapes, afctl commands |
skills/appfront-migrate/references/target-configs/xs-app-patterns.md | High | Validated xs-app.json patterns for your auth services |
skills/appfront-migrate/references/troubleshooting/known-issues.md | Medium | Issues discovered in real migrations |
skills/appfront-migrate/references/troubleshooting/workzone-integration.md | Medium | CDM steps for WorkZone-integrated apps |
Until populated: Claude uses its training knowledge of appFront as a fallback. Standard migrations (html5-repo → CF + XSUAA) work immediately. Landscape-specific details (exact service plan names, cluster URLs) will be flagged for manual confirmation.
Adding content to reference files
Each placeholder file contains a ## What to put here section listing exactly what content is needed. When you migrate an app and discover issues not covered by the skill, add them to:
skills/appfront-migrate/references/troubleshooting/known-issues.md— compatibility problemsskills/appfront-migrate/references/troubleshooting/deployment-errors.md— deploy failures with fixes
Architecture
This plugin uses only built-in Claude Code tools:
Read,Glob,Grep— reading project filesWrite,Edit— writing migrated or generated filesBash— running discovery commands (find,grep) and build commandsTask— spawning a critic sub-agent for migration quality review
No MCP servers or network access required. The plugin operates entirely on local files.
Skill Behavior Summary
| Skill | disable-model-invocation | When Claude activates it |
|---|---|---|
migrate | Yes | Only on explicit /appfront:migrate command |
validate | No | Auto-activates when user asks to validate an appFront app |
cleanup | Yes | Only on explicit /appfront:cleanup command |
The migration skill requires explicit invocation because it modifies files — auto-activation for file-modifying operations would be surprising and potentially dangerous.
Known Issues
No known issues.
How to obtain support
Create an issue in this repository if you find a bug or have questions about the content.
For additional support, ask a question in SAP Community.
Contributing
Reporting issues
If the skill misses a migration case or produces incorrect output, please:
- Add the case to
skills/appfront-migrate/references/troubleshooting/known-issues.md - Open an issue in this repository
Updating the skill logic
Skill behavior is defined in skills/*/SKILL.md. The HARD RULES, phase structure, and critic checklist can all be updated without code changes — the skills are plain Markdown.
Adding a new migration path
- Add a new guide file in
skills/appfront-migrate/references/migration-guides/ - Add a new source type reference in
skills/appfront-migrate/references/source-types/ - Add the new source type to Phase 0's Source Type Identification section in
skills/migrate/SKILL.md - Add an entry to
skills/appfront-migrate/references/INDEX.md - Update the Supported Migration Paths table in this README
Code contributions
If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.
Changelog
See CHANGELOG.md.
Related Resources
- SAP BTP Application Frontend service: SAP Help Portal
- appFront CLI (
afctl): CLI Reference - SAP Fiori Elements: SAP Help Portal
- SAP CAP (Cloud Application Programming Model): cap.cloud.sap
- SAP MTA Specification: SAP Help Portal
- MBT (MultiApps Build Tool): github.com/SAP/cloud-mta-build-tool
License
Copyright 2026 SAP SE or an SAP affiliate company and html5-applications-migration-skills-for-sap-btp contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.
History
Features 4
Notes
Added
appfront-migrateskill: migrate html5-apps-repo (managed approuter) or SAP Neo HTML5 apps to appFront. Supports CF and Kyma runtimes, XSUAA and IAS auth.appfront-validateskill: validate appFront application configuration for deployment readiness.- Reference folder structure with smart placeholders for migration guides, target configs, service configs, golden path, and troubleshooting.
- Annotated before/after mta.yaml and xs-app.json examples for html5-repo → appFront migration.
Others providing
Compare all 27 on the Agent guidance page →- sap-cx-developer-companionsap-cx-developer-companionAn agent skill for SAP Customer Experience work that routes a request to one of three jobs: finding a Commerce Cloud, Sales Cloud or Service Cloud API, writing CDS for a CX extension, or explaining an error.independent, commerceAgent skill for SAP Customer Experience APIs, CDS and errors
- sap-cloud-integration-pipeline-assistantsap-cloud-integration-pipeline-assistantAn agent skill for the Pipeline Concept framework in SAP Integration Suite Cloud Integration, covering implementation, the Partner Directory, XSLT and Groovy examples and troubleshooting.independent, btpAgent skill for the Pipeline Concept in SAP Cloud Integration
- DanKromp/skillOverflowDanKromp/skillOverflowA collection of 41 agent skills, 37 for CAP, Fiori, BTP, UI5, ABAP, Integration Suite and HANA work and four for creating, reviewing and retiring skills, each with its own eval.independent, capCollection of 41 agent skills, 37 for SAP development tasks
- ARC-DRAWARC-DRAWAn MCP server that draws BTP solution diagrams onto a live draw.io canvas, with 111 SAP BTP icons as native shapes and SAP's diagram guidelines handed to the client as drawing rules.independent, btpMCP server drawing BTP solution diagrams on a draw.io canvas
- sap-ai-dev-toolkitsap-ai-dev-toolkitAn MCP proxy that pins an agent's ABAP tools to one SAP system: setup reads the BAS destinations or the local SAP GUI landscape and writes one stdio server per system, leaving the credentials in the destination or in the editor's own login prompts.independent, abapMCP proxy pinning an agent's ABAP tools to one SAP system
- sap-odata-explorersap-odata-explorerA Rust CLI and desktop app for exploring and testing SAP OData services against real systems — catalog discovery, metadata browsing, an F4 value-help picker and a Fiori-readiness linter — with an agent skill shipped beside it.independent, btpRust CLI and desktop app for exploring SAP OData services
- btp-solution-diagram-generatorbtp-solution-diagram-generatorA Claude plugin that writes BTP solution diagrams as .drawio files in the style of the SAP BTP Solution Diagram Guidelines.independent, btpClaude plugin writing BTP solution diagrams as .drawio files
- abap-skillsabap-skillsSeventeen agent skills for ABAP development in one repository: RAP, CDS view entities, ABAP SQL and AMDP, unit testing, authorisation, eventing, abapGit, ABAP Cloud and the clean core levels.independent, abapSeventeen agent skills for ABAP development
- drawio-skill-sapdrawio-skill-sapA GitHub Copilot agent skill that writes BTP solution diagrams as uncompressed draw.io XML against the SAP BTP Solution Diagram Design Guideline, with SAP's own shape library bundled.independent, btpGitHub Copilot skill writing BTP solution diagrams as draw.io XML
- sap-mdk-appssap-mdk-appsAn agent skill for Mobile Development Kit projects: the project layout, the metadata syntax, and the rules that prevent the failures those two produce on iOS, Android and the web.independent, btpAgent skill for Mobile Development Kit projects
- sap-architecturesap-architectureA Claude Code plugin and portable agent skill that turns a plain-English description into a BTP diagram in SAP Architecture Center style, checked by a validator before it is handed over.independent, btpClaude Code plugin and skill drawing validated BTP diagrams
- SAP Datasphere Plugin for ClaudeSAP Datasphere Plugin for ClaudeEighteen Datasphere skills over a bundled 45-tool MCP server — exploration, view and analytic-model design, BW Bridge migration, security architecture and catalog governance.independent, btpEighteen Datasphere skills over a bundled MCP server
- SAP Power for KiroSAP Power for KiroA set of thirty-five-plus SAP skills packaged as a power for Kiro IDE rather than Claude Code, spanning BTP, UI5, data and analytics, ABAP, CAP and CLI tooling, with automatic context activation in Kiro.independent, btpSAP skills for the Kiro IDE
- drawio-btp-diagram-skillsdrawio-btp-diagram-skillsTwo Claude Code skills that take a BTP architecture described in words through a Mermaid sketch to draw.io XML, with a structural and a visual review after the drawing.independent, btpClaude Code skills for BTP architecture diagrams in draw.io
- AI Skills LibraryAI Skills LibrarySAP's listing of AI skills for SAP work at skills.cloud.sap: skills, plugins, marketplaces and MCP servers from SAP and from third parties, each installed with the skills CLI.sap official, umbrellaListing of AI skills for SAP, installed with the skills CLI
- aicore-sdk-javaaicore-sdk-javaAn agent skill for the SAP AI SDK for Java: it answers a request for Java or Kotlin code that calls the Generative AI Hub from thirteen templates it carries, before it looks anything up.sap official, btpAgent skill generating Java boilerplate for SAP GenAI Hub
- aicore-sdk-jsaicore-sdk-jsAn agent skill for SAP's AI SDK for JavaScript, written against the SDK's version 2: twelve compile-checked templates for calling the Generative AI Hub from TypeScript or JavaScript.sap official, btpAgent skill generating TypeScript for SAP GenAI Hub on AI SDK v2
- aicore-skillsaicore-skillsFour agent skills for SAP AI Core, published as a plugin inside SAP's AI Skills Library: admin resources, the deployment lifecycle, the foundation models in the Generative AI Hub, and the Context Registry behind tabular prediction.sap official, btpFour agent skills for SAP AI Core in SAP's AI Skills Library
- SAP/automation-pilot-agent-skillsSAP/automation-pilot-agent-skillsEight skills for writing, reviewing and operating SAP Automation Pilot content — command generation, catalogue exploration, code review, the content and executions APIs, debugging, schedules, and generating an MCP server from a command.sap official, btpEight skills for writing and operating SAP Automation Pilot content
- SAP Developers MCPSAP Developers MCPThe hosted MCP server of developers.sap.com, over which an agent searches SAP's tutorials, reads missions and queries the site's knowledge graph of tutorials and concepts.sap official, umbrellaHosted MCP server of developers.sap.com tutorials and missions
- sap-fiori-iossap-fiori-iosAn agent skill SAP publishes for SAP Fiori for iOS: it maps a node of the Fiori iOS UI Kit in Figma onto SwiftUI code, and answers which Fiori component a Figma variant becomes.sap official, btpAgent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUI
- SAP/leanix-ai-pluginsSAP/leanix-ai-pluginsOne Claude Code plugin, sap-leanix, bundling two skills that build and debug LeanIX automation scripts and create and manage calculations, both working through the LeanIX MCP server.sap official, btpClaude Code plugin with two skills for SAP LeanIX scripting
- SAP-samples/joule-a2a-agent-toolkitSAP-samples/joule-a2a-agent-toolkitFour skills for building an agent that talks to SAP Joule over A2A and getting it onto Cloud Foundry — the agent itself, and the three CLIs the deployment goes through.sap official, btpSkills for building an A2A agent for Joule and deploying it to CF
- SAP-samples/sap-devs-cliSAP-samples/sap-devs-cliA CLI that injects current SAP developer knowledge packs into an AI coding tool's context and wires up SAP's own MCP servers for it, shipped as a single binary through Homebrew, Scoop or GitHub Releases.sap official, btpCLI adding SAP developer knowledge and MCP servers to AI coding tools
- sap-tutorials-contentsap-tutorials-contentAn agent skill that maps the public developers.sap.com content API: the catalogue, the navigation, a tutorial's HTML or JSON, and full-text search, all anonymous and read-only.sap official, btpAgent skill mapping the developers.sap.com content API
- secondsky/sap-skillssecondsky/sap-skillsForty SAP development plugins installed through the skills command line or the Claude Code and Codex marketplaces, with a record per plugin of what its claims were checked against.independent, btpForty SAP development plugins for coding agents
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Contributors
History in the atlas
- Application Frontend service
- Claude Code
- The same sentence, followed by what the README's requirements name for reaching Cloud Foundry: the MultiApps Build Tool, the CF command line logged in and targeted, the CF multiapps plugin, and the optional appFront command line.
- First seen.
For your agent
- Ref
artifact:sap-samples-html5-applications-migration-skills-for-sap-btp- JSON
- /artifacts/sap-samples-html5-applications-migration-skills-for-sap-btp.json
- MCP
- Connecting an agent