Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

pi-openclaw-chat-providers

Estrelas1

Forks0

Atualizado23 de fevereiro de 2026 às 14:09

Configure chat and bot access for pi-openclaw-mcp-stack. Use when users need Telegram BotFather setup, token wiring, OpenAI-compatible provider variables, or local Ollama setup on Pi 5.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

eoinjordan

eoinjordan/pi-openclaw-mcp-stack

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

5 arquivos

SKILL.md

readonly

name	pi-openclaw-chat-providers
description	Configure chat and bot access for pi-openclaw-mcp-stack. Use when users need Telegram BotFather setup, token wiring, OpenAI-compatible provider variables, or local Ollama setup on Pi 5.

Pi OpenClaw Chat Providers

Configure Telegram access first.

Create bot via BotFather.
Set TELEGRAM_TOKEN in .env.
Restart clawdbot and confirm logs.

Choose one chat backend.

Remote OpenAI-compatible endpoint using OPENAI_API_KEY.
Local Ollama using OPENAI_BASE_URL and model name.

Apply environment safely.

Set only required keys.
Avoid printing token values in logs or output.

Validate chat path.

Check clawdbot logs.
Send help and health commands from Telegram.

Keep MCP routing separate.

Clarify that provider choice affects free-text chat behavior only.
Arduino and EI tool routing is unchanged.

References

references/telegram-botfather.md
references/provider-env.md
references/ollama-pi5.md

Mais deste repositório

mesmo repositório

pi-openclaw-ei-arduino-deploy

eoinjordan/pi-openclaw-mcp-stack

Run combined Edge Impulse MCP and Arduino MCP deployment workflows in pi-openclaw-mcp-stack. Use when users need to build an Arduino deployment package from an Edge Impulse impulse, bundle it for Arduino build, validate/build through Arduino MCP, and hand off to flash workflow for Nano 33 BLE deployment.

2026-02-261

pi-openclaw-flow-audit

eoinjordan/pi-openclaw-mcp-stack

Audit and troubleshoot end-to-end command flow in pi-openclaw-mcp-stack across clawdbot, openclaw-gateway, arduino-mcp, and EI bridge services. Use when users see degraded upstream health, connection refused errors, container restarts, missing responses, or need proof of routing behavior.

2026-02-261

pi-openclaw-arduino-flash

eoinjordan/pi-openclaw-mcp-stack

Flash firmware to Arduino boards in the pi-openclaw-mcp-stack workflow after successful build/deployment. Use when users need serial port detection, board/FQBN checks, upload commands for Nano 33 BLE, post-flash verification, or EI deployment handoff completion.

2026-02-261

pi-openclaw-pi5-quickstart

eoinjordan/pi-openclaw-mcp-stack

Set up and start pi-openclaw-mcp-stack on Raspberry Pi 5 with Raspberry Pi OS 64-bit Bookworm. Use when users need fresh install commands, Docker Compose/Buildx prerequisite fixes, profile selection (mcp-image, mcp-local, mcp), environment setup, first boot, or baseline health checks.

2026-02-231

name	pi-openclaw-chat-providers
description	Configure chat and bot access for pi-openclaw-mcp-stack. Use when users need Telegram BotFather setup, token wiring, OpenAI-compatible provider variables, or local Ollama setup on Pi 5.

Pi OpenClaw Chat Providers

Configure Telegram access first.

Create bot via BotFather.
Set TELEGRAM_TOKEN in .env.
Restart clawdbot and confirm logs.

Choose one chat backend.

Remote OpenAI-compatible endpoint using OPENAI_API_KEY.
Local Ollama using OPENAI_BASE_URL and model name.

Apply environment safely.

Set only required keys.
Avoid printing token values in logs or output.

Validate chat path.

Check clawdbot logs.
Send help and health commands from Telegram.

Keep MCP routing separate.

Clarify that provider choice affects free-text chat behavior only.
Arduino and EI tool routing is unchanged.

References

references/telegram-botfather.md
references/provider-env.md
references/ollama-pi5.md