Jira Syntax

Organization

netresearch

jira-syntax

Use when writing or formatting Jira descriptions, comments, or any text destined for Jira. Converts Markdown to Jira wiki markup, provides templates (bug reports, feature requests), and validates syntax before submission. Trigger on any Jira content authoring task.

Overview

Publisher	netresearch
Repository	`jira-skill`
Skill name	`jira-syntax`
Stars	90
Forks	26
Bundled files	8
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
8 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by netresearch on GitHub. Read the source before you install it.

Installation

Install the Jira Syntax AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/netresearch/jira-skill/tree/main/skills/jira-syntax
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/netresearch/jira-skill.git /tmp/jira-skill
mkdir -p .claude/skills
cp -r /tmp/jira-skill/skills/jira-syntax .claude/skills/jira-syntax

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Jira Syntax in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Jira Syntax on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Jira Syntax is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Jira Syntax

Jira wiki markup syntax, templates, and validation. For API operations, use the jira-communication skill.

Quick Syntax Reference

Jira Syntax	Purpose	NOT this (Markdown)
`h2. Title`	Heading	`## Title`
`bold`	Bold	`bold`
`_italic_`	Italic	`italic`
`{{code}}`	Inline code	`code`
`{code:java}...{code}`	Code block	java ```
`[text\|url]`	Link	`[text](url)`
`[PROJ-123]`	Issue link	-
`[~username]`	User mention	`@username`
`* item`	Bullet list	`- item`
`# item`	Numbered list	`1. item`
`\|\|Header\|\|`	Table header	`\|Header\|`

See references/jira-syntax-quick-reference.md for complete syntax documentation.

Available Templates

Bug Report

Path: templates/bug-report-template.md

Sections: Environment, Steps to Reproduce, Expected/Actual Behavior, Error Messages, Technical Notes

Feature Request

Path: templates/feature-request-template.md

Sections: Overview, User Stories, Acceptance Criteria, Technical Approach, Success Metrics

Syntax Validation

Run before submitting to Jira:

bash
${CLAUDE_SKILL_DIR}/scripts/validate-jira-syntax.sh path/to/content.txt

It gates the post — run it as its own step, never chained with the posting command.

Validation Checklist

Headings: h2. Title (space after period)
Bold: *text* (single asterisk)
Code blocks: {code:language}...{code}
Lists: * for bullets, # for numbers
Links: [label|url] or [PROJ-123]
Tables: ||Header|| and |Cell|
Colors: {color:red}text{color}
Panels: {panel:title=X}...{panel}

Common Mistakes

❌ Wrong	✅ Correct
`## Heading`	`h2. Heading`
`bold`	`bold`
`code`	`{{code}}`
`[text](url)`	`[text\|url]`
`- bullet`	`* bullet`
`h2.Title`	`h2. Title`
`MR !42` (bare GitLab ref)	`[MR 42\|url]` or full `group/project!42` — a bare `!…!` is image markup
`(/)` on an open/proposed item	`(x)` — `(/)` renders as a green check (done); use `(x)` for open items
`( )` as a checkbox	`(x)` — `( )` is not a macro and renders literally
`(-)` or `(x)` on a pending step in a review	`(i) pending: …` — `(-)` renders as a red no-entry sign, and in a review `(x)` means a failure

Integration with jira-communication Skill

Workflow:

Get template from jira-syntax
Fill content using Jira wiki markup
Validate with ${CLAUDE_SKILL_DIR}/scripts/validate-jira-syntax.sh
Submit via jira-communication skill

References

references/jira-syntax-quick-reference.md - Complete syntax documentation Includes Ask the renderer instead of reasoning about it: POST /rest/api/1.0/render returns the HTML Jira will produce for any markup, before anything is posted. Use it to settle a markup question rather than deriving the answer.
references/cross-project-refs.md - GitLab cross-project ref convention (group/project!N, group/project#N, group/project@tag) when linking to GitLab from Jira
templates/bug-report-template.md - Bug report template
templates/feature-request-template.md - Feature request template
${CLAUDE_SKILL_DIR}/scripts/validate-jira-syntax.sh - Automated syntax checker
Official Jira Wiki Markup

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

AGENTS.md2 KB
CLAUDE.md1 KB
evals/evals.json7 KB
references/cross-project-refs.md3 KB
references/jira-syntax-quick-reference.md17 KB
scripts/validate-jira-syntax.sh26 KB
templates/bug-report-template.md4 KB
templates/feature-request-template.md8 KB

Frequently asked questions

What does the Jira Syntax AI skill do?

Why use Jira Syntax on TypingMind?

Because you install it once and use it with any model. Jira Syntax is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Jira Syntax in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/netresearch/jira-skill/tree/main/skills/jira-syntax. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Jira Syntax?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Jira Syntax?

As many as you like. As long as a model supports skills, you can use Jira Syntax with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Jira Syntax AI skill free?

It is published on GitHub by netresearch. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Documentation Lookup

affaan-m

CommunityPopular

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React,…

Everything Claude Code

affaan-m

CommunityPopular

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

Discord User Post

Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots,…

Test Audit

Invoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Jira Syntax

Quick Syntax Reference

Available Templates

Bug Report

Feature Request

Syntax Validation

Validation Checklist

Common Mistakes

Integration with jira-communication Skill

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now