line-client

What This Skill Does

The line-client skill provides a robust bridge between your OpenClaw agent and the LINE messaging platform. By utilizing the Chrome extension gateway (line-chrome-gw.line-apps.com), this skill enables your agent to act as a fully functional LINE client. You can send and receive messages, manage your contacts, organize group chats, and view profile information directly through an automated interface. The skill handles the complex cryptographic handshake required by LINE, including the QR code authentication flow and HMAC-signed API requests.

Installation

To integrate this skill into your environment, use the OpenClaw management utility via the command: clawhub install openclaw/skills/skills/2manslkh/line-api. Ensure that your environment has access to Node.js for the HMAC signing process (which automatically starts on port 18944) and the necessary WASM dependencies (lstm.wasm and lstmSandbox.js) in the root directory. Configuration files, including your auth tokens and certificates, are stored in ~/.line-client/.

Use Cases

This skill is ideal for users who want to automate their personal or professional LINE communications. Examples include managing customer support inquiries, automating notifications from custom scripts, or creating a virtual assistant that tracks group discussions and provides summary updates. Because it functions as a persistent client, the agent can monitor incoming messages in real-time and trigger automated responses or workflows based on keywords or sender identity.

Example Prompts

1. "Check my latest messages from the 'Project Team' group and summarize any urgent requests."
2. "Send a message to my contact 'Alice' saying I'll be 10 minutes late for our meeting."
3. "Who are the members currently in my 'Work' group, and has anyone sent a contact request today?"

Tips & Limitations

Note that LINE authentication tokens expire approximately every 7 days. If you encounter an APIError(10051), you must re-initiate the QR login sequence. When authenticating, the 6-digit PIN provided by the service is highly time-sensitive; you must provide this to the user immediately upon the on_pin event trigger to prevent session timeouts. Always ensure your token storage directory has the correct write permissions, as the skill requires constant access to update your session status.