snu-artifacts

Standardize ServiceNow artifact mapping into local file structures.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/A865732/PDI-SNSyncScript --skill snu-artifacts-a865732
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snu-artifacts
Source: https://github.com/A865732/PDI-SNSyncScript/tree/main/agentrules/skills/snu-artifacts
Command: npx skills add https://github.com/A865732/PDI-SNSyncScript --skill snu-artifacts-a865732

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves inconsistencies in how ServiceNow artifacts are mapped to local files, preventing structural errors and ensuring proper synchronization between local development environments and ServiceNow instances.

Core Features & Use Cases

  • Artifact Mapping: Provides strict conventions for mapping ServiceNow fields (scripts, HTML, CSS) to local files while excluding non-code configuration fields.
  • Workflow Guidance: Defines the correct sequence for creating new artifacts, managing scoped applications, and handling complex table metadata.
  • Use Case: When a developer needs to create a new Business Rule or Service Portal widget, this skill ensures the file structure is correct, mandatory references are identified, and the sync process remains stable.

Quick Start

Follow the established naming conventions and artifact creation workflows to ensure your local ServiceNow files are correctly structured for synchronization.

Frequently Asked Questions about snu-artifacts

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

FAQPage Schema
How do I map ServiceNow artifacts to local files for ScriptSync?

To map ServiceNow artifacts to local files, apply strict conventions that separate scripts, HTML, and CSS into local files while excluding non-code configuration fields to ensure reliable synchronization with your instance.

What is the correct workflow for creating a scoped ServiceNow application artifact?

Creating a scoped ServiceNow application artifact requires following a defined sequence to manage scope, validate table metadata, and identify mandatory reference dependencies before synchronizing to prevent deployment failures.

Why does my ServiceNow synchronization fail when adding new Business Rules?

ServiceNow synchronization fails when mandatory field requirements are unmet or table metadata and reference dependencies are invalid, requiring structural validation before syncing local files to the instance.

Can I synchronize Service Portal widgets using standardized local file structures?

Yes, you can synchronize Service Portal widgets by enforcing correct local file structures for client scripts, HTML templates, and CSS styles while validating mandatory references to maintain sync stability.

Does this approach to ServiceNow artifact management exclude non-code configuration fields?

Yes, this approach to ServiceNow artifact management explicitly excludes non-code configuration fields from local file mapping to focus strictly on standardizing scripts, templates, and styles for deployment synchronization.