ajshedivy
26 verified skills42 total stars
communication
Monitor and analyze IBM i network and communication resources including TCP/IP connections, network interfaces, routing, HTTP servers, and DNS configuration via SQL services. Use when user asks about: (1) active network connections and traffic, (2) network interface status and IP addresses, (3) routing tables, (4) HTTP server configuration and status, (5) TCP/IP settings and hostname, (6) NTP/SNTP time synchronization, (7) network attributes, or (8) replacing NETSTAT, WRKTCPSTS, CFGTCP, WRKhttpsrvr commands.
testing2
message-handling
Read and analyze message queues, system history log, reply lists, and message file definitions on IBM i via SQL services. Use when user asks about: (1) reading QSYSOPR or other message queues, (2) searching the system history log (QHST), (3) finding high-severity messages, (4) viewing the system reply list, (5) looking up message definitions (CPF, MCH, SQL messages), (6) message severity analysis, (7) replacing DSPMSG, DSPLOG, WRKMSGQ commands, or (8) any message handling or troubleshooting task.
testing2
security
Assess IBM i security posture including user privileges, object authorities, vulnerability detection, and function usage via SQL services. Use when user asks about: (1) user profiles with special authorities or limited capabilities, (2) object privileges and *PUBLIC authority exposure, (3) files vulnerable to trigger, rename, or library list attacks, (4) user impersonation vulnerabilities, (5) group profile membership, (6) function usage and access control, (7) security audit and compliance, or (8) replacing WRKOBJAUT, DSPUSRPRF, DSPAUTL commands.
development2
spool
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.
testing2
ibmi
Core skill for working with IBM i systems through the ibmi CLI. Covers text-to-SQL methodology, Db2 for i conventions, schema discovery, multi-system configuration, and — critically — agent scripting patterns (automatic JSON-when-piped, semantic exit codes, NDJSON streaming, dry-run planning, watch mode, multi-system workflows). Use this skill as the foundation for ANY IBM i task: running queries, exploring the database, configuring systems, writing bash/agent scripts that target IBM i, or composing pipelines that need structured output and reliable error handling.
tools2
librarian
Manage and query IBM i library lists, library contents, authorization lists, and object privileges via SQL services. Use when user asks about: (1) current library list configuration, (2) library contents and object inventory, (3) authorization lists and secured objects, (4) object-level privilege details, (5) library information and sizes, (6) system vs user library list entries, (7) replacing DSPLIBL, DSPLIB, DSPAUTL, DSPOBJAUT commands, or (8) any library management task.
development2
performance
Monitor IBM i performance including collection services, temporary storage, disk I/O metrics, and memory pool performance via SQL services. Use when user asks about: (1) collection services configuration or categories, (2) temporary storage usage by bucket or job, (3) disk I/O performance per unit, (4) memory pool page fault rates, (5) performance data collection settings, (6) replacing WRKSYSSTS performance views, or (7) any performance analysis or capacity planning task.
development2
product
Query IBM i software products, licensing, and product health via SQL services. Use when user asks about: (1) installed software products and versions, (2) product details for a specific product ID, (3) software products with load errors, (4) license compliance and usage limits, (5) unsupported or incompatible products, (6) replacing DSPSFWRSC, WRKLICINF, DSPPTF commands, or (7) any software product management task.
testing2
ptf
Monitor and analyze PTFs, PTF groups, and system patching status on IBM i via SQL services. Use when user asks about: (1) PTF group currency or update status, (2) finding outdated or critical PTF groups, (3) individual PTF details by product, (4) installed PTF group levels, (5) defective PTF checks, (6) PTF patching summaries, (7) replacing DSPPTF, WRKPTFGRP commands, or (8) any PTF management or compliance task.
testing2
storage
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.
development2
work-management
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.
tools2
system-health
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.
testing2
application
Query and explore IBM i application objects including CL commands, data areas, data queues, programs, environment variables, exit programs, and watches via SQL services. Use when user asks about: (1) CL command attributes or discovery, (2) data area values or inventory, (3) data queue status and messages, (4) program information (ILE/OPM), (5) environment variables, (6) registered exit programs, (7) watch sessions, (8) user spaces or user indexes, or (9) replacing DSPCMD, DSPDTAARA, DSPLIB, DSPPGM commands.
development2
backup-and-recovery
Query and analyze IBM i backup and recovery resources including save files, save file contents, media libraries, and tape cartridges via SQL services. Use when user asks about: (1) save file history or contents, (2) finding where an object was saved, (3) media library device status, (4) tape cartridge inventory, (5) backup verification, or (6) replacing DSPSAVF, WRKTAP, WRKMLBRM commands.
development2
configuration
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.
development2
database-application
Analyze IBM i SQL application behavior including error logs, statement parsing, SQLCODE lookups, and system limits. Use when user asks about: (1) SQL errors in applications or error log analysis, (2) most frequent SQL errors, (3) parsing SQL statements to find referenced objects, (4) looking up SQLCODE meanings, (5) properly delimiting SQL identifiers, (6) system size limits for files or indexes, or (7) objects approaching maximum capacity.
development2
database-performance
Monitor IBM i database performance including index statistics, maintained temporary indexes (MTIs), database monitors, query supervisor thresholds, and materialized query tables. Use when user asks about: (1) index usage or unused indexes, (2) maintained temporary indexes and whether to create permanent indexes, (3) database monitor configuration, (4) query supervisor thresholds, (5) MQT statistics and refresh status, or (6) tables with high MTI overhead.
data-ai2
database-plan-cache
Explore and manage the IBM i SQL plan cache including snapshots, event monitors, and procedure references. Use when user asks about: (1) plan cache services or procedures available, (2) plan cache snapshot files on the system, (3) plan cache event monitor status, (4) how to dump or manage the plan cache, (5) plan cache sizing or QSQSRVR job memory usage, or (6) SQL syntax for plan cache management operations.
data-ai2
database-utility
Manage and analyze IBM i database files, members, partitions, and objects using SQL services. Use when user asks about: (1) file inventory or file attributes in a library, (2) member or partition statistics like row counts, deleted rows, or data sizes, (3) object statistics including last used dates and sizes, (4) catalog health analysis or cross-reference checks, (5) comparing files between libraries, (6) finding objects that depend on a file, (7) validating data integrity, or (8) finding unused objects for cleanup.
tools2
ifs
Browse, search, read, and inspect files in the IBM i Integrated File System (IFS) including authorities, locks, and server shares. Use when user asks about: (1) listing IFS directory contents, (2) searching for files by name or pattern, (3) reading text file contents, (4) checking file authorities or permissions, (5) diagnosing file lock contention, (6) finding large files consuming disk space, (7) viewing NetServer file shares, or (8) replacing WRKLNK, DSPAUT, DSPLNK command output.
testing2
journal
Manage and inspect IBM i journals, journal receivers, journaled objects, journal entries, remote journals, and audit journal data marts. Use when user asks about: (1) listing journals or journal receivers, (2) which objects are journaled, (3) reading journal entries, (4) remote journal configuration and lag, (5) journal receiver sizes or chains, (6) SMAPP access path protection, (7) audit journal data marts, (8) journal storage consumption, or (9) replacing WRKJRN, DSPJRN, WRKJRNA command output.
testing2
migrate-while-active
Monitor IBM i Migrate While Active environments including migration manager state, library and IFS object tracking, migrated objects, compression factors, synchronization estimates, and network bandwidth. Use when user asks about: (1) migration status or progress, (2) library or IFS objects being migrated, (3) migration failures or errors, (4) completed migrations, (5) data compression ratios, (6) final synchronization time estimates, (7) migration network bandwidth, or (8) cutover planning.
development
mirror
Monitor Db2 Mirror for IBM i including replication status, cluster topology, NRG communication, RDMA links, replication criteria, resynchronization, reclone readiness, and flight recorder diagnostics. Use when user asks about: (1) mirror replication status or health, (2) cluster node topology, (3) NRG or RDMA link status, (4) takeover IP addresses, (5) replication inclusion/exclusion rules, (6) resynchronization progress, (7) reclone security objects, (8) mirror version compatibility, (9) flight recorder logging, or (10) ObjectConnect state.
testing
template-skill
Replace with description of the skill and when Claude should use it.
tools
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
tools
java
Monitor Java Virtual Machines running on IBM i including heap memory usage, garbage collection activity, thread counts, and JVM configuration. Use when user asks about: (1) active JVMs on the system, (2) JVM heap or memory consumption, (3) garbage collection performance, (4) Java thread counts, (5) JVM home directories or properties, (6) identifying JVMs at risk of OutOfMemoryError, or (7) replacing WRKJVMJOB command output.
development