SkillSkilltypeA procedure an agent follows. Indexed here, never written here.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

scaffold-fiori-ai-bridge

An agent skill that makes a UI5 or Fiori app AI-callable: it generates the JavaScript bridge and the SAP Joule Frontend Actions YAML the app needs before an agent can reach into it.

Takes what a UI5 or Fiori application can already do, such as reading displayed data, applying a filter, navigating, editing a field or pressing a button, and exposes it as something a model may call, either as SAP Joule Frontend Actions or as Chrome WebMCP tools. It asks three questions before it reads any code: app or library control, which consumer, and whether tools should be semantic or one per control. It then reads the manifest, Component.js, the controllers, the views and the metadata, sorts what it finds into navigation, read, write, UI state and private or sensitive, and puts the grouped list back to the developer before generating anything. What it writes is webapp/joule-bridge.js, a webmcp-bridge.js where WebMCP was chosen, and the capability, scenario and function YAML files with a deploy script, under the constraints the runtime imposes: every action returns { status, content } with the content as a string, fifteen seconds per action, ten kilobytes per response, a thousand characters per scenario description, and com.sap.<namespace>.<ActionName>.v1 naming. It stops at the generated files and a post-generation checklist, so deploying the Joule scenario and verifying it stays the developer's step.

Facts

Last pushLicenceMIT

Where it sits

Lives in
Provides
Agent guidanceUI5Agent guidancecapabilityPackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.

Who is behind it

Vinay K NVinay K NPersonMaintains this
In the atlas: maintains 1, contributes to 2
@I562693-VKN
maintainer

What it declares

Every artifact

Type
Skill
Origin
Independently maintained

As a skill

Distributed through
does not say

Tasks this contributes to1Beta

Make a Fiori application's own actions callable by JouleA developer wants the things their UI5 or Fiori application can already do, such as reading what is displayed, applying a filter, navigating or pressing a button, exposed as actions an assistant may call, without working out the bridge and the descriptor shapes from scratch.Coversthe four-step procedure, and the bridge and descriptors it generates
What it does

It asks three questions before it reads any code, whether the target is an application or a library control, which consumer is wanted, and whether tools should be semantic or one per control. Then it reads the manifest, Component.js, the controllers, the views and the models, puts the grouped candidates back for confirmation, and writes the files only after the developer signs off on the list. It carries the runtime limits as rules rather than as notes: a { status, content } return with the content always a string, fifteen seconds an action, ten kilobytes of response, a thousand characters of scenario description, and a com.sap.<namespace>.<ActionName>.v1 name matching in the JavaScript and the YAML.

Remaining work

Deploy the capability descriptor to the Joule tenant through the command line, which the skill states is not its step, and verify the actions are reachable from there. The repository read on 2026-10-15 names no client the skill installs into, so loading it is the reader's to work out.

All options on the Agent guidance page →

Connections1

README

quoted from I562693-VKN/Skill-Hub under MIT, read
I562693-VKN/Skill-Hub/README.mdOn GitHub

Skill-Hub

Collection of dev , productivity skills for claude, joule, Ui5

MIT, read
Agent guidance
  1. DanKromp/skillOverflowCollection of 41 agent skills, 37 for SAP development tasks
  2. sap-odata-explorerRust CLI and desktop app for exploring SAP OData services
  3. WerkbankLocal desktop workspace for AI conversations with SAP connectors
  4. SAP Power for KiroSAP skills for the Kiro IDE
  5. SAP Developers MCPHosted MCP server of developers.sap.com tutorials and missions
  6. sap-fiori-guidelinesAgent skill built from the Fiori Design Guidelines
  7. SAP/ui-theme-designer-plugins-for-coding-agentsAgent plugin on the SAP Design System and theming parameters
  8. secondsky/sap-skillsForty SAP development plugins for coding agents
  9. UI5/plugins-coding-agentsUI5 plugins for coding agents
  10. UI5 Web Components agent skillsTwo agent skills for accessibility and styling of web components

Details

Sources3
SAP AI Skills Librarydiscovered here, skills.cloud.sapchecked
README.mdquoted, and what the entry declareschecked

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
discovered viaSAP AI Skills Library · skills.cloud.sap
first seen in the atlas
ecosystem and domainui5, ai-and-agents
History in the atlas2
  1. A repository new to the SAP AI Skills Library registry snapshot of 2026-10-09, with no prior processed record in the collection cache, registering one skill at skills/Scaffold-fiori-ai-bridge. Written from the repository's README and that skill's own SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the UI5 door because the files it reads and writes are a UI5 application's, with Joule and WebMCP as the consumers it generates for.
  2. First seen.
For your agent
Ref
artifact:i562693-vkn-scaffold-fiori-ai-bridge
JSON
/artifacts/i562693-vkn-scaffold-fiori-ai-bridge.json
MCP
Connecting an agent