Skill

jarvis-catalog

Use when designing ServiceNow catalog items with field-level specifications, approval workflows, and fulfillment automation. Supports both offline design and live creation via MCP tools.

npx claudepluginhub chadronbryant/napa-cowork-plugins --plugin jarvis

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Design and build ServiceNow service catalog items with full specifications.

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Jarvis Catalog Item Designer

Design and build ServiceNow service catalog items with full specifications.

Context

Workspace root: resolved from CLAUDE.md canonical root. In Cowork sessions, use mounted workspace (visible in session environment).
Analysis data: servicenow_data/napaanesthesiatest/
Catalog workbook: ITSM Process and Standards/00 - Deliverables/Catalog_Design_Workbook.xlsx
Existing catalog: servicenow_data/napaanesthesiatest/catalog_items.json

Process

Step 1: Identify Catalog Need

Top catalog opportunities (from analysis):

Password Reset / Account Unlock
Software Access Request
Distribution List Management
New Hire IT Setup
VPN Access Request
Equipment Request
Shared Mailbox Access
Security Group Modification

Step 2: Design Specification

CATALOG ITEM SPECIFICATION
─────────────────────────────────
Name:           [Item name]
Category:       [Parent category]
Short Desc:     [One-liner for portal display]
─────────────────────────────────
VARIABLES (Form Fields)
Order | Name          | Type       | Required | Options
──────┼───────────────┼────────────┼──────────┼────────
  100 | requested_for | reference  | Yes      | sys_user
  200 | [field]       | [type]     | [Y/N]    | [details]
─────────────────────────────────
APPROVAL: [Manager / Auto-approve / Multi-level]
FULFILLMENT: [Manual task / Flow Designer / Script]
ASSIGNMENT: [Group name]
SLA: [Expected completion time]
─────────────────────────────────

Step 3: Variable Types

Type	Use Case
`single_line_text`	Short text input
`multi_line_text`	Descriptions, justifications
`select_box`	Dropdown with fixed options
`reference`	Lookup to another table
`checkbox`	Boolean toggle
`date`	Date picker
`integer`	Numeric input
`email`	Email with validation

Step 4: Build Options

Option A: Offline Specification — Save design for later implementation.

Option B: Direct to ServiceNow via MCP If MCP server is connected, use catalog_builder tools:

list_catalog_categories — check existing categories
create_catalog_category — create if needed
update_catalog_item — configure catalog item
create_catalog_item_variable — add form fields (one per call)
list_catalog_item_variables — verify

MCP Console shortcut: Use AI Assist:

"List all active catalog categories"
"Create a catalog item called Password Reset in IT Services"
"Add a reference variable for requested_for on item [sys_id]"

Design Principles

Structured > Free-text: Every field captures specific data
Progressive disclosure: Show complex fields only when relevant
Sensible defaults: Pre-fill where possible
Clear descriptions: Help text on every non-obvious field
Approval proportional to risk: Low-risk auto-approve; high-risk multi-level
Measurable outcomes: Track fulfillment time, automation rate