meegle-api_skill

This skill helps you create and manage Meegle work items programmatically by building requests with templates and field values.
  • Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill meegle-api

  • _meta.json801 B
  • README.md10.7 KB
  • SKILL.md1.2 KB

Overview

This skill provides a lightweight OpenAPI wrapper for Meegle work items, enabling programmatic create, get, update, and related operations in a Meegle space. It expects a valid domain and access token (see the users/auth skill) and focuses on reliably persisting tasks, stories, bugs, and custom work item types. Use it to automate item creation, integrate planning workflows, or drive bulk updates from external tools.

How this skill works

The skill calls Meegle OpenAPI endpoints for work-item operations using the provided project_key (space ID or domain) and an access token. For creation it accepts work item type, optional template_id, name, and field_value_pairs that must match metadata from the "Get Work Item Creation Metadata" call. It validates required fields based on required_mode and returns the created item ID or API error codes for common failure modes.

When to use it

  • Programmatically create tasks, stories, bugs, or custom work items in a Meegle space.
  • Persist structured work items from automation, bots, or AI assistants.
  • Bootstrap or seed project boards and workflows.
  • Integrate third-party tools or importers that need to create items with templates and custom fields.
  • Perform scripted updates or bulk operations tied to a space domain or project_key.

Best practices

  • Obtain project_key and access token from the users/auth skill before calling endpoints.
  • Call Get Work Item Creation Metadata first to build valid field_value_pairs and use option IDs (not labels).
  • Avoid sending name or template_id inside field_value_pairs; pass them as top-level fields.
  • Set required_mode to 1 during validation runs to catch missing required fields before final create.
  • Handle common error codes (type not found, template/role parsing failure, duplicate fields, missing required fields).

Example use cases

  • Create a new story with default template: specify work_item_type_key and name, then receive the created ID.
  • Create templated work items for onboarding by passing a template_id and field_value_pairs for required fields.
  • Automate sprint planning: bulk-create tasks from a CSV by mapping columns to field_value_pairs using metadata.
  • Integrate an AI assistant to persist suggested tasks into Meegle with proper field mappings and role_owners.

FAQ

You need a domain (project_key) and a valid access token obtained from the users/auth flow; the token must have Work Items permission.

How do I set field values for option/select fields?

Use option IDs returned by the creation metadata, not display labels. Cascading fields must follow the configured option hierarchy.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
meegle-api skill by openclaw/skills | VeilStrat