IBM

Describes how to maintain an ado project including how to identify resources that are candidates for deletion, and how to label testing or provisional resources. Use when asked to clean up, tidy, or run maintenance on an ado project/context; to find what can…

Guidance for creating ado resource YAML files (discoveryspace, operation, actuatorconfiguration, samplestore, document). Covers metadata conventions, dynamic reference resolution with --use-latest/--with/--set, space design principles, avoiding duplicate…

Understand the work done in an ado project/context: recent activity, research underway, study documents, spaces and operations over time, experiments and configs used. Use when the user asks for the latest or recent activity in a project; what research…

End-to-end workflow to examine and summarise an ado discoveryspace — fetch space YAML, describe entity and measurement space structure, assess sampling coverage, export measurement data, and find related resources. Use when the user asks to inspect,…

Creates experiment campaigns for addressing discovery problems (research questions) by creating ado discoveryspace and operation YAML. Guides experiment selection and parameterization for a new space, entity-space design, validation, and operator selection.…

Query ado catalogs, metadata, and measurement data via the CLI. Use when the user asks what experiments, actuators, operators, contexts, spaces, or operations are available; to list or find resources; check the active context/project; filter by metadata or…

Reference for ado CLI command syntax, flags, and usage patterns — get, create, edit, show, describe, output flags (-o, --output-file), convenience flags (--use-latest, --set, --with), debugging with -l, and run_experiment. Use when writing, verifying, or…

End-to-end workflow for conducting empirical studies with ado — systematic exploration and analysis of entity spaces. Covers problem formulation, optional implementation of custom experiments/operators, execution (local or remote), and analysing results. Use…

Explains how operator-sdk and kubebuilder work specifically for the ibm-licensing-operator - its CRDs, controllers, reconcile flow, scheme/manager wiring, kubebuilder markers, and the code-generation chain. Use to understand the operator's architecture, where…

Install, verify, and clean the local development toolchain (operator-sdk, opm, controller-gen, kustomize, yq, linters, detect-secrets) for the ibm-licensing-operator repo. Use for first-time setup, onboarding, when a build fails because a tool is missing or…

Perform a thorough, precise code review of a GitHub pull request, in the agent thread, using the `gh` CLI. Give it a PR number (preferred) or a branch name - it fetches the PR and diff with `gh`, runs an explicit review loop, decides PASS or CHANGES…

How License Service is split across three separate repositories - the operator (this repo), the operand (the containerized License Service application), and the commons (a shared library) - and how they interplay at build time and runtime. Use to understand…

Build the ibm-licensing-operator binary/image and run or deploy it against a Kubernetes cluster for local development and testing. Use to compile the operator, run the controller locally against a cluster, build and push a dev image to the scratch registry,…

Build the development Helm charts for the License Service family (License Service, License Service Reporter, License Service Scanner) used for the "License Service without an IBM Cloud Pak" / no-operator deployment path. Use to package and test Helm-based…

Format, tidy, vet, lint, and secret-scan the ibm-licensing-operator codebase before committing or opening a PR. Runs the same checks the pre-commit git hook and CI enforce (golangci-lint, shellcheck, yamllint, mdl, go vet, detect-secrets). Use before every…

How to contribute high-quality changes to the ibm-licensing-operator repo - the end-to-end workflow, DCO sign-off, the pre-PR quality checklist, when generated files must be committed, copyright headers, branching, and version bumps. Use when preparing a…

Use this skill when making HTTP requests in fp-go using the ReaderIOResult-based HTTP client (github.com/IBM/fp-go/v2/context/readerioresult/http). Trigger on mentions of fp-go HTTP, MakeClient, MakeGetRequest, MakeRequest, ReadJSON, ReadText, ReadAll,…

Use this skill when working with logging in fp-go functional pipelines (github.com/IBM/fp-go/v2/logging). Trigger on mentions of logging in monadic contexts, ChainFirstIOK, ChainFirst with logging, side-effect logging, structured logging (SLog),…

Guides writing, refactoring, and reviewing fp-go v2 code that uses functional composition via Pipe and Flow. Apply this skill whenever the user asks to write new fp-go code, refactor imperative Go into functional style, explain a Pipe/Flow pipeline, add…

Use this skill when reviewing pull requests for fp-go code (github.com/IBM/fp-go/v2). Trigger on mentions of PR review, code review, pull request validation, fp-go best practices validation, functional programming review, or when the user asks to review…

Use this skill whenever writing, reviewing, or refactoring Go code that uses the fp-go library (github.com/IBM/fp-go/v2). Trigger on any mention of fp-go, functional programming in Go, monads in Go, Option/Either/Result types in Go, IOResult, ReaderIOResult,…

Use this skill when working with lenses and optics in Go using the fp-go library (github.com/IBM/fp-go/v2/optics/lens). Trigger on mentions of lenses, optics, MakeLens, MakeLensRef, MakeLensStrict, lens composition, immutable updates to nested structs,…

Use this skill when working with the fp-go MCP (Model Context Protocol) server located in github.com/IBM/fp-go/gen/v2. Trigger on mentions of MCP server, fp-go MCP tools, list_skills, use_skill, search_examples, get_example, configuring fp-go for Claude…

Expert guidance for generating watsonx Orchestrate native solutions from SOPs or simple prompts. Implements agents, flows, tools, and knowledge bases based on business requirements.

Use when the user wants to analyze agent telemetry traces to find bugs and get fix recommendations — walks through exporting traces from a local or remote watsonx Orchestrate server, parsing raw OTel JSON or Langfuse-format trace JSON directly, and reasoning…

Build MCP servers for customer care agents following Watson Orchestrate specifications. Guides agents through tool creation, transaction patterns, authentication, widgets, and context management with strict adherence to reference specifications. Use when…

Evaluate an agent instructions or agent definition for achievability and produce a structured, evidence-backed report artifact with per-dimension scores, findings, deterministic signals, and high-impact recommendations.

Analyzes watsonx Orchestrate (wxO) projects and generates a 3-report documentation set covering the overall solution, agents, and tools/connections/other components with Mermaid diagrams.

Expert guidance for creating high-level solution architecture documents from business requirements, use cases, or problem statements. Produces three focused documents - business overview, technical architecture, and implementation plan - with sufficient…

Expert guidance for building a Standard Operating Procedure (SOP) from a workflow diagram, Langflow JSON, n8n JSON, BPMN model or workflow description. Focuses on business problem, data requirements, and business logic in plain language.

Doctest-driven code generation for competitive-programming problems. The orchestrator first designs a quality gate of doctests (happy-path AND self-devised edge cases), verifies their expected values with a reference solution, injects them into the code…

ABLATION VARIANT — ORCHESTRATION REMOVED. This is the doctest-driven code-completion skill with the Orchestration pattern ablated out. The iterative Recovery Loop is preserved (write code, run doctests, fix on failure, repeat until they pass or the budget is…

Use this skill whenever you are given a Python code file with missing code and asked to complete it — whether that is a single incomplete line, an API invocation, or an entire function body. This skill completes the missing code by first generating doctests…

ABLATION VARIANT — RECOVERY LOOP REMOVED. This is the doctest-driven code-completion skill with the iterative Recovery Loop pattern ablated out. Everything else (Orchestration: the staged pipeline, task routing, 5-tier classification, multi-file progressive…

Use this skill whenever you are given a Python code file with missing code and asked to complete it — whether that is a single incomplete line, an API invocation, or an entire function body. This skill completes the missing code by first generating doctests…

Use this skill whenever you are given a Python code file with missing code and asked to complete it — whether that is a single incomplete line, an API invocation, or an entire function body. This skill completes the missing code by first generating doctests…

Use this skill whenever you are given a Python code file with missing code and asked to complete it — whether that is a single incomplete line, an API invocation, or an entire function body. This skill completes the missing code by first generating doctests…

Few-shot examples skill that provides reusable examples of common Wikidata SPARQL patterns. Use before generating SPARQL to find relevant examples that demonstrate how similar questions have been answered, covering patterns like direct lookups, reverse…

Graph exploration skill that inspects the Wikidata knowledge graph around seed entities using small diagnostic SPARQL queries. Use to verify property directions, discover graph paths, inspect qualifiers, and build evidence for the final query structure.

SPARQL execution skill that sends queries to the Wikidata Query Service, captures results, validates them against the user's intent, and performs iterative repair when queries fail or return implausible results. Use when you have a candidate SPARQL query…

SPARQL generation skill that constructs a SPARQL query from resolved Wikidata entities, properties, and graph paths. Use when you have verified Wikidata IDs and need to assemble them into a syntactically correct SPARQL query with proper triple patterns,…

End-to-end Text-to-SPARQL skill that orchestrates wikidata-search, graph-exploration, sparql-generation, and sparql-execution to convert a natural-language question into a validated, executable SPARQL query over Wikidata. Use when the user asks a…

Wikidata search skill that resolves entity names and relation phrases to Wikidata item IDs (QIDs) and property IDs (PIDs) using the Wikidata API. Use when you need to find Wikidata identifiers for entities or properties mentioned in a natural-language…

API spec for pyflow, IBM's LLM-optimized Python DSL for authoring DataStage and StreamSets flows. Its compact surface and compile-time validation offer context efficiency, fast feedback, and correctness guarantees, making it the ideal choice for writing flows…

Generates a Markdown bug report for an IBM watsonx.data integration session. User can invoke directly. The agent MUST propose it (and must wait for explicit acceptance) after 3 or more consecutive calls to the same tool or the same sequence of tools result in…

Guide for creating, editing, and using parameter sets (paramsets) in IBM watsonx Data Integration. Covers parameter types, value sets, PROJDEF, local parameters, runtime parameters, flow parameters, #param# and ${param} reference syntax for both DataStage…

Reference for the verbose watsonx.data integration SDK for DataStage (batch) flows, with exhaustive stage and property access. New flows can only be created with pyflow's compact DSL (`di-agent-flow-pyflow`); use this SDK to edit existing flows in place — for…

Q&A reference for the DataStage parallel engine — parallelism, partitioning theory, APT configuration files, concurrent job execution, restart/recovery, disk/resource tuning, dataset performance, flow optimization (partitioning/sorting/memory), and per-stage…

Deploys, configures, and troubleshoots IBM Cloud Code Engine workloads using the ibmcloud ce CLI. Analyzes source code to choose between app (HTTP) and job (batch) deployment, detects required secrets and environment variables, selects scaling parameters, and…

Convert amounts between different currencies with current exchange rates

Get personalized travel destination recommendations based on preferences

Get current weather and forecast for any location worldwide

Create, load, package, or modify an external custom operator for docpipe. Use when a consumer needs an AbstractOperator supplied through DOCPIPE_CUSTOM_OPERATORS, DocpipeFlowManager, package entry points, S3, or register_operator_provider without modifying…

Add or modify an ingest document source provider for IngestSourceOperator. Use when creating its Pydantic configuration, DocumentSourcePort adapter, factory registration, lazy binary retrieval, provider tests, runnable flow, dependency and documentation…

Create or modify built-in docpipe operators that ship from src/docpipe. Use when implementing transform behavior, metadata and validation, DOCPIPE_OPERATORS registration, tests, a runnable flow, documentation, and changelog updates. Do not use for externally…

Exercise observable docpipe feature behavior without depending on pytest or existing test cases. Use for operator, pipeline, ingest-provider, orchestration, REST API, or Python API validation by building a small runnable scenario, executing a public…

Use when the user wants to analyse a legacy monolithic application (Java/.NET) and generate discovery artifacts — such as tech stack summaries, architecture overviews, API inventories, data models, dependency maps, and migration readiness reports. Optionally…

Use when the user wants to decompose a monolithic application into microservices — walks through graph-first evidence retrieval from Neo4j, bounded context identification, service design, data ownership, and generation of a full microservices portfolio…

Use when the user wants to generate detailed microservice design artifacts — OpenAPI specifications, SQL ownership schemas, design documents, and design review guidelines — from architectural artifacts (architecture specifications, microservices catalog,…

Use when the user wants to generate production-ready microservice implementation code from approved architecture and design artifacts — retrieves architecture specifications, OpenAPI, SQL schemas, and design documents from MinIO, generates and validates…

Run verification checks for the galaxium-travels repo. Use after every implementation. Use when the user asks to verify, validate, run tests, check lint, or confirm that changes are correct. Knows which checks are cheap (ruff, pytest, frontend lint) vs…

Use when the user wants to stress-test and document a plan for demo purposes - asks up to 3 focused questions, then produces a Markdown summary, optionally posts it to the originating GitHub issue as a comment, and finally generates the HTML planning…

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Generate Tekton Pipeline that defines the workflow of the task execution.

Generate the Kubernetes `Secret` and `ServiceAccount` to define the docker-registry data.

Generate Tekton Task that uses Trivy to scan generated container for vulnerabilities.