182건 · 관련도순
Read and update Jira tickets through connections saved in Orca. Use it to check the details of work requested through Jira and make ticket updates, selecting a specific site when multiple Jira sites match.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinate project delivery by routing requests to eight specialist skills or running a verified delivery workflow. Use live Jira data for progress analysis and completion forecasts, with recorded evidence and checks before tasks are closed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Work with Jira issues through Orca's command-line interface. Search issues, move them through workflow states, create follow-up issues, and record completion with a PR or MR link and a comment using guidance matched to the installed Orca version.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage Jira issues, build JQL searches, and design project workflows and reports. Use bundled scripts to generate search queries and check workflow designs, with guidance on which operations require Jira’s interface or API.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Connect AI agents to Jira and Confluence through MCP, a protocol for accessing external tools. This skill guides issue searches and updates, page management, sprint workflows, authentication setup, and troubleshooting of Atlassian integrations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage Jira issues through natural language using jira CLI or Atlassian MCP, a tool connection. Search and view tickets, draft new issues, update assignments or status, and check sprints, with review and approval before changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage Jira issues through Atlassian MCP, a connection that lets an AI agent use Jira tools. Find tasks, create issues and subtasks, update assignees, add comments, and change status using the detected project configuration.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Drive JIRA workflow lifecycle via the jira-as wrapper: transition, assign, resolve, reopen, manage versions and components. Triggers: 'transition KEY to Status', 'mark KEY as Done', 'assign KEY to user', 'reopen KEY', 'release version', 'create component'. NOT for issue CRUD (mk:jira-issue); NOT for bulk transitions (mk:jira-bulk).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a central vulnerability dashboard with DefectDojo to combine scanner findings, remove duplicates, and track remediation. Includes Docker deployment, automated scan imports from CI/CD pipelines, Jira ticket integration, and API queries for reporting metrics.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
JIRA Service Management via the jira-as wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains). Triggers: 'create JSM request', 'list service desks', 'SLA status for KEY', 'approve request KEY', 'list queue NAME'. Requires JSM-licensed tenant + agent role. NOT for core Jira issue ops (mk:jira-issue); NOT for project admin (mk:jira-admin).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA issue CRUD via the jira-as wrapper. Triggers: 'create bug/task/story', 'show me PROJ-123', 'get/view/look up issue', 'update PROJ-123', 'delete PROJ-123'. NOT for transitions (mk:jira-lifecycle); NOT for comments/attachments (mk:jira-collaborate); NOT for bulk ops (mk:jira-bulk); NOT for issue links (mk:jira-relationships); NOT for time logging (mk:jira-time); NOT for sprint/epic (mk:jira-agile).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA-side cache + project-context discovery via the jira-as wrapper. Triggers: 'jira cache status', 'clear jira cache', 'discover project context for PROJ'. Diagnostic-only — no Atlassian state changes. NOT for issue CRUD; NOT for project admin (mk:jira-admin).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage JIRA collaboration surface via the jira-as wrapper: comments, attachments, watchers, notify. Triggers: 'comment on KEY', 'add attachment to KEY', 'watch KEY', 'notify KEY watchers'. Internal-vs-public comment safety enforced. NOT for issue CRUD (mk:jira-issue); NOT for issue links (mk:jira-relationships).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need Jira CLI (`jira`) installation/authentication guidance and a maintainer-authored Jira issue inventory workflow. The agent does not ingest raw Jira issue or JQL output directly; it asks the Jira project maintainer/operator to author sanitized issue summaries before analysis or @014-agile-user-story handoff. This should trigger for requests such as jira issue list; List Jira issues; Jira JQL issue query; Jira CLI issue workflow. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage JIRA issue relationships via the jira-as wrapper: link, unlink, blockers, dependencies, clone, bulk-link. Triggers: 'link KEY blocks KEY', 'what blocks KEY', 'clone KEY', 'unlink KEY from KEY'. NOT for sprint/epic relationships (mk:jira-agile).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA search + filter management via the jira-as wrapper. Triggers: 'search jira', 'find issues where X', 'jql for ...', 'export search results', 'manage saved filters'. JQL injection-safe via the shared sanitizer. NOT for single-issue CRUD (mk:jira-issue); NOT for bulk write ops (mk:jira-bulk).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA project / user / group / scheme / automation administration via the jira-as wrapper (11 sub-domains, ~65 verbs). Triggers: 'create JIRA project', 'list users', 'delete user USERNAME', 'list permission schemes', 'create group NAME'. Requires admin role. Destructive ops (project/user/group delete) require 2-step token confirmation. NOT for per-issue ops (mk:jira-issue / mk:jira-lifecycle); NOT for JSM admin (mk:jira-jsm).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA agile via the jira-as wrapper: epics, sprints, backlog, ranking, story points, subtasks, velocity. Triggers: 'create sprint', 'add KEY to sprint', 'set story points on KEY', 'rank KEY before KEY', 'velocity for board', 'epic add'. Board ID ≠ project key. NOT for issue CRUD (mk:jira-issue); NOT for time tracking (mk:jira-time).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Retrieve Jira issues, turn their requirements into testable criteria, and keep progress updated within an AI coding workflow. Includes issue searches, comments, and status changes through MCP tools or direct REST API calls.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and maintain reusable Jira issue descriptions and Confluence page structures for meeting notes, requirements, decisions, and other shared documents. The skill guides template design, generates Confluence markup, and covers validation, versioning, deployment, and usage instructions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize Jira issues, plan sprints, and define workflows with clear ownership and acceptance criteria. Get help writing JQL, Jira's query language, to find stalled work, review workloads, and support project reporting.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
JIRA time tracking via the jira-as wrapper: log work, list/update/delete worklogs, set estimates, generate reports, bulk-log. Triggers: 'log 2h on KEY', 'show worklog for KEY', 'time report for sprint', 'bulk-log 30m to JQL'. Worklog edit/delete loses data — agent confirms. NOT for sprint capacity (mk:jira-agile).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Routing skill — recommends the correct mk:jira-* leaf for any Jira task. Triggers: 'jira', 'jira ticket', ambiguous Jira intent. NOT an executor — every actual operation forks via a leaf skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage organization-wide Atlassian administration, including user onboarding and removal, group permissions, sign-in settings, and app integrations. It provides workflows for access reviews, configuration changes, operational checks, and recovery planning, primarily through admin consoles and REST APIs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.