Skill

jarvis-recommend

Use when Chadron asks what to work on next. Shows prioritized recommendations with context and estimated effort.

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Present prioritized next actions based on current project state.

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 Recommendations

Present prioritized next actions based on current project state.

Process

Step 1: Load Context (in parallel)

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

Jarvis/recommendations.md - Current priority list

Jarvis/status.json - Data freshness (affects what's actionable)

Jarvis/needs.md - Blockers that limit recommendations

memory/history/recent-activity.md - What was done recently (avoid repeats)

Step 2: Filter and Rank

Silently evaluate:

Which recommendations are currently actionable (not blocked by needs)?

Which have the highest business impact?

Which build on recent momentum from last session?

Are there any time-sensitive items (stale data, upcoming presentations)?

Step 3: Present Recommendations

Use this format:

JARVIS RECOMMENDATIONS | [date] ───────────────────────────────── READY NOW (no blockers) 1. [Action] - [why it matters] - [estimated effort] 2. [Action] - [why it matters] - [estimated effort] 3. [Action] - [why it matters] - [estimated effort] BLOCKED (needs input from you) - [Action] - blocked by: [what's needed] RECENT WINS (momentum to build on) - [What was accomplished recently] ───────────────────────────────── My recommendation: [one-liner on what to tackle first and why]

Step 4: Await Direction

Wait for Chadron to pick a direction. If he asks for detail on any item, provide full context including relevant data, files involved, and step-by-step approach.

Positioning

Always frame recommendations using proposal language:

"I'd recommend..." / "This could save..." / "Worth evaluating..."

Never: "We should deploy..." / "I'll implement..."

ROI in hours saved at $50/hr blended rate, never headcount