---
description: Weekly tooling discovery. Scans OpenCode docs/changelog, awesome-opencode, npm opencode-* packages, and major MCP servers for new releases worth trying. Outputs a Monday-morning summary. Triggered by '/tooling-watch' or auto Monday 8am via launchd.
---

# personal-tooling-watch

The OpenCode ecosystem moves fast. This skill scans weekly so good tools don't get missed.

## Trigger phrases

- "What's new in OpenCode?"
- "Anything new worth trying?"
- `/tooling-watch`
- Auto: Monday 8am via launchd

## Sources scanned

1. **OpenCode docs** — https://opencode.ai/docs (recent changes flagged in changelog)
2. **OpenCode releases** — https://github.com/anomalyco/opencode/releases (last 7 days)
3. **OpenCode plugin ecosystem** — https://opencode.ai/docs/ecosystem/
4. **awesome-opencode** — https://github.com/code-yeongyu/awesome-opencode (commits last 7 days)
5. **npm `opencode-*` packages** — `https://registry.npmjs.org/-/v1/search?text=opencode&size=50` (sorted by recently-published)
6. **MCP servers updates** — major ones Josh has installed (filesystem, time, context7, gh_grep, firecrawl, linkedin-mcp-server, etc.)

## Process

### Phase 1 — Parallel fetch (Tier 2 sub-agents)

Fire `research` sub-agents in parallel, one per source. Each returns ≤300 tokens of "what changed in the last 7 days".

### Phase 2 — Synthesize (Tier 3 main, Sonnet)

Group findings by category:

- **Major OpenCode release** — version + headline features
- **New plugins** — name + description + worth trying?
- **New MCPs** — name + description + worth trying?
- **Updates to installed tools** — any breaking changes?
- **Trending discussion** — Reddit / HN / Twitter signal on OpenCode

### Phase 3 — Recommend

For each item, classify:

- 🟢 Try this week — clear value, low cost
- 🟡 Watch — interesting but unproven
- 🔴 Skip — not relevant to Josh's setup

### Phase 4 — Output

```markdown
# Tooling Watch — Week of YYYY-MM-DD

## Headlines

[2-3 sentences synthesizing the week]

## OpenCode core

- [version] released [date]: [headline features]
- [Any breaking changes Josh should know about]

## New plugins worth trying

🟢 **[plugin-name]** — [1-line description]
- Why: [reason]
- Install: [command]

🟡 **[plugin-name]** — ...

## New MCPs worth trying

🟢 **[mcp-name]** — ...

## Updates to installed tools

- [tool] [old-version → new-version]: [what changed, breaking?]

## Trending in the community

- [discussion / pattern people are excited about]

## Recommended action this week

[The top 1-2 things to try]
```

Save to `~/.personal/reports/tooling-watch-{date}.md`.

If running auto Monday 8am: also draft a Gmail draft to Josh's personal email so he sees it in his inbox.

## Discipline

- **Don't propose installing everything.** The community ships fast; signal-to-noise is low. Use the 🟢/🟡/🔴 ruthlessly.
- **Reference Josh's existing setup.** "You already have X — this new tool overlaps, here's the diff" is more useful than "here's a new tool."
- **Note breaking changes prominently.** A patch update to context7 that breaks the tool integration matters more than 5 new shiny plugins.