jira-auth_skill

Overview

This skill authenticates with Jira Cloud REST API using API tokens or OAuth 2.0 and provides helper patterns for connection setup, credential validation, and basic rate limit handling. It includes cross-platform examples (Node.js and Python), environment variable patterns, and small client utilities to standardize requests. Use it to quickly validate credentials and bootstrap Jira API requests in scripts or CLI tools.

How this skill works

The skill reads required configuration from a .env file or environment variables (JIRA_EMAIL, JIRA_API_TOKEN, JIRA_BASE_URL) and builds a Basic auth header by base64-encoding email:token. It provides ready-to-use code snippets for Node.js, Python, and TypeScript to construct headers, instantiate a small Jira client, and call the /myself endpoint to validate connectivity. The client inspects HTTP responses, surfaces API errors, and detects 429 rate-limit responses so callers can retry or back off.

When to use it

• Setting up a new Jira Cloud integration or CI job that needs API access
• Validating that an API token, email, and base URL are correct
• Bootstrapping scripts or CLIs that call Jira REST endpoints
• Testing connectivity before performing batch operations
• Implementing basic rate-limit handling in integrations

Best practices

• Store JIRA_EMAIL, JIRA_API_TOKEN, and JIRA_BASE_URL in environment variables or a .env file, never in source control
• Always base64-encode the 'email:apiToken' pair and include the 'Basic ' prefix with a single space
• Normalize baseUrl to avoid trailing slash issues when building request URLs
• Check for 429 responses and use the X-RateLimit-Reset header to schedule retries
• Prefer API tokens over account passwords and restrict token scope when possible

Example use cases

• A CLI tool that validates a developer's Jira credentials before running migrations
• A build step that checks Jira connectivity before publishing release notes
• A small automation that creates issues after validating the project key and auth
• A monitoring probe that periodically calls /myself to verify integration health