skill-sap-samples-cap-agentic-engineered-sap-fiori · by Install
$ agentstack add skill-sap-samples-cap-agentic-engineered-sap-fiori ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sap-samples-cap-agentic-engineered-sap-fiori) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Fiori MCP-First Development
Before writing, modifying, debugging, or fixing CDS annotations, Fiori Elements page configuration, or manifest.json, you MUST query the Fiori MCP server and apply its guidance.
Tools
Use mcp__fiori__* tools — primarily mcp__fiori__search_docs, mcp__fiori__list_functionality, mcp__fiori__get_functionality_details, and mcp__fiori__execute_functionality.
Workflow
- Query before coding — call
mcp__fiori__search_docsfor annotation patterns, floorplan config, or manifest structure - Trust MCP over training knowledge — if guidance conflicts with what you know, follow MCP
- Use Fiori MCP tooling for modifications — before manually editing manifest.json or annotations, check if
mcp__fiori__list_functionalityprovides an automated function - Prefer the simplest pattern when MCP returns multiple valid approaches
Scope
This skill covers:
- CDS annotations:
@UI,@Common,@Capabilities,@Communication - Fiori Elements floorplans: List Report, Object Page, Analytical List Page
manifest.jsonconfiguration: routing, data sources, control configuration- Custom actions in manifest (
controlConfiguration.actions)
Fiori Elements App Rules
When creating or modifying SAP Fiori Elements applications:
- The application typically starts with a List Report page showing the base entity in a table. Row details are shown in an ObjectPage based on the same entity.
- An ObjectPage can contain table sections based on to-many associations. Row details in a table section can open another ObjectPage based on the association's target entity.
- The data model must have one main entity with navigation properties to related entities.
- Each property must have a proper datatype.
- For all entities, provide primary keys of type UUID.
- 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). - When modifying the application (e.g., adding columns), do not use screen personalization — modify the project code. Always check whether
mcp__fiori__list_functionalityprovides a suitable function first. - When previewing, use the most specific
npm run watch-*script for the app inpackage.json.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: SAP-samples
- Source: SAP-samples/cap-agentic-engineered
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.