pylon-support

What This Skill Does

The pylon-support skill provides a robust interface for interacting with the Pylon REST API directly from your terminal. It allows you to audit tickets, manage your queue, and perform bulk updates without needing to switch context to a web browser. By integrating with OpenClaw, this skill enables automated triage and reporting workflows that keep your team productive and informed about ongoing customer issues.

Installation

To install this skill, run the following command in your terminal within the OpenClaw environment: clawhub install openclaw/skills/skills/1waterrj/pylon-support

Ensure you have configured your environment variables by exporting your PYLON_API_TOKEN. For advanced configuration, you can utilize the pylon_env.py script to manage user IDs and default settings in a ~/.pylonrc file.

Use Cases

• Triage Automation: Quickly fetch your daily queue or aggregate reports for multiple team members using the pylon_triage_report.py tool. This is ideal for stand-ups or shift handovers.
• Rapid Issue Updates: Instead of navigating complex UI menus, use pylon_update_issue.py to move tickets to different states, update priority labels, or add tags in bulk.
• Advanced Auditing: Utilize pylon_list_issues.py to scan for specific states or blockers across large volumes of data using pagination cursors.
• Workflow Customization: Build shell scripts that rely on the output of these tools to trigger notifications or sync with other internal platforms.

Example Prompts

1. "OpenClaw, run the pylon triage report for the last 14 days showing the top 5 tickets per state for both Kody and Skyler."
2. "Can you check my Pylon queue and list all tickets that are currently waiting on me?"
3. "Update Pylon issue iss_123: change the status to waiting_on_customer and add tags 'followup' and 'pending_ops'."

Tips & Limitations

• Token Security: Always treat your PYLON_API_TOKEN as sensitive information. Avoid hardcoding it into scripts; use environment variables or encrypted secret managers.
• Pagination: When dealing with large lists, remember that the API might require you to pass a page-cursor back into the command to retrieve subsequent results.
• Filtering: While the API supports server-side filtering, local scripts may perform secondary filtering (especially for assignees). If you don't see expected results, double-check your local cache via pylon_env.py --show to ensure your user ID is correctly mapped.