Skills for the IBM Building Blocks¶
This collection of Skills for IBM Bob provides IBM Bob with the expertise to quickly build applications using the IBM Building Blocks. Each skill focuses on a specific Building Block and contains task-specific instructions, code patterns, examples and constraints Bob should follow when doing engineering work.
Quick Start¶
The Skills have been packed into a single .zip that you can easily download and install.
- Go to the skills.zip page
-
Click the
Download raw fileicon at the upper-right of the page.
-
Copy all skill folders into either your global or project-level
.bobfolder:- global =
~/.bob/skills - project =
<project>/.bob/skills
- global =
-
Bob will automatically activate the appropriate skill when working on related tasks.
Skill Taxonomy¶
Each Skill for IBM Building Blocks often aligns with an IBM product but not always. For specifics on how each skill works, read through the associated SKILL.md.
AI Skills | |
|---|---|
Agents |
agent-builder
Build and deploy multi-agent systems with tools (MCP servers) using watsonx Orchestrate's Agent Development Kit (ADK), CLI and REST API. |
AI Trust |
agent-ops
|
Data Skills | |
|---|---|
Integration |
data-streaming-confluent
data-streaming-confluent-terraform
|
Intelligence |
data-enrichment
|
Query |
no-sql-astradb
|
Automation Skills | |
|---|---|
Build |
infrastructure-as-code-ansible
|
Modernize |
code-modernization-java
|
Optimize |
automated-resource-management-turbonomics
|
Contributing to Skills for IBM Building Blocks¶
Start by reading Bob's Skills documentation plus these skill authoring best practices.
Skills are not meant to restate generic programming, architecture or cloud development concepts. IBM Bob is a frontier model with PhD-level knowledge across most engineering domains, so these Skills skip reiterating the basics.
Instead, these Skills encode the local, up-to-date know-how that does-not-yet reside in Bob's memory, mostly because it's too new, like code library updates, API endpoints or CLI command syntax for IBM' latest product releases.

A well-written skill captures the parts of engineering practice that are usually scattered across docs, repos, examples, Slack threads, and senior-engineer muscle memory. A good Skill tells Bob what inputs are required, what rules to follow, necessary syntax elements, but most important, a good skill ensures Bob let's IBM engineers, partners and customers focus more on the use case and less on the underlying complexity of modern agentic applications.
If you want to contribute to Skills for IBM Building Blocks, please open a pull request with your edits/submissions. Any other questions, contact us on #build-engineering-ww
Skills vs Modes¶
IBM Bob uses both Modes and Skills, but they solve different problems.
A Mode defines the role Bob is operating in. It sets the posture, behavior, tool usage, and level of autonomy Bob should apply to the work. A Mode answers the question: What kind of engineer is Bob acting as right now?
A Skill defines the specific engineering knowledge Bob should use while doing the work. It provides task-level instructions, implementation patterns, examples, constraints, and known-good approaches for a particular Building Block. A Skill answers the question: What does Bob need to know to do this task correctly?

Put another way: Modes shape how Bob thinks. Skills shape what Bob knows how to do. For example, an AI Solution Architect mode could use multiple Building Block Skills to design an agentic application architecture: agent-builder + agent-ops and no-sql-astradb. A Data Engineer mode might also use the no-sql-astradb skill but also use the data-pipeline-wxdata and data-streaming-confluent skills too.










