agentsclimarketplace

Servicenow

Skill jacebenson/jsn/skills/servicenow

Install
npx -y skills add jacebenson/jsn --skill servicenow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Interact with ServiceNow instances via the jsn CLI. Use when working with ServiceNow development, administration, or data exploration. Handles tables, records, business rules, flows, script includes, ACLs, update sets, and more. Triggered by ServiceNow URLs (service-now.com, servicenow.com) or when the user mentions ServiceNow, jsn, servicenow, or related terms like tables, records, business rules, flows, script includes, ACLs, update sets, or encoded queries.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.0 KB, 877 tokens by cl100k_base, as published. Nobody here has run it

Jace's ServiceNow CLI (jsn)

Explore and manage ServiceNow instances. Interactive paginated pickers with server-side search on all list commands.

Discovery

jsn --help                # All commands grouped by domain
jsn <command> --help      # Flags, subcommands, and examples

Interactive Picker

All list subcommands use a paginated interactive picker in TTY mode:

  • Arrow through items (10 per page)
  • Type to search (server-side LIKE query)
  • Scroll past last loaded item to load next page
  • Enter to select, Esc to cancel
  • Falls back to table output with --json

Agent Rules

  1. Output modes--json when parsing data; text when presenting to humans
  2. Use sys_id for updates — All update/delete operations require sys_id
  3. Check auth first — Run jsn auth status before operations
  4. NEVER logout — Only run jsn auth logout if the user explicitly asks
  5. Use --profile <name> to target a specific instance, or jsn profiles use <name> to change default
  6. Before using eval or rest — Ask: "Is there a more specific jsn command?" Prefer specific over generic over escape hatch over eval.
  7. CONFIRM before destructive operations — Show what will be created/updated/deleted and ask for approval.

Command Hierarchy

Pick the most specific tool for the job. Never default to eval — it's the last resort:

  1. Specific commandsjsn flows, jsn rules, jsn catalogitems, etc.
  2. jsn records --table <name> — generic CRUD on any table
  3. jsn rest — raw Table API escape hatch
  4. jsn eval — ⚠️ LAST RESORT ONLY
  5. Ask the human — if none of the above work

Key Commands

DomainCommands
Coreincidents, changes, requests, tasks
Catalogcatalogitems list/show/create — items with variables and flow info
Automationflows, actions, rules, workflows, triggers, scheduledjobs
Accessacls, b4rules, roles, groups, users
UXforms (section/element layout), lists, clientscripts, uipolicies
Datatables, columns, includes, logs, properties, records
Configsetup, auth, profiles, updatesets, scopes
Developereval, rest, skill, version

jsn rest examples

# Query any table by name
jsn rest --table incident --query "active=true" --limit 5 --json

# GET a single record
jsn rest --table incident --sys-id abc123... --json

# Raw endpoint access
jsn rest "/api/now/table/incident?sysparm_limit=3" --json

Troubleshooting Field Behavior

Check order (priority):

  1. Before-query business rulessys_script with when=before, action=query
    jsn b4rules list --query "collection=sys_user"
    
  2. ACLsjsn acls list --query "name=incident"
  3. Dictionary overridesjsn records list --table sys_dictionary --query "name=incident^element=caller_id"
  4. Client scripts / UI policies — form-level field behavior

Configuration

~/.config/servicenow/
├── config.json               # Profiles and settings
└── credentials.json          # Auth tokens (fallback)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.