
from nowdev-ai-toolbox8
Guidance and patterns for writing ServiceNow server-side code: Script Includes, JavaScript modules, system APIs (gs.*), session management, event queueing, and
ServiceNow Server Script Logic provides concrete, platform-aware guidance for authoring server-side code on the Now Platform. It explains scoped-app restrictions, safe replacements for blocked APIs, common system operations (user context, logging, properties), event queue usage, session and impersonation handling, and patterns for bridging older Script Include patterns with newer Fluent/SDK module approaches. The skill is focused on practical, deployable patterns rather than theoretical best practices.
Trigger this skill when authoring or reviewing server-side scripts in ServiceNow: Script Includes, Business Rules, Script Actions, Scheduled Jobs, and Fluent SDK modules. Use it when migrating classic Script Includes to module-based approaches, when handling scoped-app API limitations, or when implementing event-driven automation and safe impersonation flows.
Best used by agents or humans familiar with ServiceNow development and able to edit platform code (Glide APIs).
Skill body (SKILL.md) could not be fetched — the stored GitHub URL has a case mismatch (danielmadsendk vs DanielMadsenDK) and the source_path 'servicenow-script-server-logic' no longer exists in the repo (likely renamed to nowdev-ai-toolbox-servicenow-sdk). No scripts were present. Based on the short description and tags, this was intended as a ServiceNow server-side scripting guidance skill covering Script Includes, gs.* APIs, session management, and event-driven patterns. Without the actual content, only a minimal assessment is possible.
Stale/broken DB entry: content fetch failed due to URL case sensitivity issue. The skill slug in DB references a path that no longer exists in the GitHub repo. This skill may be a duplicate or predecessor of 'nowdev-ai-toolbox-servicenow-sdk'. Low architecture and quality scores reflect missing content, not poor quality — the skill body is entirely unavailable for review. Security score reflects no visible issues in available metadata/tags.