sn-scripting
ServiceNow Legacy Scripting
ServiceNow legacy scripting uses the GlideRecord API for server-side data access, Script Include classes for reusable server-side logic, Business Rules for server-side automation, and g_form/g_user/g_list for client-side form manipulation. All APIs are described in the reference files below.
References
Read these files when you need them — do not pre-load all references at session start. Paths are relative to the skill root (the directory containing this SKILL.md file).
| File | When to Read |
|---|---|
references/gliderecord.md |
Generating or reviewing GlideRecord queries, CRUD operations, or addQuery/getValue patterns |
references/server-side.md |
Generating Script Includes, Business Rules, or using GlideSystem (gs.*) logging |
references/client-side.md |
Generating Client Scripts using g_form, g_user, or g_list; or any client-side form manipulation |
references/gotchas.md |
Before generating or reviewing any ServiceNow script — check for hallucination traps |
Scripts
More from aatrey882/servicenow-agent-skills
servicenow-agent-skills
>
14sn-sdk-fluent
Use when working with ServiceNow Fluent DSL (.now.ts files) — generating, reviewing, or explaining metadata definitions for tables, ACLs, business rules, UI pages, client scripts, script includes, flows, service portal widgets, and other ServiceNow metadata types. Covers all 6 column types, all $id-required types, and scope prefix reading from now.config.json.
2sn-sdk-setup
Use when setting up, configuring, building, or deploying with the ServiceNow SDK — scaffolding new projects, configuring Basic or OAuth authentication, converting existing applications, building and deploying to an instance, or validating a development environment. Covers all init templates, auth setup with named aliases, the build→deploy→verify lifecycle, and the check-environment script.
2