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

amos-notify

スター0

フォーク0

更新日2026年4月20日 23:28

Post a message to a node's source system through its adapter. For a `@github:...` node, this creates a comment on the referenced issue. Use when the user wants to share status, results, or context with everyone watching the upstream tracker — not for local scratch notes. The message is visible to anyone with access to the tracker.

インストール

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

Manusで実行

ソース

tatolab

tatolab/amos

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

ダウンロード

Manusで実行

Adapters

github (builtin) — posts the message as a new comment on the GitHub issue named by the node. Supports GitHub-flavored markdown (code fences, links, lists, checkboxes).

Examples

Short status update:

"$HOME/.local/bin/amos" notify "@github:tatolab/streamlib#319" "Phase 1 merged. Starting phase 2 now."

Longer comment with markdown — use a HEREDOC to keep the quoting sane:

MSG="$(cat <<'EOF'
## Progress update

- Landed the canonical-name migration (80 plan files).
- Reattached #322 under #319 (was silently orphaned by a stale rename).
- Added missing #369 / #370 edges under #326.

Next: working on #370 (xtask JTD discriminator).
EOF
)"
"$HOME/.local/bin/amos" notify "@github:tatolab/streamlib#319" "$MSG"

When to use

Reporting progress to everyone watching the issue
Closing-out notes when finishing a task
Flagging a blocker that needs the issue reporter's attention

When NOT to use

Notes meant only for yourself or the agent → put them in the plan file body instead.
Communicating privately with a teammate → use a DM, not an issue comment.
Anything sensitive → remember the tracker is visible to everyone with repo access.

Verification

After posting, the comment appears on the issue page. amos show "<node-name>" will re-fetch the issue and include the new comment in the resolved body.

このリポジトリの他の Skills

同じリポジトリ

amos-next

tatolab/amos

Pick up and execute the next ready-to-start issue from the focused milestone, end-to-end: announce, gate on user confirmation, branch, do the work, run the tests listed in the issue body, open a PR, report. This is the skill to invoke when the user says "continue", "next task", "what's next", "pick up where we left off", "work on the next issue", "keep going", or similar. It replaces any project-local PROMPT.md protocol.

2026-05-020

amos-file

tatolab/amos

File a new GitHub issue with a well-shaped body, the right milestone, and native dependency relationships, from a short natural-language intent. Use when the user says "file this", "open an issue for X", "create a ticket", "log this as a bug", when discussion surfaces a new task that should be tracked, or after the assistant offered to file something and the user confirmed. Infers milestone and labels; asks in chat whenever confidence is low.

2026-04-270

amos

tatolab/amos

Load when working with amos nodes — markdown files carrying `whoami: amos` frontmatter — or when the user refers to "the plan", "the DAG", "the roadmap", "the tickets", "what's next", or similar work-tracking concepts. Installs the amos conventions (canonical naming, node format, when to reach for which sub-skill) into context so amos-graph, amos-show, amos-create, and amos-notify can be used correctly. Does not run the CLI on its own.

2026-04-210

amos-focus

tatolab/amos

Set the milestone the user is currently working on. `amos next`, `amos blocked`, and `amos graph` scope their output to this milestone once set. Use when the user says "let's work on <milestone>", "focus on <milestone>", "switch to <milestone>", or wants to check which milestone is currently active. Accepts free-form milestone text — the tool resolves it against the adapter's known titles.

2026-04-200

amos-create

tatolab/amos

Scaffold a new amos node with proper frontmatter. Use when the user wants to add a new ticket, task, or plan entry tracked by amos. Produces a markdown file with the canonical `@github:<owner>/<repo>#<N>` name, a description, dependencies, and the adapter block.

2026-04-200

amos-graph

tatolab/amos

Print the amos dependency tree as a nested ASCII graph. Use when the user asks about open tasks, the roadmap, what's next, what's blocked, what depends on X, or wants a structural view of the plan. Returns every node with status and a short description; does NOT resolve `@github:...` references (use amos-show for full content). Trigger on phrases like "what's on my plate", "what's open", "show me the DAG", "what's blocking X", "what depends on Y", "where are we on <umbrella>".

2026-04-200

name	amos-notify
description	Post a message to a node's source system through its adapter. For a `@github:...` node, this creates a comment on the referenced issue. Use when the user wants to share status, results, or context with everyone watching the upstream tracker — not for local scratch notes. The message is visible to anyone with access to the tracker.
disable-model-invocation	true
argument-hint	<node-name> <message>
allowed-tools	Bash

"$HOME/.local/bin/amos" notify "<node-name>" "<message>"

<node-name> must be the canonical name: value of an amos node:

"$HOME/.local/bin/amos" notify "@github:tatolab/streamlib#326" "Dependency edges updated — #326 now sits behind #369 and #370 per the umbrella ordering."

Adapters

github (builtin) — posts the message as a new comment on the GitHub issue named by the node. Supports GitHub-flavored markdown (code fences, links, lists, checkboxes).

Examples

Short status update:

"$HOME/.local/bin/amos" notify "@github:tatolab/streamlib#319" "Phase 1 merged. Starting phase 2 now."

Longer comment with markdown — use a HEREDOC to keep the quoting sane:

MSG="$(cat <<'EOF'
## Progress update

- Landed the canonical-name migration (80 plan files).
- Reattached #322 under #319 (was silently orphaned by a stale rename).
- Added missing #369 / #370 edges under #326.

Next: working on #370 (xtask JTD discriminator).
EOF
)"
"$HOME/.local/bin/amos" notify "@github:tatolab/streamlib#319" "$MSG"

When to use

Reporting progress to everyone watching the issue
Closing-out notes when finishing a task
Flagging a blocker that needs the issue reporter's attention

When NOT to use

Notes meant only for yourself or the agent → put them in the plan file body instead.
Communicating privately with a teammate → use a DM, not an issue comment.
Anything sensitive → remember the tracker is visible to everyone with repo access.

Verification

After posting, the comment appears on the issue page. amos show "<node-name>" will re-fetch the issue and include the new comment in the resolved body.