jira

Manage Jira, Tempo, and Confluence tasks via credential-proxied HTTP endpoints.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SimyV/agent-system --skill jira-simyv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/SimyV/agent-system/tree/main/config/skills/jira
Command: npx skills add https://github.com/SimyV/agent-system --skill jira-simyv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira, Tempo, and Confluence are powerful but operate as separate tools. This Skill unifies operations by enabling credential-proxied access to manage issues, time logs, and pages from a single interface, reducing context switching and manual orchestration.

Core Features & Use Cases

  • Create, update, and search Jira issues (including Epics, Sprints, and comments) via the proxy.
  • Log time in Tempo and manage Confluence pages and spaces from one workflow.
  • Read and write Confluence pages and link Jira issues to Epics and sprints as part of end-to-end project management.

Quick Start

Connect your Atlassian accounts through the credential proxy and start issuing commands to manage Jira, Tempo, and Confluence from a single interface.

Frequently Asked Questions about jira

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Jira issues and Confluence pages from a single interface?▼

You can manage Jira issues and Confluence pages from a single interface by using a credential-proxied API that routes requests through local proxy URLs to handle creation, updates, and searches across both platforms.

Can I log time in Tempo while updating Jira issues in the same workflow?▼

Yes, you can log time in Tempo and update Jira issues in the same workflow by routing requests through the local proxy URLs with the X-User-ID header to inject credentials for both services.

What is needed to connect Atlassian accounts for unified Jira and Confluence workflows?▼

To connect Atlassian accounts for unified Jira and Confluence workflows, you need to set up a credential proxy that routes requests via localhost with the X-User-ID header to authenticate and manage issues, time logs, and pages.

Does this approach support creating Epics and linking Jira issues to Sprints?▼

Yes, this approach supports creating Epics and linking Jira issues to Sprints via the proxied API, allowing you to handle issue creation, updates, and sprint management as part of end-to-end project management.

How does the credential proxy work for Atlassian issue-management and time tracking?▼

The credential proxy works for Atlassian issue-management and time tracking by routing all API requests through local proxy URLs and injecting the user's credentials via the X-User-ID header to access Jira and Tempo.

Are there limitations when using a local proxy to manage Confluence spaces and pages?▼

The main limitation when using a local proxy to manage Confluence spaces and pages is that all requests must route through localhost with the X-User-ID header, requiring the proxy environment to be running for successful operations.