Run any Skill in Manus with one click

iterm-notify

Stars8

Forks2

UpdatedMarch 16, 2026 at 06:11

macOS desktop notifications and iTerm2 badge management for Claude Code lifecycle events. Not a slash command — this plugin provides hook scripts. See README for wiring instructions.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

harnessprotocol

harnessprotocol/harness-kit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	iterm-notify
description	macOS desktop notifications and iTerm2 badge management for Claude Code lifecycle events. Not a slash command — this plugin provides hook scripts. See README for wiring instructions.
user-invocable	false

iterm-notify

Provides notify.sh — a hook script that fires on Claude Code Notification and Stop events.

Not a slash command. Wire it in ~/.claude/settings.json — see README.

What it does

On Notification (Claude needs attention):

Bounces the iTerm2 dock icon once
Sets an iTerm2 badge: <topic> ⚡ (or just ⚡ if no topic file)
Sends a macOS desktop notification via terminal-notifier with a click-to-focus action

On Stop (Claude finished):

Clears the iTerm2 badge

Prerequisites

macOS with iTerm2
terminal-notifier: brew install terminal-notifier
jq: brew install jq

Wiring

See README for setup instructions.

More from this repository

same repository

research

harnessprotocol/harness-kit

Use when user invokes /research command with any source — URL, GitHub repo, YouTube video, podcast, Reddit post, academic paper, documentation page, product site, local file, or empty. Processes and indexes research materials with raw source preservation and topic-level synthesis coalescing. Do NOT use for quick factual questions — use /explain instead.

2026-07-038

dependabot-sweep

harnessprotocol/harness-kit

Use when the user wants to fix, address, clear, or resolve open Dependabot security/vulnerability alerts for a repository, end to end. Fetches open alerts via the gh CLI, fixes them per ecosystem (pnpm/npm overrides + lockfile regen, cargo update, pip/go/bundler), verifies with audit and frozen-lockfile installs, then branches → commits → pushes → opens a PR, and squash-merges once CI is green — escalating only when a fix carries breaking-change risk or can't be resolved. Trigger on "/dependabot-sweep", "address the dependabot alerts", "fix the security vulnerabilities", "clear the dependabot alerts", "handle the dependency vulnerabilities", "sweep dependabot".

2026-06-058

rubber-ducky

harnessprotocol/harness-kit

Use when you've planned a non-trivial change and are about to implement it, finished a complex or multi-file piece of work, just wrote tests, or are stuck on repeated failures — and any time the user says "rubber duck this", "rubber ducky", "get a second opinion", "sanity-check my plan", "poke holes in this", "what am I missing", "critique my approach", "review this before I build it", or "/rubber-ducky". Spawns independent read-only critics on DIFFERENT Claude models than the one driving the session to catch blind spots, design flaws, and substantive bugs while course corrections are still cheap. Skip it only for small, obvious, well-understood changes. Do NOT use for reviewing a finished diff or PR — use /review for that; rubber-ducky pressure-tests your own in-progress thinking before and during implementation.

2026-06-058

harness-docs

harnessprotocol/harness-kit

Harness Kit documentation — installation, plugin catalog, creating plugins, cross-harness setup, architecture, and FAQ. Use when working with or configuring harness-kit plugins, understanding the plugin/skill system, installing slash commands, setting up AI coding tool configuration, answering questions about the plugin marketplace, writing SKILL.md files, using harness.yaml, or integrating with Copilot, Cursor, or Codex. Do NOT use for general Claude Code questions unrelated to harness-kit.

2026-04-188

memory

harnessprotocol/harness-kit

Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.

2026-03-278

frontend-design

harnessprotocol/harness-kit

Use when user asks to build a web component, page, or application, or when the task involves frontend design, HTML/CSS generation, or UI layout. Applies specific rules for typography, OKLCH color, layout, motion, interaction, and UX writing to produce distinctive, production-grade interfaces that avoid generic AI aesthetics.

2026-03-188

name	iterm-notify
description	macOS desktop notifications and iTerm2 badge management for Claude Code lifecycle events. Not a slash command — this plugin provides hook scripts. See README for wiring instructions.
user-invocable	false

iterm-notify

Provides notify.sh — a hook script that fires on Claude Code Notification and Stop events.

Not a slash command. Wire it in ~/.claude/settings.json — see README.

What it does

On Notification (Claude needs attention):

Bounces the iTerm2 dock icon once
Sets an iTerm2 badge: <topic> ⚡ (or just ⚡ if no topic file)
Sends a macOS desktop notification via terminal-notifier with a click-to-focus action

On Stop (Claude finished):

Clears the iTerm2 badge

Prerequisites

macOS with iTerm2
terminal-notifier: brew install terminal-notifier
jq: brew install jq

Wiring

See README for setup instructions.