Skill

jarvis-refresh

Use when ServiceNow data needs refreshing. Presents available bundles and guides through the data pull process.

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Guide Chadron through refreshing ServiceNow data by bundle.

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 10, 2026

Actions

View Source View Plugin View on GitHub View README

Jarvis Data Refresh

Guide Chadron through refreshing ServiceNow data by bundle.

Environment Detection

This skill requires network access to ServiceNow instances and local connector scripts.

Claude Code (CLI): Full access — can run connector scripts, MCP queries, update status → proceed with all steps
Claude Cowork (web/desktop): Proxy-restricted, no outbound HTTP to ServiceNow → can only show freshness status and recommend which bundles to refresh. Tell Chadron: "Data refresh requires a Code session. Here's what's stale — queue this for your next Code session."

Process

Step 1: Load Refresh Configuration

Read from workspace root (use CLAUDE.md canonical root on Mac; in Cowork use mounted workspace at the path shown in your environment):

Jarvis/status.json - Current freshness and bundle definitions
servicenow_data/config/servicenow_config.json - Instance credentials and connection config

Step 2: Assess Current Freshness

Calculate days since last pull for each instance. Present freshness status.

Step 3: Present Bundle Menu

Show available refresh bundles from status.json with current state:

DATA REFRESH MENU
─────────────────────────────────
Bundle              Tables  Last Refreshed
─────────────────────────────────
[1] ITSM Core       8       [date or NEVER]
[2] Administration  4       [date or NEVER]
[3] Catalog         5       [date or NEVER]
[4] Security        2       [date or NEVER]
[5] Knowledge       1       [date or NEVER]
[6] Integration     2       [date or NEVER]
[7] Assignment      1       [date or NEVER]
[8] CMDB            1       [date or NEVER]
[9] Changes         1       [date or NEVER]
[F] Full Refresh    ALL     [date or NEVER]
─────────────────────────────────
Recommendation: [suggest which bundle based on staleness]

Which bundle? (enter number or F)

Step 4: Execute Refresh

After Chadron selects a bundle:

Check if ServiceNow connector script exists at scripts/servicenow/
If MCP server is configured, use live API queries
If no MCP, guide Chadron through manual export steps or run the connector script
After data lands, update Jarvis/status.json with new pull timestamp

Step 5: Confirm

Report what was refreshed, record count, and any errors encountered.

Important

Always check credentials exist before attempting connection
If proxy-restricted (Cowork VM), note that outbound HTTP may fail
Never store credentials in logs or output