skills/configuration/SKILL.md
Query IBM i system configuration including system values, hardware resources, device status, environment variables, and JVM settings via SQL services. Use when user asks about: (1) system value settings like QSECURITY or QCCSID, (2) security-related system values, (3) hardware resource inventory, (4) controller, device, or line status, (5) environment variable settings, (6) active JVM information, (7) replacing DSPSYSVAL, DSPHDWRSC, WRKCFGSTS, WRKENVVAR commands, or (8) any system configuration review.
npx skillsauth add ajshedivy/ibmi-agent-skills configurationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query system configuration including system values, hardware resources, device status, environment variables, and JVM settings using SQL services from QSYS2 and SYSTOOLS.
The ibmi CLI is the primary tool for executing configuration queries. Set SKILL_DIR to this skill's installed location (the directory containing this SKILL.md file):
# SKILL_DIR = directory containing this SKILL.md
# Examples: ./skills/configuration, ~/.claude/skills/configuration
ibmi tools --tools "$SKILL_DIR/tools/" --toolset configuration_default
ibmi tool get_system_values --tools "$SKILL_DIR/tools/"
ibmi sql "SELECT * FROM QSYS2.SYSTEM_VALUE_INFO WHERE SYSTEM_VALUE_NAME = 'QSECURITY'"
ibmi tool get_security_system_values --tools "$SKILL_DIR/tools/"
ibmi tool get_system_value --tools "$SKILL_DIR/tools/" --sysval-name QSECURITY
ibmi tool get_hardware_resources --tools "$SKILL_DIR/tools/"
ibmi tool get_configuration_status --tools "$SKILL_DIR/tools/"
The tools/configuration.yaml file provides 7 ready-to-use tools:
| Tool | Description |
|------|-------------|
| get_system_values | System values with category filtering |
| get_system_value | Single system value lookup by name |
| get_security_system_values | Security-related system values |
| get_hardware_resources | Hardware resource inventory with status filter |
| get_configuration_status | Controller, device, and line status |
| get_environment_variables | System and job environment variables |
| get_jvm_info | Active JVM heap, GC, and thread information |
ibmi tool <tool_name> --tools "$SKILL_DIR/tools/" # Execute
ibmi tool <tool_name> --tools "$SKILL_DIR/tools/" --dry-run # Preview SQL
ibmi tools show <tool_name> --tools "$SKILL_DIR/tools/" # View details
tools
Query, monitor, and analyze jobs on IBM i using SQL table functions via the ibmi CLI. Use when user asks about: (1) finding jobs by status, user, subsystem, or type, (2) monitoring active job performance (CPU, I/O, memory), (3) detecting long-running SQL statements, (4) analyzing lock contention, (5) checking job queues, (6) scheduled jobs, (7) job logs, (8) replacing WRKACTJOB, WRKUSRJOB, WRKSBSJOB, WRKSBMJOB commands, or (9) any IBM i work management task.
testing
Monitor IBM i system health including CPU, memory, disk, ASPs, system limits, and network status via SQL services. Use when user asks about: (1) CPU utilization or system status, (2) memory pool sizes or page faults, (3) disk capacity or ASP usage, (4) system limits approaching thresholds, (5) TCP/IP connections and network status, (6) system activity overview, (7) replacing WRKSYSSTS, WRKDSKSTS, WRKTCPSTS commands, or (8) any system health monitoring task.
development
Monitor and analyze IBM i storage resources including ASPs, disk units, temporary storage, user storage consumption, and NVMe devices via SQL services. Use when user asks about: (1) ASP capacity, usage, or health, (2) disk unit status or I/O performance, (3) temporary storage consumption by jobs, (4) storage used per user profile, (5) NVMe device health, (6) IASP vary operations, or (7) replacing WRKDSKSTS, WRKSYSSTS storage info, or WRKSTG commands.
testing
Manage and analyze spooled files, output queues, and printer configurations on IBM i via SQL services. Use when user asks about: (1) listing or searching output queues, (2) viewing spooled file entries by queue, user, or status, (3) reading spool file content, (4) identifying top spool consumers or old spool files, (5) printer file definitions, (6) spool storage analysis, (7) replacing WRKSPLF, WRKOUTQ, WRKOBJLCK commands, or (8) any spool file management task.