ServiceNow Agent

**Judgement:** A strong, well-scoped ServiceNow integration focused on **safe, read-only data access**. It is well-suited for investigative, analytical, and audit-style workflows, but intentionally does **not** support any record creation or updates. **Strengths & Fit** - Covers most read scenarios: incidents/records, schema, history, attachments, aggregates, and catalog. - CLI interface with clear flags and examples makes it predictable for agents to use. - Schema and history commands are particularly valuable for debugging, analysis, and summarization tasks. **Key Risks & Limitations** - **Data sensitivity:** Although read-only, it can access potentially sensitive ServiceNow data (tickets, comments, attachments). Use only in trusted environments with appropriate access controls. - **No write operations:** Cannot automate ticket creation, updates, or workflow actions; this is by design but may limit automation scenarios. - **Payload/latency risk:** Large queries without conservative `sysparm_limit` or `sysparm_fields` may cause slow responses or large outputs. - **Attachment handling:** Binary downloads require care in where/how they are stored and analyzed. **Recommended Scenarios** - Triage and investigation of incidents/requests, including reading full conversation history and key fields. - Building lightweight, agent-driven reporting or dashboards using aggregate stats rather than bulk exports. - Catalog item discovery and review for support agents or catalog managers. - Technical troubleshooting aided by schema inspection and attachment retrieval. Overall, this skill is a **good fit for read-only ServiceNow exploration, analysis, and summarization**, with low operational risk but a natural ceiling on automation due to the lack of write capabilities.