meegle-api

What This Skill Does

The meegle-api skill acts as a comprehensive gateway for interacting with the Meegle project management platform via OpenClaw. This toolset is organized into a hierarchical structure that allows you to manage the entire lifecycle of projects, from setting up authentication credentials to granularly tracking work items and analyzing team performance through measurement views. Because the API is modular, it ensures that your interactions with the Meegle backend are structured, efficient, and context-aware. Whether you need to automate the creation of bug tickets, adjust process configurations, or retrieve complex Gantt chart data, this skill provides the necessary endpoints to facilitate seamless integration.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/pkycy/meegle-api After installation, ensure that you initialize your connection by first invoking the meegle-api-credentials module. This is a prerequisite for all subsequent operations to establish the required domain, authentication tokens, and workspace context.

Use Cases

This skill is designed for project managers, developers, and QA engineers who rely on Meegle for daily operations. Use it to:

• Automate the generation of user stories or bugs from external communications.
• Sync team member groups and user roles across projects.
• Perform bulk updates on work items based on custom fields or status transitions.
• Extract data for custom reporting, such as Kanban board health or Gantt chart progress.
• Standardize project configurations by programmatically managing settings across different spaces.

Example Prompts

1. "Connect to Meegle using my saved credentials, then fetch all high-priority bugs assigned to me in the current space."
2. "Create a new feature request titled 'Dark Mode Support' in the design space and add a comment tagging the lead designer."
3. "Generate a summary report of all completed tasks for this sprint using the current project's measurement views."

Tips & Limitations

• Sequence Matters: Always reference the index provided in the documentation. Failure to load credentials first will result in failed requests.
• Rate Limiting: Be mindful of API rate limits when scripting bulk operations on work items.
• Error Handling: Ensure that you have proper project_key and user_key values stored, as the API relies heavily on these identifiers to scope your requests correctly.
• Permissions: Your credentials must have the appropriate access levels to perform write operations like updating work items or modifying space settings.