ワンクリックでManusで任意のスキルを実行

notification

スター41

フォーク2

更新日2026年6月18日 18:49

Fires a native macOS notification (via terminal-notifier) to grab the user's attention when an autonomous flow needs them - a pending clarification, a human gate, the end of a long step, a failure. Takes a title, a message, an optional tone (info/alert), and an optional subtitle. Clicking the notification focuses Kitty. Use when a command, skill, or subagent needs to reach the user outside the chat window. Triggers: "/notification", "notify the user", "alert via macOS".

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vmarcosp

vmarcosp/dotfiles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

notification

Fire one macOS notification. Always use the bin/notification script — it handles terminal-notifier, Kitty focus, and fallbacks.

notification "<title>" "<message>" [--tone info|alert] [--subtitle "<text>"] [--group <id>]

Options:

--tone alert → Basso sound + default subtitle "Atenção necessária" (use for failures, blockers, unexpected events)
--tone info → Glass sound (default, use for progress and gates)
--subtitle → line below the title
--group → group ID for deduplication/removal (default: claude-code)

To dismiss a notification programmatically after it's been acted on:

notification --remove [--group <id>]

Never let a missing notification block the flow. If bin/notification is not on PATH, fall back to:

osascript -e 'display notification "<message>" with title "<title>" sound name "<sound>"'

And if not on macOS, print 🔔 <title>: <message> to chat and move on.

このリポジトリの他の Skills

同じリポジトリ

implement

vmarcosp/dotfiles

Executes an implementation plan (from /spec) end to end: turns its Steps into a tracked checklist, works through them one at a time — implement, run the Step's Verify, check it off, commit — then runs the plan's overall Verification and delivers a PR. When the plan is one phase of a /phasing roadmap, delivery also writes the phase's carry-over fragment and flips its status in the roadmap. Invoking /implement is itself the go-ahead to execute; there's no separate approval gate. Use when the user wants to execute, build, or ship a plan that already exists, or invokes /implement.

2026-07-1141

phasing

vmarcosp/dotfiles

Turns settled PRD/TDD/ADR scope into an ordered set of phases, each sized to be exactly one /spec (one Approach, one Verify surface, one PR), organized as a dependency graph so parallel streams fall out of real technical dependency instead of being guessed upfront. Writes the roadmap to docs/roadmaps/<slug>/roadmap.md; each phase becomes its own /spec afterward. Use when the user wants to break a feature or system into phases, plan a rollout across multiple PRs, or invokes /phasing.

2026-07-1141

prd

vmarcosp/dotfiles

Writes or updates a Product Requirements Document (PRD) — a concise, best-practice description of what a system, feature, or subsystem does for its users, never how it's built. Takes its input from a /brainstorm convergence artifact, a /tdd document, or the user's own description of a feature. Use when the user wants a PRD, product requirements doc, or asks to turn a brainstorm or design into product requirements, or invokes /prd.

2026-07-1141

review

vmarcosp/dotfiles

Reviews a delivered change against its contracts — the /spec plan, the roadmap phase's boundary, binding ADRs, and test authenticity — and returns a verdict with blocking and advisory findings.

2026-07-1141

spec

vmarcosp/dotfiles

Writes or updates an implementation plan — a concise, actionable breakdown of how one change will be made: what recon (and any binding ADRs) found, the chosen approach, an ordered list of steps, and how each step (and the change as a whole) is verified done. Scoped to a single change, not a system (that's a TDD) and not user-facing behavior (that's a PRD) — the plan is the handoff artifact between deciding what to build and building it. Use when the user wants an implementation plan, asks to plan a feature, bugfix, or refactor before coding it, or invokes /spec.

2026-07-1141

tdd

vmarcosp/dotfiles

Writes or updates a Technical Design Document (TDD) — a description of how a system, subsystem, or component is put together. Not a proposal: states the design rather than building a case for it, and references the ADRs, PRDs, or brainstorm docs that justify it instead of restating them. Grounds every part in the most reliable source available — code where it's built, anchor docs where it isn't yet — and flags unbuilt pieces inline instead of labeling the whole document. Use when the user asks for a technical design document, architecture document, or system design doc, or wants a system's (or part of a system's) architecture written down with diagrams.

2026-07-1141

name	notification
description	Fires a native macOS notification (via terminal-notifier) to grab the user's attention when an autonomous flow needs them - a pending clarification, a human gate, the end of a long step, a failure. Takes a title, a message, an optional tone (info/alert), and an optional subtitle. Clicking the notification focuses Kitty. Use when a command, skill, or subagent needs to reach the user outside the chat window. Triggers: "/notification", "notify the user", "alert via macOS".
user-invocable	true

notification

Fire one macOS notification. Always use the bin/notification script — it handles terminal-notifier, Kitty focus, and fallbacks.

notification "<title>" "<message>" [--tone info|alert] [--subtitle "<text>"] [--group <id>]

Options:

--tone alert → Basso sound + default subtitle "Atenção necessária" (use for failures, blockers, unexpected events)
--tone info → Glass sound (default, use for progress and gates)
--subtitle → line below the title
--group → group ID for deduplication/removal (default: claude-code)

To dismiss a notification programmatically after it's been acted on:

notification --remove [--group <id>]

Never let a missing notification block the flow. If bin/notification is not on PATH, fall back to:

osascript -e 'display notification "<message>" with title "<title>" sound name "<sound>"'

And if not on macOS, print 🔔 <title>: <message> to chat and move on.