Skip to content
Skills Library
AI & agents · Tool integration

message-project

/message-project

Forward a message from the user to a specific named project-lead and read the lead's reply. Use when the user says "tell <project> to ...", "ask <project> about ...", or "<project>: ...".

Repository
claude-soma ↗
Licence
MIT
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Forward a message from the user to a specific named project-lead and read the lead's reply. Use when the user says "tell <project> to ...", "ask <project> about ...", or "<project>: ...".

Triggers from the description

s reply. Use when the user saysask <project> about ...<project>: ...
Original author description

Forward a message from the user to a specific named project-lead and read the lead's reply. Use when the user says "tell <project> to ...", "ask <project> about ...", or "<project>: ...".

How it works

  1. Process
  2. Error handling
Original SKILL.md headings · 91 lines, 707 words
SKILL.md preview
---
name: message-project
description: |
  Forward a message from the user to a specific named project-lead and read the
  lead's reply. Use when the user says "tell <project> to ...", "ask <project>
  about ...", or "<project>: ...".
allowed-tools:
  - mcp__project-orchestrator__send_to_project
  - Bash(tmux -L soma-lead-*:*)
---

# message-project

Project-leads are NOT teammates of the channel bot. Each lead is an independent
claude process in its OWN tmux server (socket `soma-lead-<name>`, session
`soma-proj-<name>`, in a sibling cgroup). `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`
only lets a lead spawn its own subagents; it does NOT federate the lead into the
bot's team. So `SendMessage(to: "soma-proj-<name>")` always fails with
"No agent named ... is currently addressable", and there is **no push-back
channel** from a lead back to the bot. Therefore: deliver by typing into the
lead's tmux pane, and read the reply by scraping that pane.

> **If you are the channel bot, do NOT run this skill inline.** The reply-poll
> in step 3 is unbounded (the lead may think for minutes) and would freeze the
> Telegram channel. Dispatch a background `Agent` (`run_in_background=true`,
> `model="opus"`) whose prompt is to run this flow and return the lead's reply,
> ack the user immediately, and relay the reply when the agent completes — see
> "Messaging a project-lead" in `system_prompts/responsive_bot.md`. Run the
> steps below inline only when you are already a background/non-channel agent
> (e.g. that dispatched agent, or a project-lead talking to another lead).

## Process

1. **Resolve + validate.** Extract the target project name from the user's
   message, then call
   `mcp__project-orchestrator__send_to_project(name, message)`. This DELIVERS
   NOTHING -- use it only to (a) confirm the project exists (it raises
   `no project named X` otherwise) and (b) confirm the bare name. From the bare
   name the tmux coordinates are fixed:
   - socket:  `soma-lead-<name>`
   - session: `soma-proj-<name>`

2. **Deliver the message** with two SEPARATE tmux calls -- type the literal
   text, then submit. Combining the text and Enter into one call is unreliable.

   Shell-safety: the user's text is arbitrary (it may contain `'`, `"`, `$`,
   backticks, `#`, newlines). Wrap the whole message in SINGLE quotes and
   escape any embedded single quote as `'\''`. This is exactly what
   `shlex.quote` produces; inside single quotes every other character is
   literal, so nothing can expand or break out of the argument.

   ```bash
   # type the message literally (-l = literal text, no key-name interpretation)
   tmux -L soma-lead-<name> send-keys -t soma-proj-<name> -l '<safely-quoted message>'
   # submit it as a SEPARATE call
   tmux -L soma-lead-<name> send-keys -t soma-proj-<name> C-m
   ```

   Worked example -- message is: `what's the $STATUS of build #3?`
   ```bash
   tmux -L soma-lead-f1-tracker send-keys -t soma-proj-f1-tracker -l 'what'\''s the $STATUS of build #3?'
   tmux -L soma-lead-f1-tracker send-keys -t soma-proj-f1-tracker C-m
   ```

   If the text lands in the prompt but doesn't submit, send one more `C-m`
   after ~1s as a fallback. If the message spans multiple lines, send it as one
   `-l` call (single quotes preserve the newlines) -- but note each newline is
   delivered as an Enter, so the lead may treat lines as separate inputs; to
   keep a multi-line message as one turn, collapse it to a single line first.

3. **Read the reply by scraping the pane** (there is no reply bus). Give the
   lead a few seconds, then capture its pane; poll up to a few times if it's
   still thinking:

   ```bash
   sleep 4
   tmux -L soma-lead-<name> capture-pane -p -t soma-proj-<name>
   ```

   `capture-pane -p` returns the visible screen -- the lead's most recent
   output -- so just read the last lines of it for the response. For more
   scrollback, add `-S -<N>` (e.g. `-S -80` to start ~80 lines back). If the
   footer still shows the lead working/thinking, `sleep` again and re-capture.
   (Deliberately no `| tail`: the bare capture is already the tail, which keeps
   this skill's only shell dependency the single `tmux -L soma-lead-*` pattern.
   The pane is a live TUI, so expect box-drawing and a prompt footer around the
   text.)

4. **Report to the user**: relay the lead's response. If it's still working
   after a couple of polls, say the message was delivered and the lead is still
   processing.

## Error handling

- `send_to_project` raises `no project named X`: the project doesn't exist (or
  already died and was reconciled out). Offer the closest match from
  `list_projects` and ask the user to confirm.
- A tmux call prints `can't find session` or `no server running on ...`: the
  lead's session has died even if the registry still listed it. Tell the user
  the lead isn't running and offer to respawn it (spawn-project).

Versions

The database has no other skills named message-project.

Database snapshot: 13.11.2026 · package version ee4aa62168d5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ao-orchestrator
    Talk to a project's Orchestrator orchestrator: pass the user's request to it, wait for its reply and relay it. The default route for starting or changing work, "catch me up", "why", "what next" and plans. Use for "in <project>: <ask>", "tell the orchestrator ...", "catch me up…
  • 100start-team
    Start an agent team for this project in one step. Checks the prerequisites, adds the adoption line, and starts <project>-lead in the lead role, or makes this session the lead where no session can be started. Use when the operator asks to start, set up or run an agent team.
  • 100draft-message
    Draft a message, email, or reply in the user's voice and show it for review before anything is sent. Use for "text Sarah that I'm running late", "draft an email to the team", "reply saying yes", or composing a note to someone. Triggers: text, message, email, reply, draft, tell…
  • 90spawn-project
    Spawn a new persistent project-lead background session for a new app / workstream the user is starting. Use when the user says "build me X", "create an app that Y", "set up a server that Z", or similar greenfield project requests. The project-lead runs in its own cwd, has its…
  • 100send-agent-message
    Use when you need to send a message or instruction to a specific agent running inside a task
  • 100direct-message
    Send a direct message to a specific agent via MCP messaging and tmux injection. Guarantees delivery by injecting the message as a submitted prompt into the agent's tmux session AND sending a persistent MCP message. Use when you need to message a specific agent and get a…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.