snu-artifacts

Name: snu-artifacts
Availability: InStock
Author: arnoudkooi

Map ServiceNow artifacts to local file structures and naming conventions.

53|38|Updated Dec 17, 2018

Search Tags:#artifacts #naming-conventions #mapping #servicenow #file-structure #map-json

Ready to run

npx skills add https://github.com/arnoudkooi/sn-scriptsync --skill snu-artifacts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: snu-artifacts
Source: https://github.com/arnoudkooi/sn-scriptsync/tree/main/agentrules/skills/snu-artifacts
Command: npx skills add https://github.com/arnoudkooi/sn-scriptsync --skill snu-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps ServiceNow artifacts to a clear local file structure and naming conventions, enabling predictable offline development and easier rebuilds from ServiceNow data.

Core Features & Use Cases

Defines conventions for file naming and the organization of artifacts by table, scope, and artifact type.
Documents the mapping between ServiceNow artifacts and local map.json / structure.json representations to support consistent syncing.
Guides creation, naming, and organization of new artifacts to minimize misconfiguration and manual work.

Quick Start

Install or sync the artifact mapping tool and review the resulting map.json to begin organizing your ServiceNow artifacts.

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 a local file structure for offline development?▼

You can map ServiceNow artifacts to a local file structure by applying consistent naming conventions across tables, scopes, and artifact types. This approach generates map.json and structure.json files to enable predictable offline work and accurate synchronization.

What is the best way to organize ServiceNow artifact files locally by scope and table?▼

The best way to organize ServiceNow artifact files locally is to map them using structure.json representations that group items by table, scope, and artifact type. This ensures consistent file naming and minimizes manual configuration during synchronization.

Can I synchronize new ServiceNow artifact creation using a local map.json file?▼

Yes, you can synchronize new ServiceNow artifact creation using a local map.json file. The mapping captures field requirements, mandatory references, and artifact-specific script mappings to drive correct artifact creation and linkage during offline workflows.

How does mapping ServiceNow artifacts to structure.json prevent misconfiguration during rebuilds?▼

Mapping ServiceNow artifacts to structure.json prevents misconfiguration by enforcing predictable file naming and organization conventions before rebuilds. This captures mandatory references and script mappings to ensure accurate linkage and reduce manual setup work.

Do I need map.json and structure.json files to maintain ServiceNow naming conventions across multiple scopes?▼

You need map.json and structure.json files to maintain ServiceNow naming conventions across multiple scopes because they document the mapping between artifacts and local representations. This supports consistent syncing and organization across various artifact types.