agentsclimarketplace

Check inbox

Skill markbaindesign/bain-studio/.claude/skills/check-inbox

Read and process any pending messages in the current project's .claude/inbox/. Surfaces alerts, handoffs, and events from other agents or the studio system. Archives processed messages.From its SKILL.md

Install
npx -y skills add markbaindesign/bain-studio --skill check-inbox

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 469 tokens by cl100k_base, as published. Nobody here has run it

Check Inbox

Process all pending messages in .claude/inbox/ for the current project.

Steps

1. Find the inbox

The inbox is at .claude/inbox/ relative to the current project root (the directory containing CLAUDE.md).

If the inbox doesn't exist or is empty, report "Inbox empty." and stop.

2. Read each message

For each msg-*.md file in the inbox (oldest first — sort by filename):

Parse the frontmatter:

  • from — sending agent or system
  • typeevent, handoff, alert, or report
  • subject — one-line summary
  • prioritylow, normal, high, or urgent
  • sent_at — when it was sent

Read the body below the --- closing fence.

3. Act on the message

alert / urgent or high priority: Surface immediately and prominently. If it describes a broken build, failed deploy, or blocking error — investigate now before continuing.

handoff: The sending agent is passing work to this session. Read the body carefully — it will describe what was done, what is next, and any open questions. Treat it as a briefing for the current session.

event: Informational. Note it in the session summary but no action required unless the body says otherwise.

report: A completed-work summary from another agent. File it mentally as context; no action required.

4. Archive processed messages

Move each processed message to .claude/inbox/processed/:

mkdir -p .claude/inbox/processed
mv .claude/inbox/msg-*.md .claude/inbox/processed/

5. Report

Output a summary:

## Inbox — {N} message(s)

- [{priority}] {subject} (from: {from}, {sent_at})
  {One line summary of action taken or noted}

{If inbox was empty:}
Inbox empty.

If any message was urgent or described a blocker, flag it clearly at the top of the report before the list.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.