jira-service-desk_skill

This skill helps you manage Jira Service Desk data by listing, creating, and querying tickets, customers, and organizations through Membrane.
  • Python

2.5k

GitHub Stars

2

Bundled Files

3 weeks ago

Catalog Refreshed

1 month 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 veilstart where the catalogue uses aiagentskills.

npx veilstart add skill openclaw/skills --skill jira-service-desk

  • _meta.json291 B
  • SKILL.md11.4 KB

Overview

This skill integrates with Jira Service Desk to manage tickets, customers, organizations, service desks, request types, queues, comments, and attachments. It exposes pre-built actions for common workflows and a proxy mode for custom API requests. Use it to automate support workflows, fetch service desk metadata, and create or update customer requests programmatically.

How this skill works

The skill runs through the Membrane CLI which handles authentication, credential refresh, pagination, and error handling. You run pre-defined actions (list-requests, create-request, list-service-desks, etc.) or send proxied HTTP calls to the Jira Service Desk REST API when an action is not available. Action inputs and outputs follow Membrane schemas so you can discover available operations and required parameters before running them.

When to use it

  • Automate ticket creation, updates, or comment management from external systems
  • Bulk-fetch service desk metadata like request types, queues, and organizations
  • Integrate customer onboarding by creating organizations and customers in Jira Service Desk
  • Query knowledge base articles or run custom API calls not covered by actions
  • Debug or extend functionality using the proxy to call raw REST endpoints

Best practices

  • Prefer Membrane pre-built actions for common tasks to benefit from built-in auth, pagination, and error handling
  • Run membrane action list --intent=QUERY to discover available actions and input schemas before building integrations
  • Use the Membrane connection flow rather than storing API keys locally; Membrane manages credentials and refresh securely
  • When needed, use the membrane request proxy for endpoints not covered by actions and include headers, method, and query params explicitly
  • Test actions in a sandbox or with filters to avoid accidental bulk changes

Example use cases

  • Create a new customer request from a web form and attach user files automatically
  • List and export all service desk queues and request types for audit or migration
  • Add a comment and attachment to an existing request when a monitoring alert triggers
  • Create or update organizations as part of an enterprise onboarding workflow
  • Search the service desk knowledge base to surface articles for automated triage

FAQ

No. Membrane handles authentication and credential refresh. Create a connection through the CLI and avoid storing tokens locally.

What if an action I need does not exist?

Use membrane request to proxy a raw REST call. The proxy appends the Jira base URL and injects authentication headers, so you can call any API endpoint directly.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational