Jira Integration Skill for Openclaw

1. Use an AI agent platform that supports SKILL.md, such as Claude Code, Cursor, Codex, or Gemini CLI, on Windows, macOS, or Linux.
2. Install or copy the Jira Integration Skill package and its SKILL.md into the agent's supported skills directory. The exact directory and activation method depend on the host agent.
3. Ensure the agent has access to its configured LLM API. An LLM is a required dependency for interpreting instructions and coordinating tool execution.
4. Obtain a Jira API key or equivalent credential with only the permissions required for issue creation, status changes, synchronization, or workflow operations.
5. Configure the credential as an environment variable rather than hard-coding it in source files, prompts, or version control.

export API_KEY="${API_KEY:?Please set the API key environment variable}"

6. Restart the agent session or open a new terminal so the environment variable is available.
7. Verify the Jira server address, tenant information, user permissions, supported status transitions, and available automation operations.
8. Send an instruction using the required request fields:

{
  "instruction": "Create a high-priority Jira issue for the failed deployment",
  "context": "Project: OPS; assign to the on-call engineer"
}

9. Test with a non-destructive or low-risk issue operation before enabling production workflows. Protect API keys, use HTTPS, review audit logs, and observe Jira rate limits.

Request schema

Operation data

The skill maps instructions into operation-specific parameters. Common fields include:

• Issue creation: issue type, project, title or summary, description, priority, assignee, and supported custom fields.
• Status synchronization: issue ID or key and the target status or transition.
• Workflow automation: issue ID, trigger conditions, and the requested automation action.
• Tenant and authorization metadata: configured Jira tenant, authenticated user identity, permission scope, and API endpoint context.

Result schema

{
  "success": true,
  "data": {
    "result": "Skill-related configuration or Jira operation result"
  },
  "error": null
}

Generated and tracked information

• Normalized API responses containing operation status, issue identifiers, transition results, or Jira error details.
• Audit log entries for executed operations and returned outcomes.
• Runtime configuration supplied by the agent or environment; the skill does not specify a required project file layout or persistent generated-file format.
• Sensitive API keys, tokens, and credentials must never be written to results or logs.

Limits and taxonomy