一键在 Manus 中运行任何 Skill

开始使用

$pwd:

jira-read-ticket

Name: Jira Read Ticket
Author: Checkmk

// Fetch and display a Jira ticket's description, comments, attachments, and linked tickets

在 Manus 中运行

$ git log --oneline --stat

stars:2,273

forks:536

updated:2026年5月7日 10:39

文件资源管理器

3 个文件

SKILL.md

readonly

name	jira-read-ticket
description	Fetch and display a Jira ticket's description, comments, attachments, and linked tickets

Read a Jira Ticket

Fetches a Jira ticket and displays its full context: description, comments, attachments, and linked tickets. User names are anonymized.

Note: This skill is limited to the CMK project to avoid interfering with sensitive customer data. Only CMK- prefixed tickets are supported.

Arguments

The user provides one or more Jira ticket keys as the argument (e.g., /jira-read-ticket CMK-12345 or /jira-read-ticket CMK-12345 CMK-67890).

Workflow

1. Fetch ticket context

For each ticket key provided, run the helper script:

.venv/bin/python .github/skills/jira-read-ticket/read_ticket.py <TICKET_KEY>

If the script fails, report the error to the user and continue with the remaining tickets.

If multiple tickets are requested, fetch them in parallel using separate Bash calls.

2. Review attachments

Skip this step entirely if the script output contains no attachment sections.

If there are attachments, launch at most 2 Task agents (subagent_type: general-purpose) in parallel:

Images agent (only if there are image attachments): One agent receives ALL image file paths. It should read each image with the Read tool and describe what it shows (UI state, error messages, annotations, etc.). Return a concise summary per image.
Other files agent (only if there are non-image attachments): One agent receives ALL other file paths. For text-based files (logs, configs, CSVs), read and summarize key findings. For archives (tar, zip, gz), extract via Bash and summarize structure. Return a concise summary per file.

3. Present the ticket

Present the ticket context to the user. Summarize the key information:

What the ticket is about (type, status, priority)
The core ask from the description
Key takeaways from comments (decisions made, blockers, etc.)
Notable linked tickets and their relevance
Attachment summaries (if any)

Keep it concise — the user can ask follow-up questions if they need more detail.

related-skills.json

同仓库

test-review.md

from "Checkmk/checkmk"

Use when reviewing tests or test changes in a diff, pull request, or merge request. Triggers on assessing test quality, spotting test anti-patterns, or evaluating whether an assertion earns its place.

2026-05-282.3k

crash-owner-rollup.md

from "Checkmk/checkmk"

Generate the periodic "unsolved Checkmk check crashes on 2.4+" Slack rollup, grouped by component owner. Composes the crash-report and component-owners skills and emits Slack-ready plain text (no markdown).

2026-05-262.3k

crash-report.md

from "Checkmk/checkmk"

Queries and reads crash reports from crash.checkmk.com

2026-05-262.3k

jira-create-ticket.md

from "Checkmk/checkmk"

Create a Jira ticket in CMK with component, team, and epic matched from compass and roadmap data

2026-05-222.3k

grill-me.md

from "Checkmk/checkmk"

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

2026-04-302.3k

gerrit.md

from "Checkmk/checkmk"

Interacts with Gerrit code review to list changes and improve them

2026-04-232.3k

package.json

"author": "Checkmk"

"repository": "Checkmk/checkmk"

打开 GitHub 仓库查看创作者相关仓库

$ install --global

$ download --local

在 Manus 中运行

$ useful --forSOC

计算机用户支持专员计算机与数学类职业15-1232L4

软件开发工程师L4

Read a Jira Ticket

Fetches a Jira ticket and displays its full context: description, comments, attachments, and linked tickets. User names are anonymized.

Note: This skill is limited to the CMK project to avoid interfering with sensitive customer data. Only CMK- prefixed tickets are supported.

Arguments

The user provides one or more Jira ticket keys as the argument (e.g., /jira-read-ticket CMK-12345 or /jira-read-ticket CMK-12345 CMK-67890).

Workflow

1. Fetch ticket context

For each ticket key provided, run the helper script:

.venv/bin/python .github/skills/jira-read-ticket/read_ticket.py <TICKET_KEY>

If the script fails, report the error to the user and continue with the remaining tickets.

If multiple tickets are requested, fetch them in parallel using separate Bash calls.

2. Review attachments

Skip this step entirely if the script output contains no attachment sections.

If there are attachments, launch at most 2 Task agents (subagent_type: general-purpose) in parallel:

Images agent (only if there are image attachments): One agent receives ALL image file paths. It should read each image with the Read tool and describe what it shows (UI state, error messages, annotations, etc.). Return a concise summary per image.

Other files agent (only if there are non-image attachments): One agent receives ALL other file paths. For text-based files (logs, configs, CSVs), read and summarize key findings. For archives (tar, zip, gz), extract via Bash and summarize structure. Return a concise summary per file.

3. Present the ticket

Present the ticket context to the user. Summarize the key information:

What the ticket is about (type, status, priority)

The core ask from the description

Key takeaways from comments (decisions made, blockers, etc.)

Notable linked tickets and their relevance

Attachment summaries (if any)

Keep it concise — the user can ask follow-up questions if they need more detail.

jira-read-ticket

Read a Jira Ticket

Arguments

Workflow

1. Fetch ticket context

2. Review attachments

3. Present the ticket

同仓库更多 Skills

同仓库更多 Skills

Read a Jira Ticket

Arguments

Workflow

1. Fetch ticket context

2. Review attachments

3. Present the ticket