القائمة
Connect AssistClaw to a Bee wearable via BeeMCP (MCP server) without using bee CLI/proxy. Use when: BeeMCP is already installed or user wants Bee tools exposed through MCP lazy-loading.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Query and control a Bee wearable (bee.computer) — conversations, facts, todos, journals, daily briefs, and real-time event streams. Use when: user references their Bee device, asks what they just talked about, wants a daily brief, manages facts/todos captured by Bee, or searches their personal lifelog. NOT for: generic calendar/reminder apps, historical data older than the Bee account, or non-Bee wearables.
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.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks AssistClaw to add a note, list notes, search notes, or manage note folders.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Create, search, and manage Bear notes via grizzly CLI.
Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
| name | bee-mcp |
| description | Connect AssistClaw to a Bee wearable via BeeMCP (MCP server) without using bee CLI/proxy. Use when: BeeMCP is already installed or user wants Bee tools exposed through MCP lazy-loading. |
| homepage | https://github.com/OkGoDoIt/beemcp |
| metadata | {"assistclaw":{"emoji":"🐝","requires":{"bins":["uvx"],"env":["BEE_API_KEY"]},"primaryEnv":"BEE_API_KEY"}} |
Use this when you want Bee wearable context in AssistClaw through MCP only,
without the Bee CLI (@beeai/cli) and without bee proxy.
✅ USE this skill when:
bee:*).❌ DON'T use when:
bee sync markdown exports (use skills/bee).bee today / bee now.export BEE_API_KEY="your_bee_api_key"
assistclaw mcp add --name bee \
--command "uvx beemcp" \
--env BEE_API_KEY=$BEE_API_KEY
assistclaw mcp status
assistclaw mcp list-tools | grep '^bee:'
Ask AssistClaw naturally after BeeMCP is connected:
The agent will lazy-load BeeMCP tool schemas and call them as needed.
mcp:
clients:
- name: bee
command: "uvx beemcp"
env:
- "BEE_API_KEY=${BEE_API_KEY}"
| Symptom | Fix |
|---|---|
No bee:* tools listed | Confirm BEE_API_KEY is exported in the daemon environment |
| MCP client fails to spawn | Verify uvx exists: uvx --version |
| Tool calls return auth errors | Rotate key in Bee dashboard and restart AssistClaw |
BEE_API_KEY in environment/secret manager, never hardcode in files.skills/bee.