菜单
Generates GlideRecord queries, Script Include classes, and client scripts for ServiceNow legacy scripting. Use for Business Rules, Scheduled Jobs, server-side Script Includes, and client-side g_form/g_user scripts. Redirects to sn-sdk-fluent when Fluent SDK is detected in the workspace.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Expert-level agent skills for the entire ServiceNow development ecosystem. Covers Fluent SDK metadata (.now.ts), legacy scripting (GlideRecord, Script Includes, Client Scripts, g_form), and CLI setup (now-sdk auth, build, install). Use when generating, reviewing, or explaining any ServiceNow code.
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.
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.
| name | sn-scripting |
| description | Generates GlideRecord queries, Script Include classes, and client scripts for ServiceNow legacy scripting. Use for Business Rules, Scheduled Jobs, server-side Script Includes, and client-side g_form/g_user scripts. Redirects to sn-sdk-fluent when Fluent SDK is detected in the workspace. |
| compatibility | Designed for Claude Code, Cursor, VS Code Copilot, Antigravity, Codex, and similar AI coding tools. |
| license | Apache-2.0 |
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.
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 |
| Script | When to use |
|---|---|
scripts/validate-script.sh | When validating a ServiceNow script file for common issues before deploying |
Use these as structural templates — only read the example that matches your target type, do not pre-load all examples:
| File | Demonstrates |
|---|---|
assets/examples/gliderecord-crud.js | Complete GlideRecord CREATE, READ (single and multi), UPDATE, DELETE with correct getValue() usage |
assets/examples/script-include-class.js | Script Include using Class.create() pattern with initialize(), utility methods, and type property |
assets/examples/client-script-gform.js | Client Script onLoad/onChange handlers using g_form.getValue(), g_form.setMandatory(), g_user.hasRole() |
Never use GlideRecord when ServiceNow Fluent SDK is present.
If the workspace contains now.config.json, .now.ts files, or imports from @servicenow/sdk/core,
the developer is working in a Fluent SDK application. Stop and redirect:
"I can see you're working in a Fluent SDK project. Use the sn-sdk-fluent skill to generate
typed metadata definitions instead of GlideRecord scripts. GlideRecord is the legacy scripting
API and does not work inside Fluent SDK .now.ts files."
GlideRecord is server-side only — never generate GlideRecord in a Client Script. Use GlideAjax.
Always call query() before next() — while(gr.next()) without gr.query() never executes.
Use getValue() in loops — gr.field_name returns a pointer; gr.getValue('field_name') returns the string value.
Only use documented API methods — do not invent methods like gr.getField(), gr.setQuery(), or gr.addOrder().
references/gliderecord.md for CRUD patterns, references/server-side.md for Script Include structure and Business Rule context variables.references/client-side.md for g_form/g_user/g_list APIs. Never generate GlideRecord in a client script (Hard Rule 2).assets/examples/ as working templates.references/gliderecord.md documented API (Hard Rule 5).scripts/validate-script.sh <file> to check for GlideRecord in client scripts, bare setAbortAction, and g_form misuse.