Setup Mulmobridge Line
Apps & Automationsetup-mulmobridge-lineSetup Mulmobridge Line is an Agent Skill for apps & automation published in the receptron/mulmoclaude repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Interactively guide LINE bridge setup — ngrok install, LINE Developers Console config, and bridge startup. Respond in the user's language.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/receptron/mulmoclaude/blob/HEAD/.claude/skills/setup-mulmobridge-line/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/setup-mulmobridge-line, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Setup LINE Bridge
Guide the user through LINE bridge setup following the docs at docs/message_apps/line/. Use the language-appropriate version (README.md for English, README.ja.md for Japanese) based on the user's language.
Step 1: Prerequisites
- Check MulmoClaude is running (
lsof -i :3001 -sTCP:LISTEN). If not, ask the user to runyarn devin a separate terminal first. - Check ngrok is installed (
which ngrok). If not, guidebrew install ngrok+ authtoken setup.
Step 2: Follow the setup doc
Read the appropriate doc (docs/message_apps/line/README.md or README.ja.md) and walk the user through it. Key pitfalls to highlight:
- Webhook URL must end with
/webhook(without it, LINE POSTs to/and gets 404) - Disable auto-reply messages in LINE Official Account settings (prevents double replies)
- Add
LINE_CHANNEL_SECRETandLINE_CHANNEL_ACCESS_TOKENto.env
Step 3: Start the bridge
node packages/bridges/line/dist/index.js
npx @mulmobridge/line does not work inside the monorepo. Use node directly.
On failure, refer to the troubleshooting table in the setup doc.