Automate IBM i tasks via the ibmi CLI with SQL and NDJSON streaming.
npx skills add https://github.com/ajshedivy/ibmi-agent-skills --skill ibmi
Please help me install this Agent Skill. Skill: ibmi Source: https://github.com/ajshedivy/ibmi-agent-skills/tree/main/skills/ibmi Command: npx skills add https://github.com/ajshedivy/ibmi-agent-skills --skill ibmi
IBM i administrators and developers need a consistent, scriptable way to interact with Db2 for i, run queries, discover schemas, and automate cross-system workflows. This skill provides a unified CLI interface and robust scripting patterns that reduce manual tasks and errors.
Install the ibmi CLI and connect to a configured IBM i system to begin running queries and scripting tasks.
High-intent search queries and answers about installing and using this skill.
IBM i SQL query execution across multiple systems is automated using the ibmi CLI, which supports multi-system configurations, schema discovery, and deterministic outputs within CI workflows. It provides a unified interface to run cross-system tasks.
NDJSON streaming (--stream) is a data processing mechanism that outputs continuous JSON objects for IBM i scripting tasks. It is needed when handling large query result sets or running continuous agent scripts where buffering entire outputs would cause memory or pipeline bottlenecks.
The ibmi CLI supports dry-run planning for CI/CD pipelines by evaluating multi-system workflow configurations without executing destructive changes. It returns semantic exit codes to signal success or specific failure states, enabling deterministic automation pipeline control.
IBM i task automation can be extended using YAML-based tools that define custom scripting patterns for the ibmi CLI. This allows administrators to configure specific Db2 for i interactions and operational workflows without modifying the core CLI implementation.
The best way to run cross-system diffs for Db2 for i schemas is using the ibmi CLI's multi-system workflow capabilities. It connects to configured IBM i targets, discovers database schemas, and executes comparative SQL queries to identify structural differences across systems.
Semantic exit codes should be used in IBM i automation workflows because they provide deterministic success and failure signaling for CI/CD pipelines. They allow agent scripts to distinguish between connection errors, query failures, and dry-run validations for precise pipeline control.
wwa-labAnalyze IBM i data models from DDS, DB2 metadata, SQL DDL, and program evidence.
hmzainjamilAutomate DevOps workflows for deployment notifications, alert routing, and Kubernetes rollouts.
soo-kate-yeonAuthor and manage Codex skills, sub-agents, plugins, and configuration.
sparkeh9Execute native tools from PowerShell with stdout/stderr capture and exit code enforcement.
