Concept card

SAP Joule Skill Builder

As of 2026-10-06

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP Joule Skill Builder?

A Joule skill is a deterministic, parameterised unit built in Joule Studio's skill builder (SAP Build, classic edition): Joule picks it from its English description, fills its inputs, runs actions, processes or automations, and returns outputs; agents can reuse skills as tools.

The Joule skill builder is the part of Joule Studio that packages one bounded capability into a unit Joule can call: look up a sales order, return a KPI, create a ticket, start an approval. SAP's documentation describes skills as the way to let Joule "perform additional, tailored, and deterministic tasks". A skill has no open-ended reasoning of its own. The reasoning sits in Joule, which decides that a user request matches the skill, and in agents, which may call skills as tools (C162).

Where the skill builder lives and what you need

Skills are built in Joule Studio, classic edition, a component of SAP Build that depends on SAP Build Process Automation. The skill builder became generally available in Q2 2025 (SAP Business AI release highlights, July 2025). To set it up you need, per SAP Help: a Joule subscription; an active user (developer) licence for SAP Build with the build-default service plan (other licences and plans are not supported); a BTP subaccount subscribed to SAP Build Process Automation; and SAP Cloud Identity Services. A booster ("Setting Up Joule") creates the formation that links Joule, SAP Build Process Automation and Identity Services. The designer is supported on Chrome and Edge only.

The new Joule Studio announced in May 2026 follows an intent-based approach and is opened from Joule Work (C113). It generates agents rather than exposing a separate skill canvas, so the skill builder described here is the classic edition path, still documented and in use in September 2026.

Why it matters

Skills are still the cheapest, most testable way to put a deterministic SAP action behind Joule, and they become tools for agents.
Routing depends on an English description and input descriptions, not on code: that is where most 'Joule ignores my skill' issues start.
Quotas (4-minute execution, 100 KB response) and identity settings decide whether a skill that works in a demo survives production.

Key points

Built in Joule Studio classic edition (SAP Build); skill builder GA since Q2 2025; requires SAP Build build-default plan, SAP Build Process Automation, Joule and Cloud Identity Services.
Joule triggers a skill from its English description; required inputs missing from the request are asked for.
User-started skills accept string inputs only; outputs are mandatory when a skill is called by another skill.
Activities: actions, processes, automations, sub-skills, conditions, variables, formulas, send message.
Action tasks: 4-minute total execution, 512 KB request, 100 KB response; lifecycle Editable, Released, Deployed with semantic versions.
Skills carry no reasoning of their own: routing is a match on description text, not model iteration inside the skill's flow, which is also why a skill's own execution is not metered the way an agent's thinking steps are.
The confirmation switch ('Require user confirmation before running') is the cheapest human-in-the-loop control in the stack and should default to on for any irreversible skill action, not to the platform default.
The new, intent-based Joule Studio (announced May 2026) generates agents rather than exposing a separate skill canvas; the skill builder covered here remains the classic-edition path, still documented and in use in September 2026.

Terms used on this page

Joule skill: Deterministic, parameterised capability built in Joule Studio that Joule triggers from its description.
Action project: Joule Studio project that defines API actions (OData, CAP, RAP, RFC, integration flow, Business Accelerator Hub) used by skills.
Environment: Deployment area in Joule Studio classic; shared environments restrict which users or groups can run deployed skills and agents.
build-default plan: SAP Build service plan required, with the active user (developer) licence, to set up Joule Studio classic edition.
Response generation toggle: 'Allow Joule to generate a response' setting, on by default; switching it off hands response wording to an explicit Send Message step.
Direct-start toggle: 'Allow skill to be started directly by a user' setting, on by default; switching it off reserves a skill as a helper other skills can call but users cannot invoke directly.
Description drift: Two or more skills whose descriptions overlap enough that Joule's routing competes for the same requests; reviewed as a set, not skill by skill.
SAP Audit Log service: SAP BTP service that records security-relevant Joule Studio events (deploy, undeploy, assistant switch, privilege change) for governance review.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.

Joule Studio SAP: availability, skills, guardrails