Query-Tester

Deep skill for Splunk development, administration, app/add-on engineering, dashboards, SDK/REST integrations, and AI-facing tooling. ALWAYS use this skill when the task involves splunklib, Splunk REST API, search/jobs or jobs/export patterns, Python SDK, JavaScript SDK, SPL discovery/admin searches, knowledge objects, UCC add-on development, Dashboard Studio, Simple XML, Splunk MCP integration, AppInspect/package validation, or platform deployment automation. Trigger on: Splunk SDK, splunklib, SPL, Splunk REST API, jobs/export, add-on, UCC, modular input, alert action, Dashboard Studio, Simple XML, appinspect, saved searches, knowledge objects, MCP, Splunk admin, Splunk Cloud, Splunk Enterprise, Splunk automation.

Audits code in the Splunk Query Tester project for violations of project rules. Use this skill whenever you finish writing or modifying any file in this project — frontend TypeScript/React or backend Python — even if the task feels small. Also use it when the user asks to "audit", "check", "verify", or "review" any file. Do NOT skip this just because the change was minor. This skill is the enforcement gate for project conventions that are frequently violated and hard to catch later. Trigger for any of: new file created, existing file modified, feature completed, or user asking for a code review.