servicenow-scriptsync

Synchronize local ServiceNow script files with a ServiceNow instance.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Xerrion/opencode --skill servicenow-scriptsync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: servicenow-scriptsync
Source: https://github.com/Xerrion/opencode/tree/main/skills/servicenow-scriptsync
Command: npx skills add https://github.com/Xerrion/opencode --skill servicenow-scriptsync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

sn-scriptsync integration enables safe and auditable synchronization of ServiceNow script files between local worktrees and a ServiceNow instance, ensuring consistent state across environments.

Core Features & Use Cases

  • Deterministic file syncing for Business Rules, Script Includes, UI scripts, and related artifacts.
  • Enforced session workflow and safety rules to prevent data loss and misconfiguration.
  • Change-tracking guidance and error recovery procedures for reliable collaboration.

Quick Start

Start a session by running check_connection, then clear_last_error, switch_context if needed, and finally run sync_now to push changes.

Frequently Asked Questions about servicenow-scriptsync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync local ServiceNow script files with a remote instance?

To sync ServiceNow script files, initiate a session using check_connection, clear_last_error, switch_context, and sync_now to push changes safely and maintain an auditable state across environments.

What is the required workflow for synchronizing ServiceNow Business Rules and Script Includes?

Synchronizing ServiceNow Business Rules and Script Includes requires an explicit session workflow: check_connection, clear_last_error, switch_context, and sync_now, ensuring deterministic file syncing and preventing data loss.

Can I manually edit the _map.json file during a ServiceNow script sync session?

No, manual edits to _map.json are prohibited during a ServiceNow script sync session. The enforced safety rules require using the designated session commands to maintain a consistent state across global and scoped apps.

How do I handle errors when pushing script changes to a ServiceNow instance?

For error recovery during script synchronization, run clear_last_error at the start of your session to reset the state, then re-attempt the sync_now command after verifying your connection with check_connection.

Does this script synchronization method support both global and scoped ServiceNow applications?

Yes, the script synchronization process supports both global and scoped ServiceNow applications, providing change-tracking guidance and enforcing safety rules to ensure consistent state across different application contexts.