From jarvis
Use when managing, viewing, or executing tasks from the Jarvis task registry. Supports listing tasks, running individual tasks, and viewing task history.
npx claudepluginhub chadronbryant/napa-cowork-plugins --plugin jarvisThis skill uses the workspace's default tool permissions.
Manage and execute tasks from the Jarvis task registry.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Manage and execute tasks from the Jarvis task registry.
Jarvis/tasks.jsonJarvis/architecture.mdJarvis/analysis/ (analysis tasks), Jarvis/audit/ (maintenance tasks)Read Jarvis/tasks.json to load all task definitions.
Present this menu to Chadron:
JARVIS TASK MANAGER
─────────────────────────────────
[1] List All Tasks View tasks by category with status
[2] Run a Task Execute a specific task by name or ID
[3] Run Category Execute all tasks in a category
[4] Task History View recent task execution results
[5] Quick Run Run a recommended task based on current state
─────────────────────────────────
Read Jarvis/tasks.json and display tasks grouped by category:
DATA OPERATIONS
─────────────────────────────────
refresh-itsm-core Refresh ITSM Core Data [10 min] Last: never
refresh-full Full ServiceNow Refresh [30 min] Last: never ⚠ Approval
refresh-catalog Refresh Catalog Data [8 min] Last: never
ANALYSIS & REPORTING
─────────────────────────────────
analyze-incident-patterns Analyze Incident Patterns [15 min] Last: never
analyze-resolution-times Analyze Resolution Times [12 min] Last: never
analyze-automation-scan Automation Opportunity Scan [20 min] Last: never
generate-weekly-report Weekly Status Report [10 min] Last: never 📅 Mon
generate-weekly-digest Weekly Digest [8 min] Last: never 📅 Fri
[... continue for all categories]
When Chadron specifies a task:
approval_required: true, explicitly confirm before proceedingagent_prompt exactly as writtenlast_run and last_status in tasks.json when completeWhen executing a task:
agent_prompt field as your primary instructionstools_requiredoutputs.filesoutputs.brain_updatesTASK COMPLETE: [task name]
─────────────────────────────────
Duration: [actual time]
Status: ✓ Success / ✗ Failed
Output: [list of files created/updated]
Brain Updates: [list of brain files modified]
─────────────────────────────────
Update tasks.json with:
last_run: current ISO timestamplast_status: "success" or "failed"List categories and run all tasks in the selected category sequentially:
approval_required: true (list them as skipped)Read tasks.json and display all tasks with non-null last_run:
RECENT TASK RUNS
─────────────────────────────────
[date] analyze-incident-patterns ✓ Success 12 min
[date] check-data-freshness ✓ Success 1 min
[date] refresh-itsm-core ✗ Failed 3 min
─────────────────────────────────
Assess current state and recommend the most valuable task to run next:
status.json — check data freshnessrecommendations.md — check top prioritiestasks.json — check what hasn't been run recentlyRecommend based on:
Present the recommendation and ask to proceed.
If Chadron describes a new task to add: