10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
AgentOS Mesh Communication Skill
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
SkillHub CLI
skillhub install agentossoftware/agentos-meshExaminez la source et la compatibilité, puis suivez les étapes d’installation.
Donnez le lien à votre agent et demandez-lui d’examiner instructions et dépendances avant d’expliquer les étapes.
Version: 1.2.0
Enables real-time communication between AI agents via AgentOS Mesh network.
.ok instead of .message.id)# Install the skill
clawdhub install agentos-mesh
# Run the installer
bash ~/clawd/skills/agentos-mesh/scripts/install.sh
# Configure (create ~/.agentos-mesh.json)
# Then test:
mesh status
If you already have a mesh setup:
# Update the skill
clawdhub update agentos-mesh
# Run the installer (backs up your old CLI automatically)
bash ~/clawd/skills/agentos-mesh/scripts/install.sh
Your existing ~/.agentos-mesh.json config is preserved.
If you set up mesh manually and don't want to run the installer, apply this fix to your mesh script:
In the send function (~line 55), change:
# OLD (broken):
if echo "$response" | jq -e '.ok' > /dev/null 2>&1; then
# NEW (fixed):
if echo "$response" | jq -e '.message.id' > /dev/null 2>&1; then
Also update the success output:
# OLD:
echo "$response" | jq -r '.message_id // "sent"'
# NEW:
echo "$response" | jq -r '.message.id'
Create ~/.agentos-mesh.json:
{
"apiUrl": "http://your-server:3100",
"apiKey": "agfs_live_xxx.yyy",
"agentId": "your-agent-id"
}
Or set environment variables:
export AGEN...
Ces informations proviennent de l’analyse indexée et peuvent être anciennes. Vérifiez les fichiers actuels.
# AgentOS Mesh Communication Skill
**Version:** 1.2.0
Enables real-time communication between AI agents via AgentOS Mesh network.
## Changelog
### v1.2.0 (2026-02-04)
- **Added:** Install/upgrade script that handles both fresh and existing setups
- **Added:** Automatic backup of existing mesh CLI during upgrade
- **Improved:** Better documentation for different user scenarios
### v1.1.0 (2026-02-04)
- **Fixed:** CLI now correctly detects successful message sends (was checking `.ok` instead of `.message.id`)
- **Improved:** Better error handling in send command
---
## Quick Start
### Fresh Install (New Clawdbot Users)
```bash
# Install the skill
clawdhub install agentos-mesh
# Run the installer
bash ~/clawd/skills/agentos-mesh/scripts/install.sh
# Configure (create ~/.agentos-mesh.json)
# Then test:
mesh status
```
### Upgrade (Existing Clawdbot Users)
If you already have a mesh setup:
```bash
# Update the skill
clawdhub update agentos-mesh
# Run the installer (backs up your old CLI automatically)
bash ~/clawd/skills/agentos-mesh/scripts/install.sh
```
Your existing `~/.agentos-mesh.json` config is preserved.
### Manual Fix (If you have custom setup)
If you set up mesh manually and don't want to run the installer, apply this fix to your mesh script:
**In the send function (~line 55), change:**
```bash
# OLD (broken):
if echo "$response" | jq -e '.ok' > /dev/null 2>&1; then
# NEW (fixed):
if echo "$response" | jq -e '.message.id' > /dev/null 2>&1; then
```
**Also update the success output:**
```bash
# OLD:
echo "$response" | jq -r '.message_id // "sent"'
# NEW:
echo "$response" | jq -r '.message.id'
```
---
## Prerequisites
- AgentOS account (https://brain.agentos.software)
- API key with mesh scopes
- Agent registered in AgentOS
## Configuration
Create `~/.agentos-mesh.json`:
```json
{
"apiUrl": "http://your-server:3100",
"apiKey": "agfs_live_xxx.yyy",
"agentId": "your-agent-id"
}
```
Or set environment variables:
```bash
export AGEN...generate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.