jb/paseo
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(skills): rewrite skills to use CLI, reframe orchestrator as chat-first team lead

Browse Source 
- paseo: add loop, schedule, chat command reference sections
- paseo-loop: replace loop.sh with paseo loop CLI, document model selection and archive
- paseo-chat: replace chat.sh with paseo chat CLI
- paseo-orchestrator: reframe as team orchestrator using chat rooms as coordination backbone,
  agents as disposable workers, schedule heartbeat for oversight
- paseo-handoff/committee: fix --mode bypass → --mode bypassPermissions
- Delete loop.sh (541 lines) and chat.sh (635 lines) bash scripts
This commit is contained in:
Mohamed Boudra
2026-03-28 01:13:42 +07:00
parent 657b3e1ccd
commit 29876acae5
8 changed files with 369 additions and 2029 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/paseo-chat/SKILL.md
+41 -75
View File
@@ -1,14 +1,12 @@
---
name: paseo-chat
description: Use chat rooms through a chat helper. Use when the user says "chat room", "room", "coordinate through chat", "shared mailbox", or wants agents to communicate asynchronously.
description: Use chat rooms through the Paseo CLI. Use when the user says "chat room", "room", "coordinate through chat", "shared mailbox", or wants agents to communicate asynchronously.
user-invocable: true
---
# Paseo Chat Skill
This skill teaches how to use chat.
Use `skills/paseo-chat/bin/chat.sh`.
This skill teaches how to use chat rooms for agent coordination via the Paseo CLI.
**User's arguments:** $ARGUMENTS
@@ -21,136 +19,104 @@ Load the **Paseo skill** first if you need CLI guidance for launching or messagi
## Rules
When using chat:
- create a room with `chat.sh room create` if you need a new room
- inspect available rooms with `chat.sh room list` and `chat.sh room show`
- post with `chat.sh post`
- read with `chat.sh read`
- create a room with `paseo chat create` if you need a new room
- inspect available rooms with `paseo chat ls` and `paseo chat inspect`
- post with `paseo chat post`
- read with `paseo chat read`
- keep reads bounded, usually `--limit 10` or `--limit 20`
- check chat often while working
Do not read or write the backing files directly. Use `chat.sh`.
Mentions and replies are active:
- if you post `@agent-id` in a message, chat will notify that agent immediately
- if you post `@everyone`, chat will notify every agent that has already participated in that room, as if you had tagged each of them directly
- if you use `--reply-to`, chat will notify the author of the replied-to message immediately
- notifications are sent with `paseo send --no-wait`
Mentions are active:
- use `--mention <agent-id>` on your post to notify a specific agent immediately
- if you use `--reply-to`, the author of the replied-to message is notified
- notifications are sent via `paseo send --no-wait` under the hood
- mentions **interrupt** the target agent, so only mention when they need to act now
- if a normal post is enough and no one needs to act right now, skip the mention
## Command Surface
### Create a room
```bash
skills/paseo-chat/bin/chat.sh room create \
--room issue-456 \
--title "Issue 456 coordination" \
--purpose "Coordinate implementation and review"
paseo chat create issue-456 --purpose "Coordinate implementation and review"
```
### List rooms
```bash
skills/paseo-chat/bin/chat.sh room list
paseo chat ls
```
### Show room details
### Inspect room details
```bash
skills/paseo-chat/bin/chat.sh room show --room issue-456
paseo chat inspect issue-456
```
### Post a message
```bash
skills/paseo-chat/bin/chat.sh post \
--room issue-456 \
--body "I traced the failure to relay auth. Investigating config loading now."
paseo chat post issue-456 "I traced the failure to relay auth. Investigating config loading now."
```
Author defaults:
- `--agent-id` if provided
- otherwise `$PASEO_AGENT_ID`
- otherwise `manual`
Optional reply:
With a reply:
```bash
skills/paseo-chat/bin/chat.sh post \
--room issue-456 \
--reply-to msg-001 \
--body "I can take that next."
paseo chat post issue-456 "I can take that next." --reply-to msg-001
```
Direct mention:
With a direct mention:
```bash
skills/paseo-chat/bin/chat.sh post \
--room issue-456 \
--body "@agent-beta can you verify the relay path next?"
```
Notify the whole room:
```bash
skills/paseo-chat/bin/chat.sh post \
--room issue-456 \
--body "@everyone I need each of you to weigh in on whether we should cut scope or keep the full fix."
paseo chat post issue-456 "Can you verify the relay path next?" --mention <agent-id>
```
### Read recent messages
```bash
skills/paseo-chat/bin/chat.sh read --room issue-456 --limit 10
paseo chat read issue-456 --limit 10
```
### Filter reads
```bash
skills/paseo-chat/bin/chat.sh read --room issue-456 --agent-id 123abc
skills/paseo-chat/bin/chat.sh read --room issue-456 --since 2026-03-24T10:00:00Z
paseo chat read issue-456 --agent <agent-id>
paseo chat read issue-456 --since 5m
paseo chat read issue-456 --since 2026-03-24T10:00:00Z
```
### Wait for new messages
```bash
paseo chat wait issue-456 --timeout 60s
```
## Defaults
When creating a room:
- choose a short explicit room id
- prefer slugs like `issue-456`, `pr-143-review`, `feature/relay-cleanup`
- give the room a clear title and purpose
- choose a short slug: `issue-456`, `pr-143-review`, `relay-cleanup`
- give it a clear purpose
When using a room:
- read only a bounded window before acting
- post updates when they would help another agent or your future self
- use `--reply-to` when responding to a specific message
- use `@agent-id` when you want to get a specific agent's attention — but know that mentions **interrupt** the target agent immediately, so only mention when they need to act now
- use `@everyone` sparingly when you want all prior participants in the room to respond or re-check the thread
- prefer `@agent-id` most of the time so you only interrupt the agents who actually need the message
- if a normal post is enough and no one needs to act right now, skip the mention — agents will see it next time they read the room
- use `--mention` when you want to get a specific agent's attention — but know that mentions **interrupt** the target agent
- check chat frequently enough that shared coordination actually works
- your own agent ID is available via `$PASEO_AGENT_ID` — when someone asks you to report back, mention them so they get notified
- your own agent ID is available via `$PASEO_AGENT_ID`
Typical things to post:
- status updates
- blockers
- handoffs
- review findings
- important context and memories another agent may need later
Good use of `@everyone`:
- you need opinions or explicit responses from the whole team
- the room has shared context and each participant should re-check it now
Avoid `@everyone` when:
- only one or two agents need to act
- different agents are doing different jobs and you do not want to interrupt all of them
- a normal post is enough because no immediate response is needed
- important context another agent may need later
## Your Job
1. Understand whether you should use an existing room or create a new one
2. Choose a room id and title
3. Create the room with `chat.sh room create` if needed
4. Read the room with bounded history
5. Post clearly
6. Use `--reply-to` when replying to a specific message
7. Use `@agent-id` when you want to notify someone directly
8. Use `@everyone` only when you intentionally want to notify the full room and prompt a broad response
2. Create the room with `paseo chat create` if needed
3. Read the room with bounded history
4. Post clearly
5. Use `--reply-to` when replying to a specific message
6. Use `--mention` when you want to notify someone directly