Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →secondsky/sap-api-policy
Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a).
Passed 19 of 22 test cases with the skill, and 7 of 22 without it.
and 13 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building a custom AI agent that pulls daily sales order volumes from our on-premise S/4HANA 2023 system using the standard Sales Order OData V4 API. The agent will summarize this for our sales reps. Can you evaluate this architecture? I need a report that includes the mandatory legal disclaimers at the beginning and end, a summary table of the facts, your final assessment rating, your confidence level, any remaining risks, and a list of specific questions I should take to our SAP account team. Also, let me know if this will trigger any Digital Access licensing fees.
| Checked | Without skill | With skill |
|---|---|---|
| routes the Digital Access licensing question to the SAP account team without providing a definitive answer | Missed | Passed |
The instructions your model reads when the skill loads.
Assess whether an SAP API usage scenario appears aligned with the SAP API Policy v.4.2026a (and its FAQ v1.2, May 2026) by gathering evidence from official SAP sources and the user's own facts, then producing a conservative, sourced technical assessment.
Use this skill for a single SAP interface assessment, an architecture decision involving SAP APIs, or a batch inventory that needs evidence-based policy triage. Route purely legal, contractual, commercial, or roadmap questions to the appropriate SAP or customer owner.
Never present the result as legal advice, contractual advice, or a final/definitive SAP compliance decision. Only SAP, the applicable contract, or SAP support/account/legal channels can give a binding answer for a specific customer landscape. This is not a hedge you can drop to sound more helpful — SAP itself declines to publish a binary "compliant / not compliant" decision matrix (FAQ Q49), so a confident yes/no would misrepresent what is knowable. Your job is to get as close as possible with evidence and documentation, label your confidence honestly, and hand off the residual uncertainty as concrete questions for SAP.
Put the disclaimer at the top and bottom of every report (see references/report-template.md).
Some requests are not evidence-based technical-alignment questions, and you must not answer them as if they were. When a question turns on any of the following, say plainly that it is outside this assessment and route it to the right SAP channel — do not guess:
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.