What problem does it solve? Accessing Plurk social network data programmatically requires handling OAuth 1.0 authentication and multiple API endpoints, which is tedious to set up manually for reading timelines or posting responses. ## Core Features & Use Cases - Timeline Reading: Fetch your own timeline with filters (my, responded, private, favorite, replurked, mentioned) or view another user's public plurks. - Response Management: Read responses on any plurk with pagination and post new responses using Plurk qualifiers like says, thinks, or likes. - Use Case: Monitor your Plurk timeline for mentions, then reply to a specific plurk directly from the command line using its plurk_id, with all output as JSON for piping into jq. ## Quick Start Ask the agent to show the latest 10 plurks from your Plurk timeline after setting the four PLURK OAuth environment variables.