← 返回 Skills 市场
7124
总下载
7
收藏
0
当前安装
13
版本数
在 OpenClaw 中安装
/install jira-api
功能描述
Jira API integration with managed OAuth. Search issues with JQL, create and update issues, manage projects and transitions. Use this skill when users want to interact with Jira issues, projects, or workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Jira connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Jira action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Jira examples; they add no Jira capability - Jira is not an event source, a trigger cannot read Jira data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
安全使用建议
Install only if you trust the Maton packages and account connection. Prefer OAuth, grant the narrowest Jira scopes available, confirm every write or automation setup, avoid raw API keys unless the CLI cannot be used, and review any trigger destination because it can forward future event data continuously.
能力评估
Credentials
Network access, OAuth/API-key authentication, and Jira account access are proportionate to the integration purpose; raw HTTP with MATON_API_KEY is described as a fallback only and includes handling cautions.
Install Mechanism
The skill installs pinned Maton CLI/SDK packages via npm, Homebrew, and optional pip/npm SDK paths, but does not provide artifact checksums or signature verification.
Instruction Scope
The instructions repeatedly default to read/list operations, require explicit approval for connection creation and all writes, and treat third-party API/event content as untrusted data.
Persistence & Privilege
OAuth tokens, hosted functions, triggers, and destinations can persist beyond a single run, but the artifact discloses this, scopes it to user-approved workflows, and warns about cleanup, forwarding, and credentials.
Purpose & Capability
The documented capabilities match the stated purpose: Jira search, issue/project operations, connection management, and optional Maton-hosted automation around Jira workflows.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install jira-api - 安装完成后，直接呼叫该 Skill 的名称或使用
/jira-api触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v1.2.2
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.1
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.8
- Removed the file: skill-card.md
- No user-facing functionality changes
- Documentation and usage remain the same
v1.0.7
- Added CLI and Homebrew installation instructions for the Maton CLI.
- Included CLI examples alongside Python and raw REST API usage throughout the documentation.
- Expanded usage sections with clear CLI, NPM, and Python commands for common operations (connect, list, create, view, delete).
- Provided multiple examples for specifying connections and using cloud IDs with the CLI.
- Improved structure and readability of the quick start and API reference sections.
v1.0.6
- Updated all API endpoints and code examples to use `https://api.maton.ai` instead of `https://gateway.maton.ai` and `https://ctrl.maton.ai`.
- Clarified proxying behavior: Maton proxies requests to `api.atlassian.com` and injects OAuth tokens automatically.
- Added a new section on security and permissions, emphasizing explicit user approval for write operations.
- Improved clarity for specifying connections using the `Maton-Connection` header.
- Removed the LICENSE.txt file.
v1.0.5
- Added clawdbot metadata including emoji and required environment variable MATON_API_KEY to SKILL.md.
- No changes to functionality or user instructions.
v1.0.4
No changes detected in this release.
- Version bumped to 1.0.4, but no file changes or feature updates were made.
v1.0.3
- No code or documentation changes detected in this release.
- Version number updated to 1.0.3.
v1.0.2
- Added a note in the description to use the api-gateway skill for other third party apps.
- Updated Quick Start and connection management examples to use Python inline scripts instead of curl.
- Simplified authentication header instructions for better clarity.
- No changes to API endpoints or main functionality.
v1.0.1
- Added support for specifying which Jira OAuth connection to use via the Maton-Connection header.
- Updated the base API URL format instructions and clarified how to substitute `{native-api-path}`.
- Enhanced connection details in the Get Connection example (now shows `creation_time`, `last_updated_time`, and `metadata`).
- Clarified API key instructions and expanded details for account creation.
- Various doc improvements for clarity and updated examples.
v1.0.0
- Major upgrade: replaced legacy CLI-based integration with direct Jira Cloud API access via managed OAuth and Maton API gateway.
- Added documentation for cloud ID retrieval, OAuth connection management, and comprehensive API endpoints (issues, projects, transitions, users, etc.).
- Included code examples for JavaScript and Python.
- Detailed setup instructions for Maton API key and OAuth.
- Enhanced error handling guidelines and rate limit notes.
- Expanded references to official Jira API documentation.
元数据
常见问题
Jira 是什么？
Jira API integration with managed OAuth. Search issues with JQL, create and update issues, manage projects and transitions. Use this skill when users want to interact with Jira issues, projects, or workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Jira connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Jira action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Jira examples; they add no Jira capability - Jira is not an event source, a trigger cannot read Jira data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 7124 次。
如何安装 Jira？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install jira-api」即可一键安装，无需额外配置。
Jira 是免费的吗？
是的，Jira 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
Jira 支持哪些平台？
Jira 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 Jira？
由 byungkyu（@byungkyu）开发并维护，当前版本 v1.2.2。
推荐 Skills