inbox-monitoring
Skill35 starsChanged 4 months agoMITView on GitHub
Use this skill when the user wants to monitor Aicoo inbox activity, check new conversations/messages, track pending requests, or run periodic inbox checks. Triggers on: 'inbox monitoring', 'monitor inbox', 'new messages', 'pending requests', 'message watch', '收件箱监控', '/v1/conversations', '/v1/network/requests'.
- Reads credentials
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- aicooSkill
- autonomous-syncSkill
- build-memorySkill
- check-messagesSkill
- compile-identitySkill
- connect-local-agentSkill
- context-syncSkill
- daily-briefSkill
- discoverSkill
- examine-sandboxSkill
- group-chatSkill
- heartbeatSkill
- invite-teamSkill
- onboardingSkill
- raw-memorySkill
- share-agentSkill
- snapshotsSkill
- squareSkill
- start-aicooSkill
- talk-to-agentSkill
- todosSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 59
Use /loop or /routine.
- Distinctive: line 75
Use the provided script:
- Very specific: line 97
If no new items, return a single line: No new inbox activity since last check.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Inbox Monitoring
Monitor incoming communication in Aicoo and surface what needs action.
Prerequisites
AICOO_API_KEYmust be set- Base URL:
https://www.aicoo.io/api/v1
Endpoints
GET /api/v1/conversations?view=all&limit=...GET /api/v1/network/requestsGET /api/v1/os/network(optional context: links/visitors/contacts)
Core Workflow
Step 1: Pull conversation inbox
curl -s "https://www.aicoo.io/api/v1/conversations?view=all&limit=50" \
-H "Authorization: Bearer $AICOO_API_KEY" | jq .Views:
view=mefor direct/humanview=coofor shared-agent conversationsview=allfor combined monitor
Step 2: Pull pending requests
curl -s "https://www.aicoo.io/api/v1/network/requests" \
-H "Authorization: Bearer $AICOO_API_KEY" | jq .Step 3: Optional network context
curl -s "https://www.aicoo.io/api/v1/os/network" \
-H "Authorization: Bearer $AICOO_API_KEY" | jq .Step 4: Build action queue
Prioritize in this order:
- New inbound agent/human messages requiring response
- Incoming pending requests (
type: agentfirst, thentype: friend) - High-signal visitor or share-link activity
Claude Code Automation
Use /loop or /routine.
/loop example
/loop 15m monitor my Aicoo inbox using /v1/conversations?view=all and /v1/network/requests; report only new items since last check and recommended replies./routine example
/routine inbox-monitor every 15 minutes: check /v1/conversations + /v1/network/requests and summarize urgent items only.OpenClaw Automation (CRON)
Use the provided script:
# Every 15 minutes
*/15 * * * * /path/to/aicoo-skills/scripts/inbox-monitor-cron.sh >> /tmp/aicoo-inbox-monitor.log 2>&1Optional envs:
PULSE_INBOX_VIEW(all|me|coo, default:all)PULSE_INBOX_LIMIT(default:50)PULSE_INBOX_STATE_FILE(default:/tmp/pulse-inbox-monitor-state.json)
Output Contract
For each run, return:
newMessagescountnewIncomingRequestscount- top urgent items (contact + timestamp + one-line summary)
- suggested next actions (reply / accept / ignore)
If no new items, return a single line: No new inbox activity since last check.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

