Use when AI receives messages starting with `[Remote System : type]`. Provides guidelines for handling system wake-up messages and email communication.
Scanned 5/27/2026
Install via CLI
openskills install CodingJay-1/claude-mail-bridge---
name: claude-mail-bridge-wakeup
description: Use when AI receives messages starting with `[Remote System : type]`. Provides guidelines for handling system wake-up messages and email communication.
---
# Claude Mail Bridge Wake-up Response Guidelines
## Overview
This skill defines how to respond to system wake-up messages from remote control. When AI receives a message starting with `[Remote System : Wakeup]`, it must follow these guidelines.
## System Message Format
System messages use unified format: `[Remote System : type]`
**Type definitions:**
- `Wakeup` - Wake-up instruction, user requests communication with AI via email
- `Warning` - System warning messages
- `Guide` - Behavior guidance messages
## Wake-up Response Flow
When receiving a `[Remote System : Wakeup]` message:
1. **Immediately stop current operation**
- Stop any tool calls in progress
- Do not continue processing current task
2. **Set user status to away**
```bash
mcp__presence_system__set_presence(mode="away", _init_skill_invoked=True)
```
3. **Wait for further user instructions**
- Use `mcp__email_system__mail_user_and_wait` to contact user
- Or execute specified operations based on message content
## Email Communication
Use `mcp__email_system__mail_user_and_wait` to communicate with user:
```bash
mcp__email_system__mail_user_and_wait(
subject="Short summary",
background="Context and progress status",
content="The question or conclusion message",
type="question", # or "conclusion"
_init_skill_invoked=True
)
```
For detailed parameter documentation and usage examples, use `/claude-mail-bridge-init`.
## Notes
1. **Priority**: System messages have highest priority, handle immediately upon receipt
2. **Do not ignore**: Do not ignore any message starting with `[Remote System :`
3. **Timely response**: Immediately stop current operation after receiving wake-up message
4. **Status synchronization**: Ensure presence status is consistent with actual user status
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.