Creating Skills for Repeatable Workflows

Objective

After completing this lesson, you will be able to create a reusable Skill and apply the judgment test for when to make a workflow into a Skill.

Creating Skills for Repeatable Workflows

A consultant has explained the same workflow to Joule Work four times this week: check the calendar for the customer meeting, search emails from that customer, summarize open issues, produce a preparation briefing. Each time, the same steps. Each time, re-explained from scratch.

That is a Skill waiting to happen. Once created, the workflow exists permanently. No re-explanation. No re-typing. One invocation and Joule Work runs it.

The Judgment Test

Not every workflow belongs in a Skill. The test is simple:

If you have explained the same workflow to Joule Work three or more times, make it a Skill.

Three repetitions is the signal. It tells you two things: the workflow is stable enough to codify, and the overhead of re-explaining it is real. Below three, the workflow may still be evolving. At three, it is ready.

Apply the test actively. When you find yourself typing the same context and instructions again, stop. Make a Skill instead.

Two Types of Skills

Instruction-only Skills contain context and task instructions for a repeatable personal workflow. No external system connection required. Use these for workflows that draw entirely on your local files, email, and calendar.

Examples:

  • Customer Meeting Preparation — calendar check, email search, open issues summary, briefing output

  • Weekly Inbox Triage — unread email summary sorted by sender priority

  • Document Action Extractor — scan files in working directory and list all action items with owners

Plugin Skills bundle a connector with workflow instructions. Installing the Skill sets up both at once. Use these when the workflow requires an external system, for example a Signavio process map, a JIra baord, a GitHub repository.

When a workflow needs a connector, a plugin Skill is cleaner than managing the connector and the instructions separately. The connector activates automatically when the Skill runs.

Skills overview — what they are, how they activate, and the SAP AI Skills Library marketplace.

How to Create a Skill

Two approaches work equally well.

Conversationally: Say "create a skill for [your workflow]." Joule asks for a name, a description, and the workflow instructions. It guides you through the process and saves the Skill to your Extensions.

Via the interface: Extensions → Skills → + New → Create Skill. Fill in the name, description, and instructions. Save.

Either way, the result is the same: a saved Skill available in every future conversation.

Using a Skill: You do not need to explicitly call a Skill by name. Describe what you want in natural language and Joule recognizes which Skill matches your request, loads it, and runs it. If you want to choose a specific Skill manually, go to Extensions → Skills and select it from there.

Before You Build: Check the SAP AI Skills Library

Before creating a Skill from scratch, check whether someone has already built it. The SAP AI Skills Library is a public catalog of pre-built Skills, MCP servers, and plugins, maintained by SAP and the community.

To install a published Skill:

  1. Open AI Skills Library and search by name, tag, or description
  2. On the Skill's detail page, click Add to Joule Work Desktop
  3. The Skill opens in the Joule Work desktop app and is ready to use immediately

Each listing shows the author, trust level, license, and a link to the source repository, so you can review what a Skill does before installing it.

If nothing in the Library fits your workflow, build your own using the steps in this lesson.

Watch both paths: installing a prebuilt Skill from the Library, and creating a custom no-code Skill by describing the process, required inputs, expected outputs, and preferred tone.

Sharing Skills

Skills can stay personal or be shared with colleagues.

Share with a colleague: Extensions → Skills → Export → share the file. The colleague imports it via Extensions → + New → Add Skill → Import.

Contribute to the SAP AI Skills Library: If you build a Skill that could help others, you can publish it to skills.cloud.sap. The Library uses an open contributor model backed by a public GitHub repository. See the Library's contributor guide for details.

The Governance Rule

One rule applies to every Skill installation, without exception:

Only use Skills from trusted internal sources or Skills you have created yourself.

Skills from unknown external sources are not permitted. A Skill has access to your files, email, calendar, and connected systems. Before installing any Skill someone sends you, confirm it came from your IT team or a colleague you trust. When in doubt, ask your IT administrator before installing.

Lessons Summary

  • The judgment test: if you have explained the same workflow three or more times, make it a Skill.
  • Instruction-only Skills codify workflows that use local context. Plugin Skills bundle a connector with workflow instructions.
  • Create a Skill conversationally ("create a skill for...") or via Extensions → Skills → + New.
  • Use a Skill by describing what you want, the Joule Work desktop app recognizes and runs the matching Skill automatically. Select manually from Extensions → Skills if needed.
  • Before building a Skill, check the SAP AI Skills Library, a pre-built Skill may already exist.
  • Share Skills by exporting a file for a colleague to import, or contribute them to the SAP AI Skills Library.
  • Only install Skills from trusted sources — check the author, trust level, and license before installing. When in doubt, ask your IT administrator.